CoreProtect¶

CoreProtect (v23.1) is the server's block logging plugin. It silently records nearly every interaction that happens in the world -- who placed a block, who broke it, who opened a chest, and when it all happened. While it is primarily a staff tool, one of its most useful features is available to everyone: inspector mode.

Why Should I Care?

Ever come back to your base and found blocks missing? CoreProtect lets you click on any block to find out exactly who touched it and when. It is the fastest way to figure out what happened.

Inspector Mode¶

Inspector mode is the feature you will use most. It lets you click on any block to see its full history.

Toggling the Inspector¶

/co inspect

You can also use the shorthand:

/co i

Run the command once to enable inspector mode. Run it again to disable it.

Using the Inspector¶

Once inspector mode is active:

Left-click a block to see who broke something at that location.
Right-click a block to see who placed it.
Right-click a chest, furnace, or other container to see who added or removed items.

Each click shows you the player name, the action they performed, and how long ago it happened.

What Inspector Output Looks Like

After right-clicking a diamond block:

-- CoreProtect --
xeno9118 placed diamond_block 2 hours ago

After left-clicking an empty space where a block used to be:

-- CoreProtect --
griefer123 broke diamond_block 45 minutes ago

Remember to Turn It Off

Inspector mode stays active until you toggle it off with /co inspect again. You will not be able to interact with blocks normally while it is on.

Looking Up Changes¶

For more detailed searches, use the lookup command with parameters to filter results.

/co lookup u:<user> t:<time> r:<radius> a:<action> i:<include> e:<exclude>

You can also use the shorthand /co l instead of /co lookup.

Parameters¶

User -- u:<user> : Filter by player name. Separate multiple names with commas.

```
u:Notch
u:Notch,Steve
```

Time -- t:<time> : How far back to search. Use w (weeks), d (days), h (hours), m (minutes), s (seconds).

```
t:5d          (last 5 days)
t:2d12h       (last 2 days and 12 hours)
t:30m         (last 30 minutes)
t:1h-2h       (between 1 and 2 hours ago)
```

Radius -- r:<radius> : Search area around your current position.

```
r:10          (within 10 blocks)
r:#world      (entire current world)
r:#global     (all worlds)
```

Action -- a:<action> : Filter by action type (see list below).

```
a:block       (all block changes)
a:+block      (placements only)
a:-block      (breaks only)
a:container   (chest transactions)
```

Include -- i:<block> : Only show results for specific blocks or items.

```
i:diamond_ore
i:diamond_ore,gold_ore
```

Exclude -- e:<block> : Hide specific blocks or items from results.

```
e:stone
e:dirt,grass_block
```

Action Types¶

Here is every action type you can filter by:

Action	What It Logs
`block`	All block placements and breaks
`+block`	Block placements only
`-block`	Block breaks only
`chat`	Player chat messages
`click`	Player interactions (right-clicks)
`command`	Commands players have run
`container`	Items added to or removed from containers (chests, furnaces, etc.)
`inventory`	Inventory changes (item movements)
`item`	Item pickups and drops on the ground
`kill`	Entity kills (player killing mobs or players)
`session`	Player join and leave events
`sign`	Text placed on or removed from signs
`username`	Username change history

Modifiers¶

Add these to the end of any lookup or rollback command to change how results are displayed:

Modifier	What It Does
`#preview`	Preview the results without making any actual changes (useful for rollbacks)
`#count`	Show only the total number of matching results, not the details
`#verbose`	Show extra detail in the output
`#silent`	Suppress most feedback messages

Quick Nearby Lookup¶

Need a fast check of what happened around you? Use the near command:

/co near

This performs a quick lookup within a 5-block radius of your current position, showing recent changes by all players. It is the fastest way to investigate when you do not need specific filters.

Practical Examples¶

Here are some common situations and the commands to handle them:

Someone broke blocks at my base

Stand near the damage and run:

/co lookup t:3d r:10 a:-block

This shows every block broken within 10 blocks of you in the last 3 days.

Check who took items from a specific chest

Stand next to the chest and run:

/co lookup t:1d r:1 a:container

Or simply use inspector mode: /co i and then right-click the chest.

See everything a specific player did recently

/co lookup u:suspiciousplayer t:6h r:50

Shows all actions by that player within 50 blocks of you in the last 6 hours.

Find who placed diamond ore (possible x-ray)

/co lookup t:1d a:+block i:diamond_ore r:#world

Lists every diamond ore placement in the entire world over the last day.

Check recent activity around you

/co near

Quick 5-block radius scan -- perfect for a fast check when something looks off.

Rollback & Restore¶

Staff Feature

Rollback and restore commands are typically restricted to staff members. This section explains what they do so you understand what happens when staff investigate griefing on your behalf.

Rollback¶

/co rollback u:<user> t:<time> r:<radius>

A rollback reverses a player's actions. If someone broke your wall, a rollback puts those blocks back. If someone placed lava everywhere, a rollback removes it.

Restore¶

/co restore u:<user> t:<time> r:<radius>

A restore does the opposite of a rollback -- it re-applies a player's actions. This is used to undo a rollback if it went too far or was applied to the wrong area.

Undo¶

/co undo

Reverses the last rollback or restore you performed. Useful if something goes wrong.

Reporting Griefing

If you find griefing, use /co inspect to identify the player and time, then report it to staff. They can use rollback to fix the damage.