Setting Up CoreProtect for Grief Logging

CoreProtect is a logging and rollback plugin that records almost everything that happens on your server - block placements and breaks, container transactions, chat messages, player actions, and more. If a player griefs your spawn or steals from a chest, CoreProtect lets you find out exactly who did it and undo the damage with a single command.

This is one of the most important plugins you can install on a server, and we recommend setting it up before opening your server to the public.

Installing CoreProtect

The easiest way to install CoreProtect is through the built-in Plugin Installer in the Game Panel:

Log in to the Game Panel
Select your server
In the left menu, click Game then Plugins
Search for CoreProtect and click install
Restart your server

Alternatively, you can download CoreProtect manually from SpigotMC and upload the .jar file to your plugins folder.

On first startup, CoreProtect creates a plugins/CoreProtect/ folder containing its configuration and a local SQLite database. No other setup is required - it starts logging everything immediately.

Important: CoreProtect only logs events from the moment it is installed. It cannot recover data from before you installed it, so install it early.

Using the Inspector Tool

The Inspector is the easiest way to look up information about a specific block or container.

In game, type /co inspect (or /co i for short) to toggle the inspector on
Left-click a block to see who broke the block that used to be there
Right-click a block to see who placed it. For containers like chests and hoppers, this also shows the full history of items taken and placed
Type /co i again to turn the inspector off

The inspector is great for quickly answering questions like "who broke this wall?" or "who took items from this chest?".

Rolling Back Grief

If a player has griefed an area, you can undo their actions with the /co rollback command (also aliased as /co rb).

The basic format is:

/co rollback <parameters>

Common Parameters

u: - The username (for example u:PlayerName)
t: - Time range (for example t:1h for the last hour, t:30m for 30 minutes, t:2d for 2 days)
r: - Radius in blocks from your current location (default is 10)
w: - World name (for example w:world_nether)
a: - Action filter (for example a:-block for only broken blocks)

Example Commands

Roll back everything a player did in the last hour within 20 blocks of where you are standing:

/co rollback u:Griefer t:1h r:20

Roll back all actions a player did in the last 2 hours across the entire world:

/co rollback u:Griefer t:2h r:#global

Only roll back blocks they broke (not placed) in the last day:

/co rollback u:Griefer t:1d a:-block

Undo creeper damage from the last 30 minutes across the world:

/co rollback u:#creeper t:30m r:#global

Preview Before You Apply

Before running a large rollback, you can preview it first by adding #preview to the end:

/co rollback u:Griefer t:1h r:20 #preview

This shows what would be changed without actually changing anything. We strongly recommend previewing any large rollback.

Looking Up Without Rolling Back

If you want to see what happened without undoing anything, use /co lookup (or /co l). It uses the same parameters as rollback but does not change anything.

/co lookup u:PlayerName t:1d
/co lookup t:1h r:10 a:container

This is useful for investigating suspicious activity before deciding whether to act.

Undoing a Rollback

If a rollback went wrong or was too broad, you can reverse it with /co restore (or /co rs). Use the exact same parameters you used for the rollback:

/co restore u:Griefer t:1h r:20

You can also use /co undo as a shortcut to reverse the last rollback or restore you ran.

Common Use Cases

Someone Griefed My Spawn

Go to the griefed area
Preview the rollback first: /co rollback u:Griefer t:3h r:50 #preview
If the preview looks correct, run the real command: /co rollback u:Griefer t:3h r:50
If you need to cover a wider area, use r:#global instead of a number

Someone Stole from a Chest

Stand near the chest
Turn on the inspector: /co i
Right-click the chest to see the full history of items added and removed
If you want to roll back the theft: /co rollback u:Thief t:1d a:-container r:10

Who Broke This Block?

Turn on the inspector: /co i
Left-click the block (or the air where the block used to be)
CoreProtect will show you who broke it and when

Key Permissions

If you are using LuckPerms, you will want to give your staff these permissions:

coreprotect.inspect - Use the inspector tool
coreprotect.lookup - Run lookup commands
coreprotect.rollback - Roll back actions
coreprotect.restore - Restore rolled-back actions

You can also grant coreprotect.* to give full access to all CoreProtect commands, but this should only be given to trusted admins.

Maintaining Your Database

CoreProtect's database will grow over time. If it gets very large, you can purge old entries with /co purge:

/co purge t:30d

This deletes everything older than 30 days. Run this during quiet times, as purging a large database can temporarily slow your server down.

Common Issues

The Plugin Did Not Catch the Grief

CoreProtect only records events from the moment it was installed. If the grief happened before you installed the plugin, it cannot recover the data. Install CoreProtect as soon as you set up a new server.

My Rollback Did Not Cover the Whole Area

The default radius is only 10 blocks. Use a larger radius (for example r:50) or r:#global to cover the entire world.

The Rollback Did Too Much

Use /co restore with the same parameters to reverse it, or use /co undo to reverse your last rollback. Always use #preview on large rollbacks in future.

Rolling Back Creepers or TNT

To roll back explosions from entities, use u:#creeper or u:#tnt instead of a player name.

Having Trouble Setting Up CoreProtect?

Feel free to reach out to us and we can help:

Support Ticket
Discord Server - use the /support command
Email: [email protected]