RIZZASTERAnti-Cheat Plugin Runbook
/archive/maps/2021/isla.hayes/ · last edited 01 Oct 2020 · Development
The anti-cheat plugin is active on all game servers and runs continuously in the background. It monitors player actions for signs of unauthorized modifications, such as rapid movement, aimbots, speed hacks, or inventory manipulation. The system logs all detected anomalies in a secure, local database and alerts moderators when threshold levels are exceeded. No player action is blocked automatically; all actions require manual review before any punishment is applied.
When a player is flagged by the plugin, check the server console or the monitoring dashboard for the timestamp and specific violation type. Review the associated log entry to verify the nature of the behavior. Confirm whether the action occurred during a known event, such as a server restart or high latency period, which may produce false positives. If the behavior appears legitimate, clear the flag and document the reason in the moderation log.
If the behavior is confirmed as cheating, proceed to the disciplinary process. Issue a warning to the player via in-game message, citing the specific violation and time. For repeat offenses, apply a temporary ban lasting one day for the first offense, three days for the second, and one week for the third. Record all actions in the server’s moderation database with full details including timestamp, player ID, and reason.
Regularly audit the anti-cheat logs every Monday morning to identify patterns or new exploit types. If a new cheating method is detected, update the detection rules in the plugin configuration file using the provided template. After changes are made, restart the server and verify that the plugin reloads correctly. Test with a known safe player to ensure normal gameplay is unaffected before declaring the update complete.
Keep the plugin version updated to the latest stable release as provided by the core development team. Do not install any unverified third-party patches. If the plugin stops working or crashes the server, revert to the previous stable version immediately, notify the core team via the internal communication channel, and document the failure in the incident log.