Quick start

What you will do

By the end of this page, DominionProtect should be running and a player should be able to query an active claim. The plugin is paid-only and currently costs ¥69 on the Afdian product page.

1. Prepare dependencies

• Java 17 or newer;
• Paper or Folia 1.20+;
• Dominion 4.7.3+, working normally;
• MySQL 8.0+ or MariaDB 10.6+ for the administrator setup described here;
• Vault only when the server enables economy-backed subscriptions.

2. Place the plugin and start

Put the purchased DominionProtect JAR in plugins/ and start the server once. The first start creates:

plugins/DominionProtect/config.yml
plugins/DominionProtect/languages/
plugins/DominionProtect/failed-records/

Confirm the enable and database-initialization messages in the log. If the database fails, pause subscriptions and read installation and troubleshooting.

3. Configure a test plan

The first start writes default subscription plans. Test the workflow with a safe price or free mode before opening economy subscriptions to players. The price, period-days, record-limit, and quota-full-strategy keys live in config.yml; see subscriptions and economy.

4. Run the first lookup

Stand inside a Dominion claim with recording enabled:

/domp status
/domp lookup t:24h

Page through results when needed:

/domp page next
/domp page prev

To inspect a particular block, run /domp inspect and click it with an empty hand.

5. Test a rollback

Rollback requires dominionprotect.rollback. Use a narrow filter in a test claim:

/domp rollback t:10m p:Steve a:block-place r:20

If the preview is shown, review the client-only ghost blocks and confirm with:

/domp confirm

Use /domp cancel when the filter is wrong. To undo a completed rollback, run the matching /domp restore … command and confirm.

Next

• Players: lookup and inspect and rollback and restore.
• Administrators: configuration overview and admin commands.