CoreProtect records block changes so a server moderator can investigate an unwanted edit and reverse a narrowly defined part of it. The useful habit is to inspect first: identify the player, time window, location and block type before removing anything.

CoreProtect lists three stone-brick placements matching the lookup filters.
Start with a small lookup
The following example concerns a few recently placed stone bricks. Stand beside the affected area and replace YourName with the actual player name:
/co lookup u:YourName t:10m r:4 a:+block i:stone_bricks
This searches the last ten minutes, within four blocks of your current position, for that player's stone-brick placements. a:+block selects placement actions. Read the returned locations and times before continuing; if the results include unrelated work, make the filters more specific.
The cottage example uses three stone-brick blocks across the entrance. The lookup found those placements before the rollback. A diamond block beside the entrance acts as a marker outside the selected material filter.

Before rollback: three stone-brick blocks form the cottage sill. The diamond marker is outside the chosen material filter.
Roll back only the matching placements
Stay at the same search position and use the same filters:
/co rollback u:YourName t:10m r:4 a:+block i:stone_bricks
In the cottage example, the three stone-brick sill blocks disappear, revealing the wooden floor beneath. The cottage frame and neighboring diamond marker stay in place. The radius follows the executing player's position, so return to the same search position before each command if you moved away to inspect the result.

After the targeted rollback: the three sill blocks are gone, while the cottage and diamond marker remain.
Restore the change if you need it back
To reverse that rollback, keep the same player, time, radius, action and material filters:
/co restore u:YourName t:10m r:4 a:+block i:stone_bricks
The same three stone-brick blocks return, rebuilding the sill. Check the result in the world before moving on to another report.

After restore: the same three-block sill is back at the entrance; the diamond marker is unchanged.
Install and use it carefully
Stop the Paper server, add the compatible CoreProtect plugin JAR to plugins, and restart. Logging needs to be active when a change happens; installing a logger afterward cannot recreate history it never recorded. Give investigation and rollback permissions only to people who need them.
If a lookup finds nothing, check the player's name, elapsed time, your location and whether you selected placements or removals. Begin with a lookup every time you change the filters. Keep ordinary server backups as well: a targeted block-history tool and a complete world backup solve different recovery problems.
Comments 0
Share what worked, ask for help or reply to another player.
Use your Modonix account to join the discussion and manage your comments.
Sign in to commentNo comments yet. Share what worked for you.