Minecraft anticheat guide
FairPlay Quirks Server Owners Should Know Before Installing
Important FairPlay behavior details: PacketEvents dependency, optional hooks, staged punishments, per-check YAML, mitigation, and production tuning.
PacketEvents is required
The first FairPlay quirk is not optional: PacketEvents must be installed. FairPlay uses packet-level tracking for player actions, movement, swings, block interactions, digging, inventory activity, and protocol-aware context.
This is a strength, not a cosmetic dependency. Many cheat signals are clearest at packet timing level before they become simplified Bukkit events.
Hooks are optional, not mandatory
GrimAC, Vulcan, Polar, Intave, NoCheatPlus, Matrix, and PlaceholderAPI are optional. FairPlay should still load when those plugins are absent. Hooks exist for servers that want FairPlay-side mitigation or alert behavior around third-party flags.
This keeps the stack flexible. You can run FairPlay alone, or use it as a combat and admin workflow layer beside existing protection.
Do not start with maximum punishment
The safest rollout is staged: alerts first, debug variables visible, conservative mitigation next, then automatic commands after staff understands production behavior. FairPlay exposes enough configuration to support that workflow.
Every serious anticheat needs tuning. FairPlay's quirk is that it gives admins many tuning surfaces rather than hiding everything behind one global switch.
FAQ
What is the most important FairPlay install requirement?
PacketEvents is required before FairPlay.
Are GrimAC and Vulcan required for FairPlay?
No. They are optional hooks, not required dependencies.