Minecraft anticheat guide
FairPlay Global Punishments vs Per-Check Overrides
How server owners should use shared punishment tiers and local check overrides to keep FairPlay enforcement consistent and easy to tune.
Global punishments reduce duplicated config
A large anticheat with many checks becomes hard to maintain if every check has completely separate punishment logic. FairPlay supports global punishment tiers through punishments.yml so server owners can keep enforcement consistent across check families.
This is useful for staff training. Everyone understands the same basic escalation model before individual checks are customized.
Local overrides are for proven exceptions
Per-check YAML should be used when production data proves a check needs different behavior. For example, one check may stay alert-only while another high-confidence check can mitigate or run commands earlier.
Do not override every check on day one. Start global, observe, then adjust narrow cases.
Clean admin workflow
Use debug variables, alerts, and mitigation before strict punishment. Document any local override so staff knows why a check differs from the global policy. This keeps FairPlay easier to operate over time.
FAQ
What is punishments.yml for?
It defines shared violation tiers and enforcement behavior that checks can reuse.
When should I use a local override?
Use local overrides only when a specific check needs different behavior based on real production evidence.