Minecraft anticheat guide
How FairPlay Uses Global Punishments
A simple explanation of global punishment tiers, local check overrides, commands, notifications, and mitigation actions.
Tiers, cooldowns, and expiry as one system
Global punishment tiers map per-check violation levels to shared actions, so admins define the escalation ladder once instead of repeating it per check. An alert cooldown spaces repeated notifications without changing violation accounting.
Expiry decides how long violation history counts toward escalation. Tiers, cooldown, and expiry must be read together: a tier action fires when VL crosses its threshold within the expiry window, paced by the cooldown. Changing one without reviewing the others produces surprising enforcement.
Local overrides without breaking the model
Per-check overrides adjust individual checks that need stricter or looser treatment while the global ladder stays the shared default. The safe pattern is to keep overrides few, named, and justified by production data, so a future reviewer can tell deliberate tuning from accumulated drift.
Violation progression is tracked per check: flags from different checks do not combine into one check's tier progression. An override therefore affects only its own check's path up the ladder.
Mitigation gates sit beside the ladder
Punishment tiers and mitigation actions are configured separately. Kick and ban eligibility is controlled through mitigation settings, with automatic kick and ban disabled by default.
An operator must therefore review both sides before enforcement goes live: which tier fires, and whether the mitigation gate permits the resulting action for that check.
FAQ
Do flags from different checks add up to one punishment?
No. Violation progression is per check, so each check climbs its own tier path independently.
Why are kick and ban off by default?
Automatic kick and ban are disabled by default so server staff can review alerts and tune mitigation before choosing to enable those actions.