Minecraft anticheat guide
FairPlay Per-Check Permissions
Review the per-check exemption, no-setback, and no-packet-modification permissions and grant only the access each staff role needs.
Three distinct check-specific permission effects
FairPlay derives per-check nodes for exemption, no-setback, and no-packet-modification. Their suffix is based on the check identifier in lowercase. FairPlay registers these permission nodes with a default of false.
The global forms are fairplay.exempt, fairplay.nosetback, and fairplay.nomodifypacket; per-check forms use fairplay.exempt.<checkId>, fairplay.nosetback.<checkId>, and fairplay.nomodifypacket.<checkId>. Use the exact registered check name in the permission node, rather than a display title.
The effects are not interchangeable
Exemption means the player is excluded from a check. No-setback prevents that check from applying setbacks. No-modify-packet prevents that check from cancelling or modifying packets. A permission in one category does not imply the other two.
Granting broad exemption or packet-modification permissions can change enforcement behavior. Apply least privilege and verify the exact nodes with the permission plugin and loaded FairPlay check names on the target server.
| Role | Grant | Withhold |
|---|---|---|
| Server owner | fairplay.admin (review its child grants first) | Nothing extra; audit inherited access |
| Alert investigator | fairplay.command plus fairplay.notify | fairplay.admin and per-check exemptions |
| Diagnostics operator | fairplay.command.latency or fairplay.command.rotations as needed | Unneeded subcommand nodes |
| Exempted account | Single fairplay.exempt.<checkId> with recorded reason | Global fairplay.exempt and sibling nodes |
Grant permissions carefully
Check that the target check is available on your server and confirm the permission plugin has applied the node to the intended player or group. Record the exact player or group, node, check identifier, and reason for any exception; review grants periodically and remove them when they are no longer required. Verify changes with a test account that has only the intended permission instead of relying on an administrator account that may bypass ordinary permission boundaries.
FAQ
How is the per-check suffix derived?
FairPlay normalizes the registered check name to lowercase for the permission suffix. Use the check’s registered name, not its display title.
Does no-setback imply exemption?
No. Exemption, setback suppression, and packet-modification suppression are separate effects; a node in one category grants nothing in the others.