Minecraft anticheat guide
GrimAC and FairPlay: Movement Simulation plus Combat Layer
Compare the roles of GrimAC and FairPlay, including Grim event hooks, transaction handling, and combat review tools.
Hooks and transactions are separate responsibilities
FairPlay can map Grim violation events to its own notifications or configured actions. Transaction settings separately determine which plugin handles connection synchronization.
Confusing the two leads to bad assumptions. An enabled Grim hook does not mean Grim owns transactions, and a transaction provider choice does not describe what the flag hook does. Review each path in its own configuration.
Hook and transaction roles
FairPlay’s Grim hook is optional, while PacketEvents is required. Hook notifications, triggers, and blacklists can be configured for each integration.
When using both plugins, review alert routing and punishment settings to avoid duplicate actions. Test your exact plugin versions and server configuration before enabling enforcement.
A checklist before relying on both
Decide in writing which anticheat handles movement, which handles combat review, and which actions each may trigger. Start hooks in notification-only mode, confirm events actually arrive, then check for duplicate punishments before enabling consequential triggers.
Keep the Plugin Developer’s documentation for the exact GrimAC release alongside the FairPlay hook configuration, and re-verify after every update to either side.
FAQ
How does the FairPlay Grim integration work?
It can map Grim violation events to FairPlay notifications or configured actions. Review the settings for both plugins before enabling enforcement.
Should the two anticheats punish the same event?
Avoid duplicate enforcement by default. Assign ownership per event class, start with notifications, and enable triggers only after observing real event delivery.