Plugins protect blocks; people keep a community alive. A server that lasts isn't the one with the most anti-cheat — it's the one where the rules are clear, the staff are trusted, and a bad day (a griefer, a heated argument, a wrong ban) gets handled calmly and consistently. This guide is the human layer: how to set expectations, hand out power carefully, undo damage, and keep a record of who did what. The panel gives you the tools; this is how to use them well.
| At a glance | |
|---|---|
| You need | A running Minecraft server you administer |
| Plan | Any — every tool here works on the free plan |
| Time | An afternoon to set up, then it runs itself |
1. Write the rules down before you need them
Moderation without written rules is just mood. Post a short, plain list — in your MOTD, a signed book at spawn, or a Discord channel — covering the handful of things that actually ruin servers: griefing and stealing, cheating and exploits, harassment, and spam. Say what happens when someone breaks each one (warn → mute/kick → temp-ban → ban). Players accept punishment they saw coming; they resent punishment that feels invented on the spot.
🎯 Good to know: Rules you can point back to are also what make appeals simple — "you broke rule 3, here's rule 3" ends most arguments before they start.
2. Ops discipline: give power slowly
The single most common way new servers implode is handing out operator (op) status too freely. A full op can do anything — change the world, ban anyone, run any command — so treat it like handing someone the keys to the building.
- Op from the panel, not the console guesswork. The Players page has an Operators tab where you add and remove ops without touching a file. (Full tour in Make your server yours.)
- Keep the op list short. You, and people you'd trust with your account. Everyone else gets permissions through a plugin, not op.
- Use a permissions plugin for real staff ranks. Op is all-or-nothing; a rank ladder isn't. LuckPerms lets a "helper" mute and kick without also being able to
/stopthe server or edit the world — the rank-ladder guide builds exactly this. Grant the narrowest power that lets someone do their job.
⚠️ Heads up: The
op-permission-levelproperty (on the Properties page) sets how much a plain op can do. Leave it at the default unless you understand each level — raising it hands every op more command-block and server power.
3. When grief happens: roll it back, don't rebuild it
Someone will eventually tear up spawn. If you planned ahead, this is a five-minute fix instead of a lost weekend. CoreProtect logs who placed and broke every block, so you can look up exactly what a player did and roll it back like it never happened:
/co lookup user:Griefer time:2h radius:30
/co rollback user:Griefer time:2h radius:30The catch is in the tense: CoreProtect can only undo what it was already recording. Install it on day one — it's insurance, and insurance only pays out if you had it before the fire. The full inspector-and-rollback workflow is in the CoreProtect guide.
4. Bans, done fairly
The Players page is your moderation desk. Its tabs cover the whole membership:
| Tab | What it's for |
|---|---|
| All Players | Everyone who's joined — op, ban, or whitelist from here |
| Whitelist | The allow-list of who may join (pairs with the white-list property) |
| Operators | Your op list (see above) |
| Banned Players | Account bans — add, review, and lift them |
| Banned IPs | Ban by address for ban-evaders who keep making new accounts |
You can ban from the panel or with the in-game /ban <player> <reason> command — always include a reason, because "banned" with no note is the thing you'll regret when they appeal in three weeks and nobody remembers why. Reach for an IP ban only for repeat evaders; addresses are shared and change, so it's a heavier, blunter tool than a normal ban.
💡 Tip: Match the punishment to the crime. A first-time spammer gets a mute, not a permaban. Save permanent bans for grief, cheating, and harassment — the things you actually don't want back.
5. An appeals process that stays sane
Give banned players one clear place to appeal — usually a Discord channel or a form — and one simple standard for lifting a ban. A workable rule of thumb:
- They say what they did (not "I did nothing").
- They acknowledge the rule they broke.
- First offences and honest apologies get a second chance; grief, cheating, and repeat offenders don't.
Decide it once, apply it the same way every time. The consistency is the point — inconsistent moderation breeds "the admins are unfair," which does more damage than any single griefer.
6. Keep your staff honest: the Activity log
The moment you have more than one person with power, you need a paper trail — not because you distrust your team, but because "who unbanned that guy?" needs an answer that isn't a guess. The Activity page records every action taken in the panel: files edited, settings changed, backups deleted, players managed — who did it, when, and from which IP. It's filterable by category and survives reinstalls, because it's panel history, not a server file.
This is the accountability layer for sub-users. When you invite staff to the panel, give each the least access they need (Console and Player permissions for a moderator; not Settings or Danger), and let the Activity log be the record if something goes wrong.
🎯 Good to know: In-game actions (chat,
/bantyped in the console) show in your server's own logs — open them from the Logs page. Panel clicks show in Activity. Between the two, almost nothing happens without a trace.
Incident cheat sheet
| Situation | First move |
|---|---|
| Spawn got griefed | /co lookup then /co rollback on the culprit |
| A player is spamming chat | Mute first (via a chat/essentials plugin), warn, escalate |
| Cheating suspected | Watch, gather evidence, then ban with a reason |
| A staffer misused power | Check the Activity log, then adjust their permissions |
| Ban evader on new accounts | IP-ban from the Banned IPs tab |
| "Was my ban fair?" | Point to the written rule they broke |