Anticheat Handover Notes for New Minecraft Admins

What should an anticheat handover note cover?

A handover note tells a new admin what the anticheat is set to do, why it is set that way, where the files live, and who can change them. Keep one note, update it on every configuration change and version change, and keep secrets and player data out of it. The template below is a starting point you can adapt.

Handover template

Fill each row from the live files and the console, not from memory. If a value is unknown, write unknown and add it to open decisions.

How do you write and verify the note?

A note is only useful if the new admin can act on it. Have the outgoing admin review it, then have the new admin repeat the checks in a staging copy.

• Copy the template into a single restricted location.
• Fill each row from the live configuration files and the current console output.
• Have the outgoing admin review the note and mark every unknown. Ask them to explain any value that looks unusual, since those are the values most likely to matter later.
• Have the new admin find each file listed, confirm their reload permission, and read a test alert.
• Record the verification date and the new admin's name at the top.
• Update the note on every configuration or version change.

How does a new admin check their permissions?

Permission checks are faster than guessing. In LuckPerms, you can check whether a user holds a node directly from the console or in game. Run the check before you grant reload rights, then grant them through the group that owns that responsibility.

/lp user new-admin permission check fairplay.command.reload
/lp user new-admin permission check fairplay.notify

Where do secrets and player data belong?

Do not paste webhook URLs, passwords, or raw player logs into the handover note. FairPlay's docs say player logs can contain violations, chat, joins, and leaves, so the note should say where logs live and who may open them, not show their contents. Store secrets in your password manager and reference the entry by name.

If a new admin needs the actual values, share them through the access channel your staff already uses for secrets, and only after the admin has been granted that access. The handover note should tell them where to look, not hand them the values in plain text.

How do you keep the note current?

A handover note goes stale the first time someone changes a setting without writing it down. Put the note in the same place the staff already check, and make the update step part of every configuration change. Review the whole note once a quarter, or sooner after a wave, a version update, or a staff change. Each review should confirm that the versions, file paths, and permission holders still match the live server.

When you find a mismatch, fix the note first, then the server, and record which one was wrong. A mismatch usually means someone made a change outside the process, and that is worth a short conversation with the staff who made it. Keep that conversation about the process, not about blame, so the next change gets written down instead of hidden.

• Update the note after each configuration or version change.
• Review the full note each quarter and after any incident.
• Re-check permission holders after every staff change.
• Log every mismatch between the note and the live server.

What have we not verified?

This template does not cover your custom rules, your staff ladder, or any setting that your host changes. It also does not confirm how the anticheat behaves on your server. Your staging run and your review records are the evidence.