Server rules and moderation: the plugins that protect your community

Most Minecraft servers do not die of lag or too few players, but of what happens between players: a demolished base nobody can trace, a chat that derails in the evening, a moderator who gives a friend a second chance and a stranger none. Moderation is not a matter of writing more rules, but of getting three things right: being able to see what happened, being able to punish fairly and visibly, and distributing power precisely. This article lists the plugins and the agreements that do that, even if you manage the server alone.

First see what happened: CoreProtect

CoreProtect records every placed and broken block, every chest opened and every item moved, with who did it and when. With /co inspect you click a block and see its history; with /co rollback you roll back the damage of a player in an area over a time span, without touching the rest of the world. That turns griefing from a disaster into a two-minute inconvenience, and it makes arguments unnecessary: the log does not lie.

Two settings matter. Set the retention (purge) to at least thirty days so you can also investigate late reports, and use a separate database (MySQL) once your server is larger than a few hundred chunks; the default SQLite becomes slow then. CoreProtect costs little CPU but does use storage, so keep an eye on disk space.

Preventing damage instead of repairing it

Rolling back is nice, preventing is better. With GriefPrevention or Lands players claim their own area where others cannot build; with WorldGuard you protect spawn and public buildings and set rules per region such as no PvP, no explosions or no mob spawning. Combine the two: WorldGuard for the server-wide regions you manage, a claim plugin for the players' areas. The guide for WorldGuard is in our knowledge base: installing WorldGuard.

Punishing fairly: LiteBans or AdvancedBan

A ban through the vanilla command /ban works, but has no history, no temporary variant and no reason the player sees. LiteBans (paid) and AdvancedBan (free) add exactly that: temporary bans and mutes, escalating warnings, a reason shown at login, IP bans for persistent cases and a history per player every moderator can view. Important for fairness: all moderators see the same history and the reason is attached, so a second chance is not a matter of friendships.

Create a fixed punishment ladder and put it in your rules: warning, one-hour mute, one-day mute, three-day temporary ban, permanent ban. Deliberate griefing and cheating skip the ladder. That way every moderator knows what to do and every player knows what to expect.

Distributing power: LuckPerms and roles

LuckPerms is the standard for permissions and the place where you set up moderation roles. Create at least three layers: helper (may mute and warn, may not ban), moderator (may ban temporarily and roll back with CoreProtect), admin (permanent bans, plugins, world management). Give nobody OP unless truly necessary: OP bypasses every permission and every log line, and a helper with OP is an accident waiting to happen. Most servers that get "hacked" were in reality wrecked by someone with too many rights.

Also lay down in LuckPerms what moderators may not do: no creative in survival, no giving items, no teleporting to players without reason. Rights that do not exist cannot be abused.

The chat: filters and context

A chat filter (through ChatSentry, EssentialsX or a modern chat plugin) catches the worst: swearing, links to other servers, caps and spam. Do not tune it too aggressively: a filter that blocks normal sentences annoys more than it helps. More important than the filter is that moderators see the context: a chat log per player, and the rule that you only punish after reading once what was said before the incident. For larger servers a link with Discord (DiscordSRV) is handy: the chat is then also visible to moderators who are not logged in.

Rules people actually read

Ten rules on a sign at spawn are not read; five rules in plain language are. A set that works on most survival servers:

1. Do not build on other people's land and do not break anything that is not yours.
2. No cheats, hacks or xray; not even "just having a look".
3. Chat as you would talk at a table with strangers.
4. No advertising for other servers.
5. Listen to moderators; disagree? Open a ticket, no discussion in chat.

Put the punishment ladder underneath and refer to the rule number with every punishment. Players accept a mute far more easily when the reason is "rule 3" than when it is "because the mod said so".

Handling an incident in five steps

When something goes wrong, a fixed order helps. One: ask the reporter for coordinates and a time, and look yourself with /co inspect or in the chat log. Two: temporarily hold the suspected culprit (a short mute or freeze) so they do not continue while you investigate. Three: roll back the damage with /co rollback for exactly that player, area and time span. Four: punish according to the ladder and record the reason in the ban system with the rule number. Five: tell the reporter what happened. That last step is forgotten most often and is the reason players get the feeling that reporting is pointless.

Routines for the owner

• Daily, five minutes: go through the ban list and warnings, check that moderators are consistent.
• Weekly: check CoreProtect storage, test a backup, clean up claims of departed players.
• Monthly: update plugins on a test server, review permissions, reread the rules with the moderators.
• Cheap Minecraft hosting: what actually matters when you compare
• Making money with your Minecraft server: what the EULA allows

Backups remain the last line of defence; even with CoreProtect you want to be able to restore yesterday's world if a moderator accidentally runs the wrong rollback. How to set that up is in a backup strategy for your Minecraft server, and the technical side of accounts, whitelist and anti-cheat in securing your server.

The basic set in one go

CoreProtect, WorldGuard plus a claim plugin, LiteBans or AdvancedBan, LuckPerms and a chat filter: five plugins, together a few hundred megabytes of RAM, and the difference between a server that empties after the first griefer and a community that stays for years. If you host with us, you install them through the panel in a few minutes; our Minecraft servers have room to scale per gigabyte as the community grows.