Skip to main content
Plugins

Minecraft CoreProtect Rollback Guide

Use CoreProtect to log every block action and roll back grief on your Minecraft server, install, lookup, rollback and tips.

7 min read9 sectionsJava & Bedrock

CoreProtect logs every block place, break, container access and chat message. When grief happens, you roll it back, usually in seconds. This guide covers install, lookup, rollback, and how to use CoreProtect without nuking innocent edits.

1. Install

Download CoreProtect from SpigotMC. Drop into plugins/, restart. Default storage is SQLite. For big servers, switch to MySQL in plugins/CoreProtect/config.yml.

2. The wand

/co inspect

Toggles inspector mode. Left-click a block to see who placed it; right-click an air block to see what was there before.

3. Lookup before rollback

Always check before rolling back:

/co lookup u:Griefer t:6h r:50 a:block

Reads: actions by user Griefer, in the last 6 hours, within 50 blocks of you, of type block. Other useful flags:

  • i:diamond_ore, only diamond ore
  • e:break, only breaks
  • a:container, only chest accesses
  • w:world, only in this world

4. Rollback

Same flags, replace lookup with rollback:

/co rollback u:Griefer t:6h r:50

This UNDOES the changes, broken blocks return, placed grief is removed.

5. Restore (undo a rollback)

/co restore u:Griefer t:6h r:50

6. Container logging

If you suspect chest theft:

/co lookup u:Griefer a:container t:24h

Shows what items were taken from which chest. Doesn't return the items but tells you exactly what to /give back.

7. Performance

CoreProtect's biggest cost is disk. SQLite handles small servers fine; a 50-player server should be on MySQL with a fast NVMe disk. Set retention in config:

purge:
  enabled: true
  default-time: 30d

Then schedule /co purge t:30d weekly.

8. Common pitfalls

  • Rolling back too wide a radius, use the smallest r: that fits the affected area.
  • Rolling back time including legitimate edits, ALWAYS lookup first.
  • Not logging container access in config, check blacklist: isn't excluding the container types you care about.
  • Using CoreProtect as a backup, it's not. Keep file-level backups too.

Want to see all this in action? Astroworld MC runs a custom-built economy survival server with custom bosses, eternal enchants, crates and an auction house. Join at astroworldmc.com, IP play.astroworldmc.com, Java + Bedrock crossplay.

Questions about Minecraft CoreProtect Rollback

What exactly is Minecraft CoreProtect Rollback doing here?

CoreProtect logs every block place, break, container access and chat message.

What are the numbers behind Minecraft CoreProtect Rollback?

Always check before rolling back: Reads: actions by user Griefer, in the last 6 hours, within 50 blocks of you, of type block.

Which command does Minecraft CoreProtect Rollback use?

CoreProtect logs every block place, break, container access and chat message. This guide uses /co inspect.

Where does Minecraft CoreProtect Rollback store its settings?

For big servers, switch to MySQL in plugins/CoreProtect/config.yml.

What should you avoid while doing Minecraft CoreProtect Rollback?

Other useful flags: i:diamond_ore, only diamond ore e:break, only breaks a:container, only chest accesses w:world, only in this world Same flags, replace lookup with rollback: This UNDOES the changes, broken blocks return, placed grief is removed.

Minecraft CoreProtect Rollback Guide: Use CoreProtect to log every block action and roll back grief on your Minecraft server, install, lookup, rollback and tips.
Minecraft CoreProtect Rollback Guide, from the Plugins guides on Astroworld.

Blocks and items in this guide

Diamond in MinecraftDiamond

Diamond is named in the Minecraft CoreProtect Rollback guide above. Look them up in the item database.

More guides on this site

More Plugins Guides

Related Tools & Databases