DominionProtect
Installation, usage, configuration, and operations documentation for DominionProtect.
Start here
Read the quick start to go from dependencies to the first lookup. Players can use the player docs for subscriptions, lookup, inspect, rollback, and restore. Administrators should start with the administrator manual for installation, database, configuration, permissions, and troubleshooting.
What is DominionProtect?
DominionProtect is an add-on for Dominion that records block, entity, container, and interaction changes inside Dominion claims, with lookup, ghost-block preview, rollback, and restore workflows. It is intended for survival, building, and community servers that use claims as their governance boundary.
The plugin itself is paid-only and currently costs ¥69. Purchase it from the Afdian product page. That product purchase is separate from the in-server subscription plans configured by a server owner.
Core workflow
Events inside a claim → asynchronous recording → filtered lookup → rollback preview / confirmation → batched execution → restore when neededRecording, lookup, rollback, and cleanup are claim-scoped. A claim without an active subscription does not continue recording; viewers also need both plugin permission and the Dominion dominion_protect_view flag.
Documentation map
| Goal | Page |
|---|---|
| Install and run a first lookup | Quick start |
| Learn player commands and filters | Player commands |
| Find a player’s or block’s history | Lookup and inspect |
| Preview, confirm, or undo a rollback | Rollback and restore |
| Manage in-server protection plans | Subscriptions and economy |
| Install the server plugin | Installation and upgrades |
| Manage admin commands and permissions | Admin commands · Permissions |
| Tune database, recording, rollback, and cleanup | Configuration overview · config.yml |
| Diagnose a production issue | Troubleshooting |
Important boundaries
- Dominion must be installed and working; the 0.3.0 build targets Java 17, Paper / Folia 1.20+, and Dominion 4.7.3+.
- Rollback is not an unconditional undo button: narrow the filters first, then preview or confirm; operations beyond rollback.maxRecords are rejected.
- A preview is visible only to the executor and does not modify the world until confirmation.
- Expired subscriptions enter a grace period first; cleanup is controlled by the administrator’s cleanup settings.