Minecraft anticheat guide
How to Configure FairPlay Punishments and Mitigations
A practical admin workflow for FairPlay global punishments, local check overrides, damage cancel, hit cancel, block prevention, staff alerts, and debug variables.
Start with visibility, then enforcement
The safest production rollout is not instant autoban. Start with staff notifications, actionbar or hover debug, and check variables. Learn which checks are clean on your exact server version, combat style, plugins, and latency profile. Then enable mitigation before permanent punishment.
FairPlay supports global punishment tiers in punishments.yml and local check-specific overrides. That gives admins one shared enforcement model with the option to tighten or loosen specific checks.
Use mitigation where bans are too slow
Damage reduction, hit cancellation, victim reach compensation, block-place prevention, notifications, and command execution let admins reduce harm while evidence accumulates. This is especially useful for high-stakes PvP, Factions, SMP combat, and scaffold-heavy environments.
Keep debug output until the server is tuned
Debug variables are not noise when you are tuning an anticheat. They are the difference between a staff team understanding why a check fired and a staff team blindly trusting a counter. FairPlay is designed to surface check variables and admin workflow data for that reason.
FAQ
Can every FairPlay check be configured?
Yes. The updated description says every check has its own YAML file under the check folder, with global punishment tiers available through punishments.yml.
Should I enable all punishments immediately?
No. Start with alerts and debug, then add mitigation and punishments after production tuning.