If someone griefs your Minecraft server, CoreProtect is what lets you figure out exactly who did it and undo the damage. It’s a block logging and anti-griefing plugin that tracks every block placement, break, and interaction across your server in real time. The two commands you’ll use most are /co lookup to investigate and /co rollback to reverse changes — but knowing how to use them correctly makes the difference between a clean rollback and accidentally wiping legitimate builds. This guide covers the full CoreProtect command set and how to roll back grief without touching the rest of your world.
Need a server to run CoreProtect on? Physgun’s Minecraft server hosting supports Spigot, Paper, and Purpur out of the box.
What Is CoreProtect?
CoreProtect is one of the most popular Minecraft plugins for grief prevention, moderation, and rollback management. It tracks:
- Block placements and breaks
- Chest and container interactions (including theft)
- Sign edits, paintings, fire, and explosions
- Entity kills and player deaths
- Piston activity and adjacent block updates
With logs this detailed, server staff can identify griefers, recover stolen items, and restore damaged builds without guessing. CoreProtect works on Spigot, Paper, Bukkit, and Purpur and supports multiple worlds. It uses SQLite storage by default, with optional MySQL support for large servers.
Installing CoreProtect
- Visit the CoreProtect plugin page and download the latest version
- Stop your server
- Drop the
CoreProtect.jarinto yourplugins/folder - Restart the server
Once loaded, CoreProtect is fully functional immediately — no additional configuration required to start logging. It also includes an automatic update checker so you know when newer versions are available.
CoreProtect Commands
All commands use the /co prefix (or /coreprotect) and can be run in-game or from the console. CoreProtect integrates with Spigot’s permission system so you can control what moderators and admins can access.
| Command | Description |
|---|---|
/co help | Shows detailed command information |
/co inspect | Click blocks to view their history |
/co lookup | Search logs using filters |
/co rollback | Reverse matching actions |
/co restore | Undo a previous rollback |
/co purge | Delete old log data |
/co status | Show plugin and database status |
Using /co lookup
The lookup command investigates griefing, theft, or any suspicious activity. Syntax:
Available filters:
| Filter | Description |
|---|---|
u: | Player/username |
t: | Time range (e.g. 2h, 30m, 1d) |
r: | Radius in blocks |
a: | Action type (e.g. block, container, kill) |
b: | Block type |
Example — look up everything Steve did in the last 2 hours within 20 blocks:
You can filter by multiple users, exclude users, or narrow results to a specific block type to zero in on exactly what happened.
Using /co rollback
The rollback command reverses all actions that match your filters. It uses the same filter syntax as lookup:
Example — roll back all block changes in the last 30 minutes within 10 blocks:
Always run a /co lookup with the same filters first to preview what will be affected before committing a rollback. If you roll back too much, use /co restore with the same filters to reverse it.
For large grief incidents affecting a wide area, you can increase the radius or omit it to target a specific player’s actions across the whole world.
Tips for Effective Use
- Inspect before rolling back — use
/co inspectto click individual blocks and understand the scope of damage before running a broad rollback - Be specific with time ranges — the tighter the time range, the less chance of reverting legitimate builds that happened near the grief
- Use
/co restoreas a safety net — if a rollback catches unintended blocks, restore brings them back - Purge old data regularly —
/co purge t:30dremoves logs older than 30 days to keep your database lean on large servers