Reverse an accidental CoreProtect rollback with the matching scope

Applies to: CoreProtect; match the linked maintainer documentation to your installed platform and release.
Documentation checked 9 November 2026.

An accidental rollback should be reversed from its recorded parameters, not followed by a broader repair. Capture the operation details before another administrator changes the same area.

Follow the procedure

Pause building in the affected area and record the rollback command, executor, completion time and reported scope. Identify whether the action was a rollback, restore or only a preview.
Read the installed command documentation for restore and /co undo. The documented undo performs the opposite of the relevant rollback or restore; verify which operation the current context will target.
Take a current recovery copy before making a second world change. Preserve the CoreProtect database and any before-incident backup so later review has both states.
Rehearse a matching restore or supported undo on an isolated copy when the affected area is valuable. Keep the same user, time, action and spatial filters rather than widening them.
Have the authorized administrator execute the reviewed reversal once. Watch completion output and keep other staff from starting overlapping recovery commands.
Compare the affected blocks and containers with the recorded expected state. Check work performed after the first rollback separately, since a reversal may not preserve every intervening player action.

Check the result

The incorrectly reversed actions should return to the intended state within the matching scope, with completion output retained. Verify both the original damage and any legitimate later work. A command saying finished does not establish that every affected player’s possessions are correct.

If the result is wrong

If the reverse preview or rehearsal is wrong, stop and retain the current state for review. Do not alternate broad rollback and restore commands repeatedly. Use the exact recorded operation or a coordinated backup recovery plan, with world and database state kept consistent.

Give a LuckPerms permission an expiry without leaving permanent access

Make a LuckPerms event rank expire while preserving other ranks

Limit a LuckPerms command permission to one Minecraft world

Keep a LuckPerms permission local to one network backend

Move a player along a LuckPerms track without replacing unrelated groups

Fix a LuckPerms prefix priority without changing chat formatting

Remove a direct LuckPerms exception without weakening its parent rank

Apply a small LuckPerms web-editor session to the correct server

Export LuckPerms data before changing its storage configuration

Find an inheritance cycle before it complicates a rank change

Keep default-player permissions separate from staff inheritance

Diagnose LuckPerms edits that reach one backend but not another

Check a player UUID before changing LuckPerms account data

Remove a staff member from one LuckPerms track without clearing their account

Give an EssentialsX rank a fixed home limit

Restrict one EssentialsX warp to an approved player group

Test EssentialsX teleport delay and movement cancellation

Add an EssentialsX cooldown to one utility command

Resolve an EssentialsX command alias conflict without removing either plugin

Check EssentialsX AFK kick exemptions for a staff role

Limit EssentialsX nickname changes without granting formatting control

Give staff a read-only EssentialsX player-information role

Recover from an accidental EssentialsX ignore setting

Restrict EssentialsX repair commands to the intended tool policy

Review EssentialsX command-disabled entries after a plugin change

Test an EssentialsX jail location without trapping a real player

Change the EssentialsX starting balance for new players only

Set EssentialsX maximum and minimum money limits with a boundary test

Change the EssentialsX currency symbol without changing stored money

Test an EssentialsX pay dispute using two controlled accounts

Review EssentialsX worth prices before enabling item selling

Explain an EssentialsX balance leaderboard that looks out of date

Trace an unexpected EssentialsX command charge

Back up EssentialsX money before a player-data migration

Verify a LiteBans temporary ban expires at the intended time

Test whether a LiteBans mute covers a private-message command

Build a LiteBans appeal-review role without punishment access

Check a LiteBans moderator’s maximum punishment duration

Find which plugin handled a ban command on a mixed-plugin server

Verify the server scope of a LiteBans network punishment

Investigate a LiteBans database connection failure without losing history

Reverse one appealed LiteBans punishment while preserving the audit trail

Test an AdvancedBan time layout before staff use it

Check AdvancedBan warnings without accidentally escalating a real player

Give an AdvancedBan helper access to history without ban powers

Check AdvancedBan storage before changing from local files to MySQL

Lift one AdvancedBan restriction after an approved appeal

Locate AdvancedBan correctly on a proxy network

Test SuperVanish visibility with separate staff and player accounts

Check whether a vanished SuperVanish moderator can pick up items

Verify flight is safe when a SuperVanish moderator reappears

Check silent chest inspection without changing container contents

Find a SuperVanish join or player-list information leak

Remove vanish access from a staff role without leaving a hidden account

Check PremiumVanish layered visibility after changing staff ranks

Verify PremiumVanish network vanish across Velocity backends

Check vanished staff interactions before a live investigation

Recognize the PremiumVanish API jar before installing an integration

Give GrimAC alerts to one observer without granting exemptions

Remove a GrimAC exemption and verify when checks resume

Collect a GrimAC prediction log for a false-positive report