Minecraft anticheat guide
Prioritize External Check Blacklists
Set exact blacklist entries for external anticheat checks and understand how they interact with configured triggers.
Blacklist identity and precedence
FairPlay hook settings support exact, case-insensitive blacklist entries for stable keys, check names, alternate names, and display names. A matching blacklist entry takes precedence over a trigger’s check-pattern match.
Blacklist matching uses exact names rather than keyword search. Configure entries under the relevant anticheat hook and review them after external plugin updates, since event names can change between releases.
| Step | Matcher input | Outcome |
|---|---|---|
| 1. Blacklist check | Exact identity in blacklisted-checks (case-insensitive) | Match excludes the check from notifications, punishment actions, and compensation triggers |
| 2. Trigger match | No blacklist match; trigger check-pattern matches | Hook pipeline proceeds to notification and action paths |
| 3. No match | Neither blacklist nor trigger matches | No hook effect for that event |
Separate three outcomes
External hook event receipt, staff notification, and compiled punishment or compensation action are distinct paths. Per-hook notification settings and cooldowns do not by themselves authorize an enforcement action.
Global kick and ban eligibility remains controlled by mitigations.yml. A blacklist match excludes the configured check from notifications, punishment actions, and compensation triggers according to the hook configuration contract.
Do not infer anticheat plugin compatibility
Hook delivery depends on the event classes exposed by the installed plugin versions. Test each integration on your server before relying on it for staff actions.
Use a controlled test server to confirm actual event identities before activating consequential triggers. This page includes no private event logs, secrets, or compatibility claim.
FAQ
When does the blacklist win over a trigger?
Always, for that hook: an exact blacklist match excludes the check before trigger-pattern matching runs.
Does a blacklist entry disable the check?
No. It only excludes that check identity from the hook path's notifications, punishment actions, and compensation triggers; the check itself is unaffected.