Setting Up CoreProtect: Block Logging and Rollback

Setting Up CoreProtect: Block Logging and Rollback

Not "who do we think did it" — an actual log of every block change, with a command to undo it.

CoreProtect logs block placements, breaks, container access, and more, with a timestamp and the player responsible. When something gets griefed — or a build just needs reverting after a mistake — CoreProtect can both show what happened and roll it back automatically.

Install CoreProtect

Drop CoreProtect.jar into plugins/ and restart. It starts logging immediately using its own SQLite database by default — no config changes needed to begin logging.

Looking Up What Happened in an Area

Stand near the affected area and run:

/co inspect

This gives you a tool (by default, your held item) that shows block history when you left-click a block — who placed or broke it, and when.

Looking Up a Specific Player

/co lookup player <name> time:1h

shows everything that player did in the last hour, across their logged radius. Add action:block or action:container to narrow it to a specific type of action.

Rolling Back Damage

/co rollback player <name> time:30m radius:50

reverts every logged change by that player within 50 blocks of your current location, in the last 30 minutes. This is the core feature — most other logging plugins only show history, not revert it.

Restoring a Rollback (Undo the Undo)

/co restore player <name> time:30m radius:50

reapplies whatever a rollback just removed — useful if a rollback accidentally reverted legitimate changes along with the griefing.

Logging Container Access

CoreProtect also logs chest/container opens and item transactions by default, which is often how item theft between players gets resolved — /co lookup with action:container surfaces exactly who took what from a shared chest.

Performance Considerations

On a very active, long-running server, the logging database can grow large. /co purge t:30d purges logs older than 30 days, trading long-term history for database size — a reasonable tradeoff on servers without a strong moderation need to reference very old incidents.

A Few Things Worth Knowing

• CoreProtect logs by default as soon as it's installed — there's no separate "enable logging" step.
• Rollback and restore both affect a radius around your current location, not the entire world — standing in the right spot before running the command matters.
• MySQL storage is supported and recommended for very high-traffic servers, configured the same way most other plugins switch storage backends.