Administrator manual · Overview
Installation, configuration, permissions, and cleanup guidance for server operators.
Administrator responsibilities
Operate DominionProtect around four goals:
- record only the Dominion claims that actually need protection;
- keep database writes, queries, and cleanup from affecting the server;
- give players enough visibility while reserving rollback for trusted roles;
- back up before changing production configuration or storage structure.
Recommended deployment order
- Check Java, Paper / Folia, Dominion, and database versions against installation.
- Stop the server and put the purchased JAR in plugins/.
- Start once and check the generated configuration, language files, and database connection.
- Fill in the database settings and review subscription and recording policies.
- Use a normal player account to test subscription, lookup, inspect, and a small rollback.
- Open the service to players and periodically review database status and failed-record files.
File map
| Path | Contents | Guidance |
|---|---|---|
| plugins/DominionProtect/config.yml | Language, database, recording, subscriptions, query, rollback, and cleanup | Back up before editing; reload after changes |
| plugins/DominionProtect/languages/ | zh_cn.yml and en_us.yml | Adjust localized messages as needed |
| plugins/DominionProtect/failed-records/ | Files created after failed database batches | Inspect before removing |
| dp_records_[id] | One physical record table per claim | Maintain through plugin workflows |