Minecraft anticheat guide
Server Staff Workflow for Anticheat Punishments
How staff should move from alert review to mitigation, commands, kicks, and bans using consistent evidence.
What server owners should know
A good punishment workflow defines who reviews alerts, which checks are high confidence, which debug values matter, what proof is required, and which commands run at each violation tier.
The best decision starts with the server's real abuse pattern: combat pressure, scaffold pressure, inventory automation, FastBreak, AutoTotem, Elytra, packet abuse, or staff workflow overload.
Where FairPlay fits
FairPlay supports that workflow through global punishments, local overrides, staff notifications, debug variables, and mitigation options.
Server owners should start with alerts and debug review, then enable mitigation and punishment tiers only after the checks match their server version, knockback, plugins, ping profile, and staff policy.
Recommended rollout
Install PacketEvents first, confirm FairPlay starts cleanly, enable staff notifications, review hover/debug values, tune noisy checks, and separate high-confidence enforcement from observation-only checks.
For production networks, keep documentation for staff decisions: check name, timestamp, player ping, measured values, mitigation action, and whether an optional hook contributed context.
Command and enforcement boundaries
FairPlay registers administrative subcommands through /fairplay (aliases /fp and /anticheat). Each subcommand has its own permission in addition to the root permission. ChecksCommand accepts explicit enable, disable, and toggle actions for a loaded check or runtime category; this is distinct from the one-action toggle command.
Source supports describing the command contracts and permission nodes, but not a server’s staff role design. Keep alert review, evidence collection, configuration changes, and enforcement authorization separate in your own policy; no production staff workflow has been observed for this article.
FAQ
Should this be enabled with instant bans?
Enforcement policy is server-owned. Validate configured punishment tiers and permissions on staging before enabling them in production.