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

UltimateKoth configuration#

The installed files are designed to be edited together: config.yml controls global behavior, commands.yml controls command permissions/aliases, modes.yml defines event modes, GUI files control menus, and language files control player-facing text.

config.yml areas that matter most#

GUI#

Config.gui.enabled enables the GUI system. player_permission and admin_permission are separate, and the no-argument options decide whether /koth or /ukoth opens a GUI automatically.

Economy#

Config.money.enabled enables money handling; the supplied type is VAULT. If command costs/rewards fail, verify the economy extension/provider rather than changing KOTH data.

KOTH defaults#

  • default_icon: TOTEM_OF_UNDYING
  • default_capture_time: 60
  • disable_knockback: false
  • proximity enabled, default 16
  • maximum time enabled, default 300
  • player warp enabled by default with 3 second delay
  • starter item enabled by default
  • key system enabled by default

These are defaults for creation/behavior; existing KOTH data may have per-event values.

Group behavior#

Config.group.default_allow_without_group: true means a player can participate even when no group implementation is available, unless per-event rules/integrations change that behavior.

Scoreboard#

The supplied configuration enables the scoreboard and board recovery. If another scoreboard plugin is installed, confirm which implementation is active before diagnosing visual conflicts.

Scheduler#

Timezone is America/Sao_Paulo. Configure automated schedules only after manual event testing.

Blocks manager#

The optional blocks manager is disabled in the supplied configuration. Enabling it changes block-related restrictions during/after events, so test it on a disposable KOTH.

Editing workflow#

  1. Stop the KOTH you are editing.
  2. Change one feature.
  3. Reload only when the edited file requires it.
  4. Use /ukoth view <name> and a manual event to verify behavior.
  5. Keep a backup before large GUI/language/config refactors.