CoreProtect
Block logging and rollback tool. Tracks who placed/broke blocks, container transactions and chat. Roll back grief instantly.
AdminWhat is CoreProtect?
CoreProtect is the standard block-logging and rollback tool. It records who placed and broke every block, every container transaction, sign edits, and more into a fast database, then lets staff inspect any block's history and roll back damage by player, area and time window. A griefer's entire session can be reversed in one command, and restored again if needed. Inspection mode shows the log for any block you click. It is lightweight, supports SQLite or MySQL, and is valued for being fast enough to log busy servers without noticeable lag.
Who it's for: Every survival, SMP and economy server that needs grief recovery and an audit trail of who did what. Treated as essential staff infrastructure rather than an optional extra. It is built and maintained by Intelli and sits in the admin category.
Key features of CoreProtect
- Block logging
- Rollback and restore
- Container transaction logging
- Chat logging
- Per-user lookup
- Radius-based rollback
- Time-based queries
- SQLite and MySQL support
How to install CoreProtect
CoreProtect runs on Bukkit, Spigot or Paper servers. Intelli maintains CoreProtect for current Spigot/Paper versions; recent builds cover modern Minecraft while logging remains compatible across a wide range.
- 1Stop your server, or have it ready to restart. Always back up your world and plugins folder before adding a new plugin.
- 2Download CoreProtect.jar (a build matching your server version) and place it in your server's /plugins folder.
- 3CoreProtect has no required dependencies, so it runs on its own once the jar is in place.
- 4Start the server fully. CoreProtect generates its configuration files on first launch — stop the server, edit them to taste, then start again.
- 5Confirm it loaded by checking the console for CoreProtect on startup, or by running one of its commands in-game.
Note: Drop CoreProtect.jar into /plugins and restart; it creates its config and database automatically (SQLite by default, or point it at MySQL in config.yml for networks). It only logs activity from the moment it is installed — earlier grief is not recorded — so install it early.
CoreProtect commands and permissions
Main commands
/co inspect- Toggles inspector mode; left-click a block to see who broke it, right-click to see what was placed and when.
/co rollback- Reverses changes filtered by player, radius and time — for example /co rollback u:griefer t:2h r:30.
/co restore- Re-applies changes that were rolled back, undoing an over-broad rollback.
/co lookup- Searches the logs without changing the world, to investigate before rolling back.
Permission nodes
coreprotect.inspect- Allows using inspector mode.
coreprotect.rollback- Allows performing rollbacks.
coreprotect.restore- Allows restoring rolled-back changes.
coreprotect.lookup- Allows querying logs without modifying the world.
CoreProtect FAQ
How do I roll back grief with CoreProtect?
Use /co rollback with filters: u: for the username, t: for the time span and r: for the radius, e.g. /co rollback u:Griefer t:1h r:20. CoreProtect reverses that player's changes in the area over that window. Run /co lookup with the same filters first to preview what will change.
Can I undo a rollback if I made it too large?
Yes. /co restore re-applies what a rollback removed, using the same filter syntax. Because rollbacks and restores are symmetric, you can iterate safely — preview with lookup, roll back, and restore if you scoped it wrong.
How do I see who broke a block?
Run /co inspect to enter inspector mode, then left-click the broken block (or the space where it was) to see who removed it and when, and right-click a block to see placement history. Run /co inspect again to leave inspector mode.
Does CoreProtect log activity before it was installed?
No. It can only log events that happen after it is running, so it cannot recover grief that occurred before installation. This is why it is recommended to install CoreProtect on day one of a server, before any building or damage takes place.
Should I use SQLite or MySQL?
SQLite (the default) is fine for a single server and needs no setup. Use MySQL when you run a network and want shared or external storage, or when the log database grows very large and you want it off the game server. Configure the choice in CoreProtect's config.yml.
Features
- Block logging
- Rollback and restore
- Container transaction logging
- Chat logging
- Per-user lookup
- Radius-based rollback
- Time-based queries
- SQLite and MySQL support
Commands
/co inspect/co rollback/co restore/co lookup/co purge/co reloadPermissions
coreprotect.inspectcoreprotect.rollbackcoreprotect.restorecoreprotect.lookupcoreprotect.purge