Wiki Release: 2026.09.5 · UltimateKoth: 2.26.1 · Documentation branch: 2

UltimateKoth troubleshooting#

Start with the symptom, then verify the smallest subsystem that can cause it.

KOTH cannot be created#

Check that the wand selection is complete, both points are in the intended world/region, the event name is unique, and command use is not blocked by disabled_command_regions or disabled_command_worlds.

Event starts but nobody captures#

Verify the actual capture region/center with /ukoth view and /ukoth tp. Test with one non-OP player first. Then check group integration, event mode, proximity and any contesting participant still inside the area.

Capture resets or behaves differently than expected#

Determine whether the KOTH uses normal mode or PercentageEvent. Test proximity and capture rules separately. Do not compare percentage-mode progress with the classic capture timer.

Scheduler does not start an event#

Check Config.scheduler.timezone, the exact KOTH identifier and /ukoth scheduler list. Then verify minimum-player rules. Always confirm /ukoth start <name> works manually first.

Warp does not work#

Check that the KOTH allows player warp, the player has ukoth.player.warp, and the target has a valid location. If teleport begins and then cancels, test movement/combat cancellation and the 3 second default teleport delay.

Loot/reward does not appear#

Use a guaranteed test chance and a harmless reward command. Verify the reward branch independently from keys. If money commands fail, check the active economy implementation/Vault.

Key block cannot be opened#

Verify the key feature is enabled, the configured block is acceptable, the key was created/given by the current KOTH setup, and the block belongs to the intended event. Test without region-protection plugins first if interaction is cancelled.

Hologram is missing#

The KOTH can work without a hologram. Verify a compatible hologram extension is loaded and Config.holograms allows the world/region. Recreating the KOTH normally does not fix a missing hologram provider.

Scoreboard remains after event#

Verify event stop/cleanup first, then check scoreboard implementation conflicts. The supplied configuration enables recover_boards, so a persistent board may indicate an interrupted cleanup or another scoreboard plugin taking control.

Command says no permission while OP works#

Test the exact node from commands.yml with OP disabled. Player GUI and admin GUI permissions are also separate from command permissions.