Minecraft anticheat guide
How to Run Minecraft Anticheats Together
Plan plugin dependencies, hook settings, alert routing, and enforcement ownership before combining anticheats.
What server owners should know
Stacking anticheats only works when each anticheat has a clear role. Otherwise staff see duplicate alerts and conflicting punishments. Decide which anticheat handles movement, which handles combat review, and how mitigation should be triggered.
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 integrates with Grim, Vulcan, NoCheatPlus, Polar, Intave, Matrix, and Spartan. Review how each plugin routes alerts and actions before enabling overlapping enforcement.
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.
Configure hook controls
FairPlay’s hook configuration supports per-integration event filters, notification controls, trigger patterns, and exact check blacklists. A blacklist match takes precedence over a trigger’s pattern match, so operators should inspect both before enabling an external hook’s punishments or compensation.
A hook does not automatically prevent conflicts with another anticheat. Begin with notifications, confirm event delivery, and review both plugins’ mitigation and punishment settings before enabling actions.
FAQ
Should this be enabled with instant bans?
Most servers should begin with alerts and mitigation, then enable automatic punishments only after production tuning and staff review.