CoreProtect Commands for Minecraft

CoreProtect is a popular Minecraft plugin for controlling griefing on your server. It uses a powerful data logging system which can be used to restore any griefer damage.

Typically staff members of a server are able to use this plugin to inspect, lookup, and rollback almost anything. The commands can be used to replace or remove blocks, place items back into chests, and even undo player commands and messages.

CoreProtect Commands

Due to the nature of such an expansive plugin, CoreProtect commands can be a bit tricky to use. Let’s take a look at them, and go over some usage examples!

CoreProtect Commands

  • /co help
  • /co inspect
  • /co rollback u:<user> t:<time> r:<radius> a:<action> b:<blocks> e:<exclude>
  • /co restore u:<user> t:<time> r:<radius> a:<action> b:<blocks> e:<exclude>
  • /co lookup u:<user> t:<time> r:<radius> a:<action> b:<blocks> e:<exclude>
  • /co purge t:<time>
  • /co near
  • /co undo
  • /co reload
  • /co status
/co help

Displays a list of commands within your game.

/co inspect

Toggles the use of the inspector tool. A shortcut /co i is also available to use.

/co rollback u:<user> t:<time> r:<radius> a:<action> b:<blocks> e:<exclude>

Used to perform a rollback. You can specify tons of parameters here to make your rollback as specific as needed. A shortcut /co rb is also available to use.

Most of these parameters (anything inside of < > brackets) are optional. You do not need to enter each one, but you can also use all of them at once. See the parameters section for more info on these.

/co restore u:<user> t:<time> r:<radius> a:<action> b:<blocks> e:<exclude>

Used to “restore” or undo a rollback that may have gone wrong. It works the same as a rollback, but in reverse. A shortcut /co rs is also available.

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

This command is used to lookup any of the available parameters within your database. It will return a list of whatever you’ve decided to search.

If multiple pages of data is returned, use /co lookup <page> to switch pages. For example:

  • /co lookup 3 (switches to page 3)

A shortcut /co l is also available.

/co purge t:<time>

Because the plugin stores data on almost everything in your server, it will eat up lots of HDD space as your server grows. It’s important to clean out your data from time to time. The most you can purge via game command is 30 days, with the following command:

  • /co purge t:30d

This will remove all saved data except the most past 30 days. You can remove more data when entering the command from the console.

/co near

Performs an automatic lookup within 5 blocks of you.

/co undo

Reverts your most recent rollback or restore command. If you accidently enter something incorrectly, use this to immediately undo it!

/co reload

Reloads the plugin configuration file. If you make changes to the config file, you can use this command to update the plugin without restarting your server completely.

/co status

Shows the current status of the plugin within your server. Useful for debugging purposes.


A parameter is anything inside of < > brackets that you see above. Many CoreProtect commands allow you to enter these parameters for a more specific command. All available options for these parameters can be found below.


This specifies the user in your server that the rollback is for. It’s as simple as entering the person’s username.


Enter the amount of time you wish to rollback to. This allows for time units in weeks (w), days (d), hours (h), minutes (m), and seconds (s).

You can use as many or as few of these in your command. Decimals can also be used. They are formatted like this:

  • t:3w,4d,6h,7m,8s (3 weeks, 4 days, 6 hours, 7 minutes, 8 seconds)
  • t:2.50h,12m (2 and a half hours, 12 minutes)


This is the area where you want to perform the rollback. There are a number of different ways you can enter this:

  • By number of blocks – r:10 (10 blocks)
  • By world – r:#my_cool_world
  • By a selected WorldEdit – r:#we
  • Rollback globally – r:#global


There are a number of different things you can rollback. This is the parameter which you choose what you’d like to rollback. Below is a list of all possible actions to rollback:

  • a:block (blocks placed/broken)
  • a:+block (blocks placed)
  • a:-block (blocks broken)
  • a:click (player interactions)
  • a:container (items taken from or put in chests)
  • a:+container (items put in chests)
  • a:-container (items taken from chests)
  • a:kill (mobs/animals killed)
  • a:chat (messages sent in chat)
  • a:command (commands used)
  • a:session (player logins/logouts)
  • a:+session (player logins)
  • a:-session (player logouts)
  • a:username (username changes)


Here you can specify if you want the command to only remove certain blocks. In order to use this, you’ll need to know each block’s specific ID. You can use this tool to find the “Legacy ID” for any block in Minecraft.

If you wanted to limit this rollback to only dirt blocks and stone blocks, you would enter it like this:

  • b:3,1 (3 is the ID for dirt, 1 is the ID for stone)


Similar to the parameter above, but used for excluding certain blocks. It works the same exact way, and is useful for doing rollbacks while allowing certain blocks to remain.

If you wanted to do a complete rollback except for obsidian blocks, you would enter it like this:

  • e:49 (49 is the ID for obsidian)


You can use a hashtag (#) at your rollback command to do a few different things. It’s very useful for previewing and accessing information about your rollbacks.

You can use the following hashtags:

  • #preview (shows a preview of what will happen when using the specified command before you actually enter it – great for testing!)
  • #count (shows the number of affected rows in your database from the rollback)
  • #silent (displays less information about your rollback)
  • #verbose (displays extra information about your rollback)