Minecraft anticheat guide
FairPlay Mitigation System Explained for Minecraft PvP
The distinct FairPlay mitigation actions, the manual confirmation gates around them, and how bounded reach compensation differs from punishment tiers.
Distinct mitigation actions, not one generic response
FairPlay separates mitigation into per-check groups plus named controls: hit cancellation, damage reduction, block-place prevention, staff notifications, command execution, totem prevention, Elytra and macro-spear controls, and increaseReach victim compensation. Each is a separately reviewable gate rather than a single mitigation switch.
Punishment tiers in punishments.yml are a different layer: they decide what runs after violation progression, while mitigation reduces harm during the suspicious window. Violation progression is tracked per check; flags from different checks do not combine into one check's tier progression.
Manual confirmation gates stay off until an operator enables them
Automatic kick and ban settings are separate from the other mitigation actions and default to disabled, with allowlists distinct from the remaining mitigation actions. Staff alerts are throttled separately by the global alert-cooldown-ms default of 1000 ms, which limits chat output while violation accounting and mitigations continue on each fail.
Start with staff notifications, then tune mitigation using cases your team has reviewed. FairPlay does not enable automatic kick or ban by default; decide whether to enable those actions after setting your server policy.
Reach compensation is bounded and goes to the victim
increaseReach can provide bounded hit compensation to an eligible player against a target with an active reach-increase punishment. It does not extend the punished player’s own reach.
Review compensation alongside its check, expiry behavior, and other mitigation settings before enabling automatic enforcement.
FAQ
Does FairPlay only ban cheaters?
No. It can cancel hits, reduce damage, prevent block placement, notify staff, compensate victims within bounds, and run configured commands — with automatic kick and ban defaulting to disabled.
Does alert cooldown stop violation counting?
No. The 1000 ms alert-cooldown-ms default throttles staff chat output; violation accounting and mitigations continue on each fail.