CoreProtect is a fast, efficient, data logging and anti-griefing tool. Allowing us to rollback and restore any amount of damage.
CoreProtect Documentation
Please use this plugin with extreme care, and always double-check if you’re doing exactly what you intend to do.
If you’re unsure, use /co help, look at the CoreProtect Documentation or ask other staff members for help!
If you notice that you messed up big time, and `/co undo` doesn’t help after a rollback, message happy and say something in the staff chat!
We can enter inspect mode using /co i or /co inspect.
/co near shows you a list of logs that happened around you.
While in this mode, we can do the following:
- Left-click a block to see placement and destruction history for that exact block
- Right-click a block to view changes to the block above it
- Right-click a container (e.g., chests, furnaces, hoppers) to view item transactions
- Right-click doors, trapdoors, buttons, levers, etc. to see interaction logs
- Right-click signs to see past edits or placements
To exit inspect mode, use /co i again.
We can lookup things by either using /co lookup or /co l. This is super useful when trying to find out who the bad guy is.
You can use filters to find specific things when looking through logs.
Example Lookup Commands #
Lookup commands are generally the same as rollback commands. The primary difference is that a default radius is not applied to lookups, meaning all lookup commands do a global search by default.
/co lookup i:diamond_ore t:1h a:-block(lookup all diamond ore mined in the last hour)/co lookup u:Notch t:30m a:chat(lookup chat messages sent by Notch in the last 30 minutes)/co lookup u:Notch t:3d a:inventory(lookup inventory transactions by Notch in the last 3 days)/co lookup u:Notch a:login(lookup all logins ever done by Notch)/co lookup u:Notch a:username(lookup previous usernames used by Notch)
We can rollback stuff by either using /co rollback or /co rb.
If you want to make sure you are rolling back the right things, you can always use #preview at the end of the command to see a preview of the rollback, and then decline or accept the rollback. If you messed something up, you can use /co undo to undo the rollback.
Note: Rolling back container interactions doesn’t remove the items from the bad actor’s inventory or wherever they put it. When it’s about valuable items, it’s best to use other commands to try and locate them and retrieve them, before doing a rollback.
You can use the same filters on this command as well.
Example Rollback Commands #
By default, if no radius is specified, a radius of 10 will be applied, restricting the rollback to within 10 blocks of you. Use r:#global to do a global rollback.
/co rollback Notch t:1h(rollback Notch 1 hour (with default radius of 10))/co rollback u:Notch,Intelli t:1h #preview(PREVIEW rolling back both Notch & Intelli 1 hour (with default radius of 10))/co rollback u:Notch t:23h17m(rollback Notch 23 hours and 17 minutes (with default radius of 10))/co rollback u:Notch t:1h i:stone(rollback ONLY stone placed/broken by Notch within the last hour (with default radius of 10))/co rollback u:Notch t:1h i:stone a:-block(rollback ONLY stone BROKEN by Notch within the last hour (with default radius of 10))/co rollback u:Notch t:1h r:#global e:stone,dirt(rollback EVERYTHING Notch did in the last hour EXCEPT for stone and dirt placed/broken)/co rollback u:Notch t:1h r:20(rollback griefing Notch did in the last hour that is within 20 blocks of you)/co rollback u:Notch t:1h r:#nether(rollback griefing Notch did in the last hour ONLY in the Nether)/co rollback u:Notch t:5m a:inventory(rollback inventory transactions by Notch in the last 5 minutes)/co rollback t:15m r:30(rollback everything done in the last 15 minutes by anyone within 30 blocks of you)/co rollback t:15m r:#worldedit(rollback everything done in the last 15 minutes in a WorldEdit selection)