---
title: "CoreProtect Rollback Guide: Commands and Safe Restores | ZCS"
description: "Learn the CoreProtect commands for inspecting, looking up, rolling back and restoring blocks and containers without making a griefing incident worse."
url: "https://www.zcraftstudios.com/blog/coreprotect-rollback-commands-guide"
updated: "2026-10-20T07:16:50.972429+00:00"
source: "ZCraft Studios"
---

> Site index for AI agents: https://www.zcraftstudios.com/llms.txt (full reference: https://www.zcraftstudios.com/llms-full.txt). Every page is available as Markdown by adding `.md` to its URL or sending `Accept: text/markdown`.

1. [Home](https://www.zcraftstudios.com/)
2. [Blog](https://www.zcraftstudios.com/blog)
3. CoreProtect Rollback Guide: Commands and Safe Restores

[ All posts](https://www.zcraftstudios.com/blog)

# CoreProtect Rollback Guide: Commands and Safe Restores

ZCraft StudiosOct 19, 2026Updated Oct 20, 2026

Learn the CoreProtect commands for inspecting, looking up, rolling back and restoring blocks and containers without making a griefing incident worse.

## In this guide

- [The commands you will use](#the-commands-you-will-use)
- [Rollback parameters](#rollback-parameters)
- [A safe rollback workflow](#a-safe-rollback-workflow)
- [Roll back container and item changes](#roll-back-container-and-item-changes)
- [Limits and permissions](#limits-and-permissions)
- [Database size and purging](#database-size-and-purging)
- [Rollback does not replace backups](#rollback-does-not-replace-backups)
- [Related reading](#related-reading)

## CoreProtect Rollback Guide: Commands, Radius, Time and Safe Restores

_A rollback that is too wide or too old can undo legitimate builds. CoreProtect gives you the tools to prevent that, but only if you narrow the search first and preview the result._

## The commands you will use

| Command | Alias | Purpose |

| --- | --- | --- |

| `/co inspect` | `/co i` | Toggle inspector mode, then click or place blocks to see their history |

| `/co near [radius]` | | List nearby changes |

| `/co lookup` | `/co l` | Search the database without changing the world |

| `/co rollback` | `/co rb` | Undo matching changes |

| `/co restore` | `/co rs` | Re-apply changes that were rolled back |

| `/co undo` | | Reverse your most recent rollback or restore |

| `/co purge` | | Delete old log data |

| `/co status`, `/co reload` | | Check and reload the plugin |

## Rollback parameters

Rollback, restore and lookup share the same parameters:

| Parameter | Meaning | Example |

| --- | --- | --- |

| `u:` | Player or players (comma separated) | `u:Steve,Alex` |

| `t:` | How far back, using `w`, `d`, `h`, `m`, `s` | `t:2d5h` |

| `r:` | Radius, or a scope such as `#global` or `#worldedit` | `r:20` |

| `a:` | Action type | `a:block`, `a:+block`, `a:-block`, `a:container` |

| `i:` | Include only these blocks or items | `i:diamond_ore` |

| `e:` | Exclude these blocks or items | `e:stone,dirt` |

Action examples: `a:+block` is blocks placed, `a:-block` is blocks broken, and `a:container` covers items added to or removed from containers.

## A safe rollback workflow

1. **Inspect first.** Stand at the damage and use `/co i`. Click a few blocks to confirm who changed them and when.
2. **Look up before you roll back.** Run the exact command with `lookup` instead of `rollback`:

`/co lookup u:Steve t:3h r:30`

1. **Count or preview.** Current versions support `#preview` to show the result before applying it. Check your version's documentation for the flags it supports.
2. **Roll back narrowly.** Use the same parameters:

`/co rollback u:Steve t:3h r:30`

1. **Check the area.** Walk it, and ask staff or the build owner to confirm.
2. **Undo mistakes.** `/co undo` reverses the last action. `/co restore` re-applies changes with the same parameters.
3. **Log it.** Record the player, time window, radius and who ran the command.

Tip: if a griefer also edited other people's builds, add `a:-block` or `a:+block` so you only reverse what you intend.

## Roll back container and item changes

Use `a:container` to reverse items that were taken from or put into chests, barrels and other containers:

```
/co rollback u:Steve t:1d r:50 a:container
```

CoreProtect logs container transactions and, depending on your config, item drops and pickups. It is not a full inventory backup. To restore a player's inventory after death or a bug, use a dedicated inventory backup plugin such as InventoryRollbackPlus alongside CoreProtect.

## Limits and permissions

- Every command needs its own permission, such as `coreprotect.inspect`, `coreprotect.lookup`, `coreprotect.rollback`, `coreprotect.restore` and `coreprotect.purge`. Give rollback and purge only to trusted staff.
- The default config limits the maximum radius. Raise it carefully, and prefer repeating smaller rollbacks over one huge one.
- Large rollbacks on big databases take time and can cause lag. Run them off-peak.

## Database size and purging

CoreProtect uses SQLite by default, and MySQL is available for larger servers. The database grows quickly on busy worlds. Purge old data with a command such as `/co purge t:60d`, but take a backup first. CoreProtect enforces a minimum purge age, so check the current documentation. Purged data cannot be rolled back.

## Rollback does not replace backups

CoreProtect reverses logged actions. It cannot fix corrupted chunks, restore a deleted world, or recover data from before it was installed. Keep [regular backups](https://www.zcraftstudios.com/blog/minecraft-server-backup-strategy) and see [Chunk Corruption Recovery](https://www.zcraftstudios.com/blog/minecraft-server-chunk-corruption-recovery) for those cases.

## Related reading

- [Setting Up CoreProtect: Block Logging and Rollback](https://www.zcraftstudios.com/blog/coreprotect-block-logging-setup)
- [Dealing With Cheaters on a Minecraft Server](https://www.zcraftstudios.com/blog/minecraft-server-cheaters)
- [Minecraft Server Staff Training Checklist](https://www.zcraftstudios.com/blog/minecraft-server-staff-onboarding)

## Continue reading

- [Setting Up CoreProtect: Block Logging and Rollback](https://www.zcraftstudios.com/blog/coreprotect-block-logging-setup)
- [EssentialsX Commands Every Admin Should Know](https://www.zcraftstudios.com/blog/essentialsx-commands-cheat-sheet)

[ Previous guide EssentialsX Config Guide: Messages, Chat and Modules](https://www.zcraftstudios.com/blog/essentialsx-config-guide-messages-chat)[ Next guide EternalTags Setup: Chat Tags, Menus and Permissions](https://www.zcraftstudios.com/blog/eternaltags-plugin-setup-guide)