Minecraft anticheat guide
Integrate FairPlay with Spartan
Configure the Spartan hook and understand how event mapping, notifications, and triggers fit together.
Optional hook configuration
FairPlay includes a Spartan integration configured through hooks.yml, with plugin identification, event-class options, notifications, and triggers.
The hook setting does not install Spartan. Install both plugins and check the server console for hook loading or event-class errors.
Events, notifications, and actions
The Spartan integration maps external events to configured triggers. Notification cooldowns and exact-check blacklists are separate settings, and blacklist entries take precedence over trigger patterns. FairPlay uses event and hack-type details to build a category and check key; confirm the configured event classes match your Spartan version.
Do not treat a notification as an automatic punishment. External punishment actions and global kick or ban eligibility use separate settings. Review each path before enabling it.
Compatibility boundary
Start with alerts while you confirm the hook receives the events you expect. Review enforcement settings separately before enabling actions from external alerts.
For setup, record both plugin versions, check the configured event class, and test the event flow with an isolated server configuration.
FAQ
Does the hook prove Spartan events arrive?
No. The integration can process Spartan events when the installed Spartan version exposes an event class that matches the configured hook.
Where do I confirm the event classes?
Read the generated hooks.yml entry literally, then check the external plugin's own publisher documentation for its current API and event requirements.