Open a server to people you don’t fully know and eventually someone breaks something they shouldn’t. CoreProtect quietly records who placed and broke every block, who opened which chest, and when - so a grief that would have meant restoring a backup (and losing everyone’s recent progress) becomes a ten-second, surgical rollback of just the damage.
Install it on day one
This is the one rule that matters: CoreProtect can only undo what it logged, and it starts logging the moment it’s installed. It cannot recover damage from before it was added. So put it on a Paper server early: Plugins tab → "CoreProtect" → Install → restart, and let it build history from the start.
Find out who did it
- 1Run /co inspect (or /co i) to toggle inspect mode.
- 2Left-click a broken block’s space, or the block where something was placed, to see a dated log of every change there and who made it.
- 3Right-click a chest, door or other container to see who accessed it and what they took.
- 4Run /co i again to turn inspect mode off.
Roll back the damage
- 1/co rollback u:Griefer t:2h r:20 - undo everything the player "Griefer" did in the last 2 hours within 20 blocks of you.
- 2Adjust the filters: t: is time (e.g. 30m, 1d), r: is radius, u: is the username. Leave u: off to roll back an area regardless of who.
- 3/co restore with the same filters re-applies the changes if you rolled back too much.
- 4Rollbacks happen live, block by block - players watching will see the damage repair itself.
Pair it with the Players tab
Once you’ve identified the culprit with /co inspect, deal with them from the Players tab - kick to interrupt, ban to keep them out - then roll back their work. Logging plus a whitelist for friend servers, or CoreProtect plus active moderation for open ones, keeps a survival world from ever being one bad guest away from disaster.