Wiki Release: 2026.09.5 · UltimateClans: 9.1.4 · Documentation branch: 9
UltimateClans troubleshooting#
Diagnostic method#
Reproduce the smallest failing workflow with a non-OP account. Confirm version/command/config first, then optional integrations, then persistence/synchronization. Avoid deleting generated data until a backup exists.
Common symptoms#
| Symptom | Likely cause | What to check / fix |
|---|---|---|
/clan command missing or subcommand unavailable | Core/module did not load, command disabled, alias changed or permission missing | Check startup component list, commands.yml, exact Bukkit permission and disabled worlds/regions. |
| Player has Bukkit permission but clan action is denied | Clan-role permission or clan state blocks the action | Check the member role permission, leadership requirement, cooldown/cost and clan state. |
| Clan data differs after restart | Storage save/load problem or multiple storage backends are mixed | Check storage.yml, database connectivity and the first persistence error; do not delete storage. |
| Different servers show different clan state | Shared DB/Redis multiserver settings differ | Compare storage plus Multiserver Redis channel/database/server names on every node. |
| GUI button does nothing | GUI action/command placeholder, module dependency or permission is invalid | Resolve the configured click action, run the equivalent command manually and inspect GUI/module logs. |
| Placeholder returns empty/raw text | Placeholder hook unavailable, wrong identifier/context, or the requested clan/player is absent | Confirm PlaceholderAPI/integration and test a simple core placeholder with an online clan member. |
| Addon/module refuses to load after Core update | Minimum/compatible version check fails | Use the component build intended for V9/Core version and read the first min-version message. |
Startup failures#
Read from the first plugin-specific warning or exception. Later errors are often consequences. Verify Java/Minecraft compatibility, Core/component minimum versions, YAML parsing and storage connection before changing gameplay settings.
Configuration failures#
Validate YAML indentation and exact keys. If a problem started after an edit, compare only that section with the supplied default/current installed file rather than replacing the whole configuration.
Storage failures#
Back up first. Verify the configured backend, credentials/path, schema/table permissions and whether another server is writing the same data. Never solve an unknown persistence error by deleting the production database.
Integration failures#
Map, hologram, economy, entity, protection, PlaceholderAPI and other providers should be diagnosed independently. Confirm the provider works on its own and that the matching extension/implementation was detected.
Support information#
Include product version, Minecraft/server implementation, exact command/action, relevant YAML section and first related console error. Remove passwords, tokens, webhook URLs and API keys.