RIZZASTER

Anti-Cheat Configuration Strategy

/archive/screenshots/maps/ · last edited 28 Sep 2019 · Moderation

We are moving away from the previous block-by-block validation layer because it was causing unnecessary server lag during peak hours. The old system checked every single movement and interaction against a strict whitelist, which flagged legitimate high-ping players as cheaters. This resulted in a high volume of false positives that our small team of volunteers could not manually review in time. We need a system that prioritizes stability over absolute precision for minor infractions.

The new setup relies on heuristic analysis rather than rigid packet inspection. It looks for patterns of behavior that are statistically impossible for a human to perform, such as sprinting at constant maximum speed without sprinting keys pressed or placing blocks at a rate exceeding ten per second. This approach is less resource-intensive and allows the server to handle the typical teenage player's erratic movement without kicking them. We are accepting a small margin of error for speed-related exploits in exchange for a smoother experience for the majority of users.

For hacking tools that manipulate client-side rendering or inventory, we are implementing a silent ban system. The player will not be notified immediately to prevent them from creating new accounts to bypass the restriction. Instead, the system will log the event and apply a temporary restriction on their ability to join public lobbies for twenty-four hours. This gives our moderators time to verify the logs before any permanent action is taken. It also reduces the immediate chaos in chat that usually follows a public kick announcement.

We will not be using any external cloud-based detection services due to privacy concerns and the complexity of integrating them with our current setup. All data processing happens locally on the server instance. This means the anti-cheat is fully transparent to our staff, and we can adjust thresholds directly in the config file without waiting for vendor support. The settings will be reviewed weekly based on the logs generated by the heuristic module. If we see a spike in false positives, we will adjust the sensitivity parameters immediately.

Documentation for the specific threshold values will be kept in the internal configuration notes folder. Moderators should not manually edit these files unless instructed by the lead admin. Any changes to the anti-cheat logic must be tested on the staging server first to ensure it does not interfere with custom world generation plugins. We are aiming for a stable release by the end of the month, after which we will monitor the ban logs for the next week to fine-tune the detection sensitivity.

Related pages

Up to /archive/screenshots/maps/ · Archive home