How to stop griefing on your Minecraft server
Griefing is someone breaking, stealing or burning what others built. On a small friends server it is rare; the moment an address gets shared around, it is not. Good protection has three layers: keep the wrong people out, make it hard to damage things, and make every bit of damage undoable.
Layer 1: keep the wrong people out
- Whitelist: on a private server, the strongest protection there is. Only names you add can join. See whitelist and operator levels.
- Few operators: every op can undo all your protection. Give op to yourself; give everyone else a group with only the commands they need.
- Online mode on:
online-mode=trueinserver.propertiesmakes sure people are who they say they are. Turning it off lets anyone use any name, including yours.
Layer 2: let players protect their builds
On a server with more than a handful of players, claims are the answer. A claim is an area only its owner, and people they trust, can change.
| Server type | Claims tool |
|---|---|
| Paper, Purpur, Spigot | GriefPrevention, or Lands for towns and nations |
| Forge or NeoForge packs | FTB Chunks or Open Parties and Claims, often already in the pack |
| Fabric | Open Parties and Claims, or a claims mod made for Fabric |
With GriefPrevention, players claim land by clicking two corners with a golden shovel, and let friends build with /trust Name. They earn more claim area the longer they play, which rewards regulars and limits newcomers.
Layer 3: make damage undoable
CoreProtect keeps a diary of the world: who placed or broke which block, who opened which chest and took what, and at what time. When something goes wrong, you roll it back as if it never happened.
- Install CoreProtect from the catalog in the Plugins tab and restart. It starts logging right away; it cannot see what happened before it was installed.
- To see who changed a block, type
/co inspectand click the block. Type it again to stop. - To undo everything one player did in the last day, anywhere:
/co rollback u:Name t:1d r:#global. - Made a mistake?
/co restorewith the same options puts it back.
On Fabric, the mod Ledger does the same job with similar commands.
Keep backups as well. CoreProtect undoes the work of a few players; a backup in the Backups tab saves you when something bigger breaks, like a corrupted region.
Game rules that prevent accidents
Not all damage comes from players. In the World tab under Game rules you can switch off:
- Mob griefing: creepers stop blowing holes and endermen stop picking up blocks. Note that villagers also stop farming with it off.
- Fire spread: lightning and lava no longer burn down wooden builds.
When it happens anyway
- Look up who did it with
/co inspector/co lookup u:Name t:2h. - Ban them from the Players tab so they cannot come back while you clean up.
- Roll back their changes with CoreProtect.
- Check chests: rollbacks also return taken items to their containers.
Questions
Can CoreProtect undo griefing from before it was installed?
No. It only knows what it logged. For damage from before, restore a backup, or rebuild. Install it on day one.
Does CoreProtect use a lot of storage?
Its database grows with activity. On a busy server, set it to purge entries older than a few weeks with /co purge t:30d, so the log does not fill your storage.
Is a whitelist enough for a friends server?
Usually, yes. Add CoreProtect anyway: accidents happen between friends too, like a creeper or a joke that went too far.
Checked against CoreProtect and GriefPrevention on Paper for Minecraft Java 26.2, September 2026. Written by the Cheapest Minecraft Hosting team, updated .