How to rollback griefing using CoreProtect
If you want to have soft griefing control over your server, that is, no plugins preventing breakage of blocks, but also, being able to revert any damage, a plugin like CoreProtect is highly desirable, this guide will explain how to install it and use it on your server:
Please note that it is only possible to perform a rollback once the plugin has been installed and configured. It is NOT possible to rollback if no copy exists.
Downloading and Installing CoreProtect
Head over to CoreProtect website and select “Download Now” on the top-right hand corner.
Then install the plugin by going to your plugins folder and upload the downloaded plugin.
After you restart the server the plugin should work with no problems, and will start gathering information about the server, such as blocks broken, people in the server, etc. you can see a list of logged events in the plugin on the CoreProtect website.
Command Specifications and Explanations.
In order to properly rollback damage, we first need to understand how CoreProtect works.
It takes account of the region being loaded by every player but takes up a specific time and radius around them.
To rollback the area of damage, Do /co rollback u: t: r:
u: means the user who did, or experienced the changes.
t: is how much time has passed since the present time, it has a special formatting, being first put the largest time, and at last the least significant time, expressed in weeks, days, hours, minutes or seconds. that is, for example. t:1w3d13h5m will execute a rollback to 1 Week, 3 days, 13 hours and 5 minutes ago
r: is the radius around the player specified in “u:” specified in blocks, can be set to #global to do a whole world rollback.
We don’t always know who did the damage, so to inspect those changes, we can use /co inspect and left click the blocks in-game, that will tell when they were last modified, right-clicking them will show the changes done to adjacent or previous-adjacent blocks.
Also, right-clicking containers (Chests, furnaces, etc) will tell which items were retrieved or deposited into them, also displaying at what time, and who did so.
To turn off the inspect just to /co inspect again.
Permission nodes for usage with a permissions plugin.
CoreProtect has many permissions, but the most important in order to do the inspect and the rollbacks are:
coreprotect.inspect - for being able to use the inspector
coreprotect.rollback - to use the rollback command
coreprotect.* - To allow usage of all coreprotect commands.
If you require any further assistance, please create a ticket here.
Created By: Daniel R.
Please note that it is only possible to perform a rollback once the plugin has been installed and configured. It is NOT possible to rollback if no copy exists.
How to rollback griefing using CoreProtect
Downloading and Installing CoreProtect
Head over to CoreProtect website and select “Download Now” on the top-right hand corner.
Then install the plugin by going to your plugins folder and upload the downloaded plugin.
After you restart the server the plugin should work with no problems, and will start gathering information about the server, such as blocks broken, people in the server, etc. you can see a list of logged events in the plugin on the CoreProtect website.
Command Specifications and Explanations.
In order to properly rollback damage, we first need to understand how CoreProtect works.
It takes account of the region being loaded by every player but takes up a specific time and radius around them.
To rollback the area of damage, Do /co rollback u: t: r:
u: means the user who did, or experienced the changes.
t: is how much time has passed since the present time, it has a special formatting, being first put the largest time, and at last the least significant time, expressed in weeks, days, hours, minutes or seconds. that is, for example. t:1w3d13h5m will execute a rollback to 1 Week, 3 days, 13 hours and 5 minutes ago
r: is the radius around the player specified in “u:” specified in blocks, can be set to #global to do a whole world rollback.
We don’t always know who did the damage, so to inspect those changes, we can use /co inspect and left click the blocks in-game, that will tell when they were last modified, right-clicking them will show the changes done to adjacent or previous-adjacent blocks.
Also, right-clicking containers (Chests, furnaces, etc) will tell which items were retrieved or deposited into them, also displaying at what time, and who did so.
To turn off the inspect just to /co inspect again.
Permission nodes for usage with a permissions plugin.
CoreProtect has many permissions, but the most important in order to do the inspect and the rollbacks are:
coreprotect.inspect - for being able to use the inspector
coreprotect.rollback - to use the rollback command
coreprotect.* - To allow usage of all coreprotect commands.
If you require any further assistance, please create a ticket here.
Created By: Daniel R.
Updated on: 19/12/2023
Thank you!