Wiki Release: 2026.09.5 · UltimateClans: 9.1.4 · Documentation branch: 9 · ClanGladiator
ClanGladiator troubleshooting#
Use this page when ClanGladiator loads but a gameplay/admin workflow does not behave as expected. Start with the narrow symptom rather than changing multiple configuration sections at once.
Fast diagnostic order#
- Confirm the component loaded and its required Core version is compatible.
- Reproduce with a non-OP test account and verify the exact command/role permission.
- Check YAML syntax and the specific feature section involved.
- Verify optional providers (economy, map, hologram, entity, Redis, WorldGuard, etc.) only when that feature depends on them.
- Check persistent storage and cross-server synchronization after configuration/permission checks.
- Read the first component-specific console error produced during startup or reproduction.
Common symptoms#
| Symptom | Likely causes | What to check / fix |
|---|---|---|
| Arena will not start or enable | Selection/setup is incomplete, too few spawns, disabled arena, missing server kit, or participation limits cannot be satisfied | Run /clanglad arena info <arena> and correct every missing setup field; verify mode/kit and min/max limits. |
| Player cannot join serverkit event | Inventory safety rule rejects armor, offhand, cursor or storage items, or player/clan limit was reached | Read the rejection message and Server-Kit.* settings; empty the required slots and retry. |
| Event stays in recruitment/countdown | Minimum clans or leader lineup confirmation has not been satisfied | Check joined clans, Lineup.require-leader-confirmation, and the configured minimum clan count. |
| World border is not visible/shrinking | WorldBorder is disabled, shrink time/final size is invalid, or the optional border implementation is unavailable | Check WorldBorder.enabled, arena timing and final size; inspect startup integration logs. |
| Players keep event inventory after stop/restart | Session/recovery restore did not complete | Do not delete recovery data; stop cleanly, check recovery/storage errors, then retest with a disposable account. |
| Blocks are not restored | Arena protection is NORMAL or regeneration snapshot could not be applied | Use REGENERATE when rollback is required and verify the arena bounds before the event starts. |
| Scheduler does not open event | Scheduler disabled, schedule entry disabled/invalid, or server time does not match the configured HH:mm/day rule | Check Scheduler.enabled, /clanglad schedule list, server clock/timezone and arena enabled state. |
Configuration validation#
Focus on these configuration areas for this component: file-version, General, Default-Arena, Server-Kit, WorldBorder, Rewards, Scheduler, Visuals, Spectator, Lineup, History, Config, Storage. Preserve exact YAML indentation and key names.
Storage and restart checks#
- Do not delete live storage as a first troubleshooting step. Make a backup and inspect it first.
- If the issue appears only after restart, compare what is persisted with what is rebuilt in memory at startup.
- If the issue appears only on one server in a network, compare the component version, config, database and sync channel on that server.
- After a failed migration/recovery operation, keep the original data until the failure is understood.
What to include in a support ticket#
Provide the product/core version, component version, Minecraft/server implementation, the exact command/action used, the relevant config section, and the first related console error. Avoid sending passwords, database credentials, webhook secrets or API keys.
Diagnostic workflow#
Use this order before changing multiple settings at once:
- Startup: find the first warning/error mentioning this component; later exceptions are often consequences.
- Version/dependencies: verify the parent plugin version and every required/optional integration actually detected at startup.
- Configuration: validate YAML indentation/types and compare the relevant path with the default documented in this Wiki.
- Access: test both Bukkit permission and UltimateClans role/internal permission using a non-OP player.
- Context: reproduce in an allowed world/region and check claim/PvP/economy hooks if the feature depends on them.
- Persistence: restart and verify state is loaded from the intended YAML/SQLite/MySQL backend.
- Multiserver: reproduce on a single node first, then verify identical configs/storage/sync on all nodes.
- Isolation: disable unrelated integrations one at a time only when the evidence points to a hook conflict.
What to include when requesting support#
- Exact plugin/core/component versions.
- The command/action performed and expected result.
- The first relevant console exception/warning, not only the last line.
- The relevant configuration section with secrets removed.
- Whether the problem reproduces with a non-OP player.
- Server software/version and whether the server is part of a multiserver network.
Files worth checking#
commands.ymlconfig.ymlgui.ymllanguages/Lang_EN.ymllanguages/Lang_ES.ymlpolymart.yml