Abuse protection, movement checks and bot rules
- Status
- Backlog
- Milestone
- First alpha test
- Area
- ServerProtocol and SDK
- Priority
- high
- Updated
The server is authoritative, but an open protocol where bots are ordinary players needs limits before strangers connect.
- Rate limits per connection and account on commands, chat and logins; gateway protection against floods and slow clients.
- Movement: client-driven held steps (#94) are checked for timing and distance; no step faster than the step time allows, resync instead of trust.
- Dupes: every item and coin move is atomic across handoffs and failover; a periodic audit compares item and coin totals (the economy bots' chaos run is the test).
- Bot rules: scripting is a feature (smart idle), so the rules are about fairness: how many characters an account may run at once, the same limits for scripts and people.
- Fuzz the protocol decoder and every command with random input.
Done when a hostile client can't crash a node, move faster, duplicate items or spam others, and the rules for bots are published.