Get started

Free trial Try any game free for 3 days. No card needed. Start a free trial Start a free trial

Game servers

All games

Guides / Minecraft / Plugins

Roll back griefing with CoreProtect (no 26.3 build yet)

CoreProtect has no 26.3 build yet. Its 26.2 build may still work but can cause bugs or lag. How to install it safely, then look up and roll back griefing.

Updated , checked on Minecraft Java 26.3

CoreProtect had no build for Minecraft 26.3 when this was checked on 11 October 2026. Its newest release, 24.1, is made for 26.2. An older build like that can still work on 26.3, but it can also cause bugs or lag, so take a backup first. Once it runs, type /co i to turn on the inspector and click a block to see who placed or broke it, and /co rollback u:Name t:1h r:20 reverts what that player did in the last hour within 20 blocks of you.

CoreProtect logs block changes, chests, kills, chat and commands, so you can answer “who did this?” after the fact. It is a plugin, so you need Paper or Purpur.

Check your Minecraft version first

CoreProtect 24.1 is on Modrinth and Hangar, made for Minecraft 26.1 to 26.2. The panel’s Add-ons page only offers builds made for your server’s exact version, and its search leaves out plugins that have none, so on a 26.3 server CoreProtect does not show up there. The SpigotMC entry, “CoreProtect Community Edition”, says “No build of this is made for this server’s version and loader.”

Your options on 26.3:

  • Use the 26.2 build anyway. Plugins often keep working on a newer Minecraft version, but an older build can cause bugs or lag, or fail to load. Upload it by hand: see use a build made for an older version below.
  • Wait for a release that supports 26.3, and check Add-ons again.
  • Run Purpur 26.2 instead. Open Add-ons, then Versions. See change the server version.

This guide does not recommend another logging plugin in its place.

Use a build made for an older version

  1. Take a backup first. If the plugin misbehaves you can go back.
  2. Download CoreProtect 24.1 from its page on Modrinth (modrinth.com/plugin/coreprotect) or Hangar. Use only the plugin’s own pages: copies elsewhere have carried malware.
  3. Open Files, go into the plugins folder, and choose Upload, then Upload from computer.
  4. In Add-ons, Plugins, choose Scan for tampering. It reads every jar in the plugins folder for hidden code, including files you uploaded yourself.
  5. Restart the server. Type plugins in the Console: CoreProtect should be green. Read the start of the Console for errors that name CoreProtect.
  6. Watch it for a while. Type spark tps: a healthy server shows 20. See fix lag.

In the ArthOS panel

On a version CoreProtect has a build for:

  1. Open Add-ons, then Plugins. Under Find plugins choose Modrinth, search for CoreProtect and choose Install.
  2. Choose Restart now when the page offers it.
  3. Make yourself an operator in Players so the commands work. CoreProtect gives its commands to operators by default.

Once CoreProtect is installed

Find out who did it

Type these in game chat.

  1. Type /co i. The inspector is on. Type it again to turn it off.
  2. Left click a block to see who placed it. Right click a block to see what was removed next to it. Right click a chest, door, lever or button to see who used it last.
  3. For a wider search, use /co lookup. For example /co lookup u:Alex t:2h lists what Alex did in the last two hours. a:-block limits it to broken blocks, a:container to chests, a:chat to chat.

A lookup searches the whole server by default. A rollback does not.

Roll it back

  1. Stand near the damage. Preview first: /co rollback u:Alex t:1h r:20 #preview.
  2. If the preview looks right, run it without #preview: /co rollback u:Alex t:1h r:20.
  3. Rolled back too much? /co restore u:Alex t:1h r:20 puts those changes back. /co undo reverses the last rollback or restore.

The options:

OptionMeaningExample
u:Player or playersu:Alex,Sam
t:How far backt:30m, t:2h, t:1d, t:2w
r:Radius around your:20
a:Kind of actiona:+block placed, a:-block broken
i: / e:Include or exclude blockse:stone,dirt

A rollback with no r: uses a radius of 10. To cover the whole server use r:#global, and for one dimension r:#nether. Time units can be combined: t:1h30m.

By hand

  1. Get a CoreProtect file made for your Minecraft version, from a source you trust.
  2. Upload it to the plugins folder in Files and restart.
  3. Type plugins in the console. CoreProtect should be green. /co status shows the version.

CoreProtect keeps its data until you remove it. /co purge t:30d deletes everything older than 30 days; in game it only accepts data older than 30 days.

If it does not work

  • “You do not have permission”. The commands belong to operators by default, so make yourself an operator, or give coreprotect.inspect, coreprotect.lookup, coreprotect.rollback and coreprotect.restore with a permissions plugin.
  • A rollback changed nothing. The radius is only 10 unless you set r:. Move closer or widen it. Check the name and time with a lookup first.
  • It undid too little or too much. Use #preview, and /co restore or /co undo to reverse it.
  • You need inventory changes undone. Add a:inventory to the rollback, for example /co rollback u:Alex t:5m a:inventory, and check with a lookup first.
  • You cannot find it in Add-ons on 26.3. The panel only offers builds made for your exact version, and there was none when checked. Upload the 26.2 build by hand, as described above.
  • It loaded but the server lags or shows errors. That is the risk of a build made for an older version. Turn it off in Manage all, restart, and wait for a release made for your version.

If the damage is old or you do not know who did it, a backup is the other way back.

More on the game: Minecraft servers.

Sources: docs.coreprotect.net: Commands, docs.coreprotect.net: Permissions, raw.githubusercontent.com: README.md, modrinth.com: Versions, hangar.papermc.io: CoreProtect

Minecraft serversAll Minecraft guides