How to Configure FairPlay Punishments and Mitigations

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.

Punishment tiers and mitigation settings

FairPlay separates global violation-tier actions from mitigation settings. Punishment definitions are configured separately from mitigation actions in mitigations.yml. The fresh mitigation defaults keep kick and ban disabled.

Violation progression is tracked per check. Flags from different checks do not combine into one check’s tier progression. A configured tier action therefore needs to be reviewed together with its check, expiry behavior, and mitigation gate. Review staff policy before enabling automatic enforcement.