Rollback and restore
Safely preview, confirm, execute, or undo claim-local changes.
Narrow the scope first
Rollback requires dominionprotect.rollback and normally targets the claim where you stand. Include at least a time and player filter when possible:
/domp rollback t:10m p:Steve a:block-break r:30Operations beyond rollback.maxRecords are rejected; the default limit is 50000 records.
Preview and confirmation
Ghost-block preview is enabled by default. When the match count is at or below rollback.previewMaxBlocks (10000 by default), the plugin sends block changes visible only to you. The world is not modified yet:
- Confirm a correct preview with /domp confirm.
- Cancel a wrong filter with /domp cancel.
- A timed-out preview is cancelled automatically.
When the match count is above the preview limit, the plugin sends a confirmation prompt instead. The default confirmation window is 30 seconds.
Execution and progress
After confirmation, changes are dependency-sorted and processed in batches to reduce cascading effects from gravity blocks, attached blocks, and liquids. A BossBar reports progress, and only one rollback / restore task runs for a claim at a time.
Restore a rollback
Restore reverses records that have already been rolled back:
/domp restore t:10m p:Steve a:block-break r:30
/domp confirmIf no matching rolled-back records remain, the plugin reports that there are no records to restore.
Restore is not a backup
Restore depends on the records still existing, not being cleaned up, and remaining distinguishable from later changes. Keep normal world and database backups for important claims; record-level restore is not a replacement for a full backup.