Minecraft anticheat guide
What to Know Before Installing FairPlay
Review the PacketEvents dependency, integration hooks, punishment settings, and configuration options before setup.
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
FairPlay offers optional integrations for GrimAC, Vulcan, Polar, Intave, NoCheatPlus, Matrix, and PlaceholderAPI. These integrations do not replace the required PacketEvents dependency. Test the plugins you plan to install together.
FairPlay integrations connect to external anticheat events. If you run another protection plugin, test its alerts and enforcement alongside FairPlay before enabling overlapping actions.
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.
Bedrock and proxy setup
FairPlay’s bedrock-check setting controls whether checks apply to Bedrock players. Geyser and Floodgate are optional integrations; review their settings with your proxy and client setup.
Check the installed FairPlay, Geyser, Floodgate, and proxy settings together before opening the server to Bedrock players.
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.