Server Troubleshooting

Server troubleshooting

Wiki home · Player commands · Get help

Diagnose installation, database, integration, and configuration problems.

This wiki documents Civilizations 1.0.1. Numbers are bundled defaults; in-game menus and previews show your server’s current values.

Question or symptom	Explanation and next step
Plugin fails with UnsupportedClassVersionError	The server launched with an older Java runtime. Select Java 25 in the actual service/panel startup environment, not only your terminal.
Maven reports an unsupported release	Check mvn -version; Maven must run under JDK 25.
Unsupported API version or missing Bukkit methods	Check that the server implements Spigot API 26.2. A newer label or a different fork is not proof of compatibility.
Maven cannot resolve dependencies	The first build needs repository access. Inspect the reported repository/network error; offline mode only works after dependencies are cached.
Everyone is blocked by “territory data is warming up”	Check database endpoint, credentials, grants, TLS, migration logs, and the readiness message. Do not disable protection as a workaround.
MySQL “access denied”	Check both username/password and the allowed source host for that MySQL account. Container/remote source addresses differ from localhost.
Migration checksum mismatch	Use the matching release lineage or restore a matched backup; do not edit checksums or old migrations.
Vault is installed but payments do not work	Install/enable a compatible economy provider and set economy.mode: VAULT, then restart and check provider readiness.
Plots cost nothing and taxes are not collected	The default economy mode is DISABLED; money-backed play requires Vault mode and a provider.
Random travel causes lag	Candidate chunks may need generation on Spigot's main thread. Use an intentional play-area border and review pre-generation/server performance.
I changed config.yml but behavior is unchanged	/civ admin reload only reloads messages and validates configuration. Structural/gameplay changes require a full restart.
A customized catalog was replaced	Startup detected a mismatched catalog version or legacy format and backed it up before restoring the shipped format. Review .pre-v*.bak and reapply compatible changes.
Can I connect several servers to one schema?	Not with this implementation. There is no cross-server cache invalidation; use a separate schema per active server.

When reporting a bug, include the exact plugin/server/Java versions, reproduction steps, relevant command and error text, active integrations, and a sanitized log excerpt. Omit database passwords, private player data, and full database dumps from public issues.

---

Continue reading: Server setup and installation · Administration and maintenance · Operations runbook · Player FAQ and troubleshooting