Troubleshooting

The plugin does not enable

Check Java 17+, Dominion version, the JAR location in plugins/, and startup errors mentioning dependencies or plugin.yml. DominionProtect cannot run without Dominion.

Database connection fails

Check host, port, database, username, and password in config.yml. Confirm that the account has the privileges listed in installation. If the pool cannot initialize, pause player subscriptions and recording, then inspect the full server log.

A lookup returns nothing

Check, in order:

1. You are inside the target Dominion claim.
2. The claim has an active subscription.
3. You have dominion_protect_view.
4. Time, action, player, and block names are formatted correctly.
5. The action is not disabled by recording.disabledActions.
6. The record is not past retention or evicted by the quota strategy.

Subscription fails

• Vault or a compatible economy service is missing.
• The balance is insufficient.
• The plan ID does not exist.
• The claim already has an active subscription.
• vaultUnavailableStrategy forbids subscriptions without Vault.

Use /domp plans, /domp status, and the server log together.

Rollback is rejected or has no preview

Narrow t:, p:, a:, b:, or r:. Records beyond rollback.maxRecords are rejected. Counts above rollback.previewMaxBlocks use a confirmation prompt instead of ghost blocks. The default confirmation window is only 30 seconds.

Database writes fail

Check whether plugins/DominionProtect/failed-records/ contains failure files. Keep those files and the server log for maintainers; do not delete them just to hide the failure.