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

UltimateKoth getting started#

The safest way to configure UltimateKoth is to build one small test KOTH, make it work from start to finish, then add automation and rewards.

Before creating the first KOTH#

Check these global settings first:

  • Config.gui.enabled — controls the GUI system.
  • Config.money.enabled and Config.money.type — controls money integration. The supplied configuration uses VAULT.
  • Config.koth.default_capture_time — default capture time for newly created KOTHs; supplied default is 60 seconds.
  • Config.koth.proximity.default — default proximity radius; supplied default is 16 blocks.
  • Config.koth.maxtime.default — default maximum event duration; supplied default is 300 seconds.
  • Config.scheduler.timezone — supplied value is America/Sao_Paulo; scheduler times are interpreted using this timezone.

Create a test KOTH#

  1. Run /ukoth wand and select the region required by the creation flow.
  2. Run /ukoth create and complete the name/input requested by the plugin.
  3. Verify it with /ukoth list, /ukoth view <name> and /ukoth tp <name>.
  4. Keep capture time short while testing.
  5. Run /ukoth start <name> manually.
  6. Enter the region with a normal player and verify the capture timer/progress.
  7. Contest the region with a second eligible player/group and confirm the configured dispute behavior.
  8. Let the event finish and verify winner handling before adding expensive rewards.

What players should see#

Players normally use /koth events, /koth info, /koth stats, /koth loots and /koth warp. These commands are useful during testing because they show what UltimateKoth itself considers active/next/configured.

Add features in this order#

After the manual event works, add one feature at a time:

  1. reward commands;
  2. loot/key behavior;
  3. warp and starter item;
  4. holograms/scoreboards;
  5. proximity and maximum-time edge cases;
  6. scheduler and pre-alerts.

This order makes troubleshooting much easier because a broken scheduler cannot hide a broken KOTH definition.