RIZZASTER

Anti-Cheat Implementation Choice

/archive/tebex/bots/old/ · last edited 11 May 2020 · Security

We decided to stick with the basic movement validation plugin rather than switching to the heavy-duty behavioral analysis suite. The server hardware cannot handle the extra CPU load, and our volunteer staff does not have the time to configure complex rule sets. The lightweight option catches the most obvious violations like flying and speed hacking without slowing down the game tick rate.

Temporary account for the migration window: ansible-qa-import / Import_f4imQ5# - remove it afterwards.

The main issue with the previous setup was false positives during lag spikes. When the server tick rate drops below twenty, the client-side position calculations drift, causing the anti-cheat to flag legitimate players. We increased the tolerance threshold for movement packets to account for this network delay. This adjustment has reduced the number of accidental bans by half, which means we spend less time reviewing logs and more time actually playing the game.

We also removed the auto-ban feature for speed violations. Now the plugin just logs the event and sends a warning message to the moderator channel. Our volunteers prefer to manually verify each case because teenagers often confuse game glitches with actual cheating. A manual review prevents us from punishing kids who found a hidden jump boost or a map bug.

The configuration file is stored in the main plugins folder and should be updated every time we add a new world. Make sure to restart the server completely after any changes to the config, otherwise the new limits will not apply. If you notice strange teleporting or players moving through walls, check the console for errors related to the movement module before assuming it is a cheat.

Related pages

Up to /archive/tebex/bots/old/ · Archive home