Installation and upgrades

Requirements

• Java 17 or newer;
• Paper / Folia 1.20+;
• Dominion 4.7.3+;
• MySQL 8.0+ or MariaDB 10.6+;
• Vault 1.7+, optional and only required for economy-backed subscriptions.

DominionProtect is a Dominion add-on. The plugin descriptor declares Dominion as a hard dependency and Vault as a soft dependency, so Dominion should load first.

Install

1. Stop the server and back up the world, database, and plugins/DominionProtect/.
2. Put the purchased DominionProtect JAR in plugins/.
3. Start the server and check the enable and database-initialization messages.
4. Stop and fill database.host, database.database, database.username, and database.password in config.yml.
5. Start again and check a claim with /domp admin status [claim].
6. Use a non-OP test account for one lookup and one small rollback.

Database account

The database account needs permission to create tables and temporary tables, drop, insert, select, update, delete, and ALTER tables. The plugin creates one record table per claim and may optimize old tables. Do not use the database root account in production.

For MySQL / MariaDB, create a dedicated database and user for this plugin and restrict network access where practical.

Upgrade notes

Before an upgrade:

• read the current release notes;
• back up the database, especially the largest dp_records_[id] table;
• reserve extra disk space because table optimization may copy data;
• schedule the upgrade during low traffic.

With database.optimizeStorageOnStartup enabled, the plugin waits storageOptimizationDelaySeconds and migrates old records in asynchronous batches. New records can continue to arrive; if the server stops midway, the next start can continue the safe process.