CoreProtect, Rollback Specific Player Only

When You Need a Player-Specific Rollback

A griefer joins, breaks 500 blocks, lava-floods a build, and leaves. You need to undo their damage without touching anything other players built in the same area. This is exactly what a coreprotect rollback specific player command handles. Instead of rolling back an entire region (which would erase legitimate changes by other players), you target one username and reverse only their actions.

Basic Player Rollback Command

The core command structure is straightforward:

/co rollback u:griefer_name t:1h

This reverses every action by griefer_name in the last hour, server-wide. The u: parameter is the user filter, and t: sets the time window. You can use time formats like t:30m, t:2h, t:1d, or compound values like t:1h30m.

Adding a Radius Filter

If the griefer only damaged one area, add a radius to limit the rollback scope:

/co rollback u:griefer_name t:2h r:50

This rolls back the player's actions within 50 blocks of your current position. For large builds, increase the radius. For pinpoint precision, stand at the center of the damage.

Filtering by Action Type

Sometimes a player broke blocks but also placed blocks (like cobblestone pillars or lava). You can filter by action type to handle each separately:

# Undo only block breaks
/co rollback u:griefer_name t:2h a:block r:100

# Undo only block placements (removes cobble towers, lava, etc.)
/co rollback u:griefer_name t:2h a:+block r:100

The a:block parameter targets broken blocks (restores them), while a:+block targets placed blocks (removes them). Running both commands sequentially gives you a complete targeted cleanup.

Preview Before You Commit

Always preview a rollback before executing it. Add #preview to the end of any rollback command:

/co rollback u:griefer_name t:2h r:50 #preview

CoreProtect shows you what would change without actually modifying any blocks. Walk around and inspect the preview. If it looks correct, run the same command without #preview to commit. If you accidentally commit a bad rollback, use /co restore with the same parameters to reverse it.

Inspecting Before Rolling Back

Before issuing a rollback, use the inspect tool to verify the damage:

/co inspect

Click any block to see its history. This confirms which player caused the damage, when it happened, and what the original block was. It prevents you from rolling back the wrong player or the wrong time window. For a full walkthrough of inspection and rollback workflows, see the CoreProtect rollback guide.

Handling Container and Inventory Theft

Block rollbacks do not automatically restore stolen chest contents. For container theft, use:

/co rollback u:griefer_name t:2h a:container

This reverses item additions and removals from chests, furnaces, hoppers, and other containers. Run this separately from block rollbacks to keep the operations clean. A full coreprotect rollback specific player approach covers both blocks and containers.

Multi-Player Rollbacks

If multiple players griefed together, you can specify more than one username:

/co rollback u:player1,player2,player3 t:3h r:100

CoreProtect reverses all three players' actions in one operation. After the rollback, use your ban system to prevent repeat offenses.

Exclude Blocks from the Rollback

Sometimes a griefer placed valuable blocks alongside destructive ones (like placing diamond blocks as bait near TNT damage). You can exclude specific block types from the rollback with the e: parameter:

/co rollback u:griefer_name t:2h r:50 e:diamond_block,gold_block

This reverses the player's actions but skips any diamond or gold block changes. Useful for preserving legitimate contributions while cleaning up the rest.

Summary

A coreprotect rollback specific player operation is the surgical approach to grief recovery. Use /co inspect to identify the culprit, preview with #preview, then roll back with user, time, radius, and action filters. Always handle block and container rollbacks separately for the cleanest results.

Full config access on every plan: Astroworld Hosting, NVMe SSDs, Pterodactyl panel.

Questions about CoreProtect

What exactly is CoreProtect doing here?

A griefer joins, breaks 500 blocks, lava-floods a build, and leaves.

What do you type for CoreProtect?

This is exactly what a coreprotect rollback specific player command handles. This guide uses /co rollback u:griefer_name t:1h.

What does this guide say about basic player rollback command?

You need to undo their damage without touching anything other players built in the same area.

CoreProtect: what does preview before you commit mean here?

This is exactly what a coreprotect rollback specific player command handles.