TribeCraft Wiki · Release 2026.09.5
Wiki Release: 2026.09.5 · UltimateClans: 9.1.4 · Documentation branch: 9 · ClanGladiator

ClanGladiator practical usage guide#

ClanGladiator adds clan-versus-clan arena event with recruitment, leader lineup confirmation, server kits or own items, spectators, schedules, rewards, world border, protection modes, history and recovery. This guide focuses on the actual administrator and player workflow: what to set up first, how to test it in-game, and what to check before enabling it for everyone.

How the feature works#

In normal use, the feature follows this flow: Run /clanglad wand, select both arena corners, then /clanglad arena create <arena>. Stand at the waiting location and run /clanglad arena setlobby <arena>, then set the return point with setexit. Add enough independent clan combat points with /clanglad arena addspawn <arena>; use arena info to validate the setup.

  1. Run /clanglad wand, select both arena corners, then /clanglad arena create <arena>.
  2. Stand at the waiting location and run /clanglad arena setlobby <arena>, then set the return point with setexit.
  3. Add enough independent clan combat points with /clanglad arena addspawn <arena>; use arena info to validate the setup.
  4. Choose serverkit or ownitems. For serverkit, prepare your inventory, run /clanglad kit create <kit>, then assign it with arena setkit.
  5. Set clan/player limits, recruitment/countdown/max duration/shrink/finishing times, border size, timeout resolution and block protection.
  6. Configure rewards with arena reward addcommand and/or additem.
  7. Enable the arena, then use /clanglad start <arena> for recruitment. Players use /gladiator join <arena>; if lineup confirmation is required, the clan leader confirms the lineup.
  8. Use /clanglad forcestart only when you intentionally want to bypass the normal waiting flow. Schedules can automate event opening.

Administrator setup checklist#

  • Use arena info after every structural change; an arena should have bounds, lobby, exit and usable combat spawns before production.
  • For serverkit mode, configure inventory restrictions deliberately: storage/armor/offhand/cursor checks exist to prevent item duplication or unintended carry-over.
  • Select NORMAL/INDESTRUCTIBLE/REGENERATE protection according to whether blocks should be changed and later restored.
  • Test player disconnect/reconnect and a forced stop once; recovery storage exists specifically to restore interrupted sessions.

Commands and GUI access#

Use the command examples in the workflow above and open the Commands page in the sidebar for the complete configured command tree. Command labels can be changed in commands.yml, so the Wiki keeps the player-facing examples separate from the raw message templates.

Configuration areas#

  • file-version
  • General — debug, allow-multiple-events, prevent-non-participants-in-arena, disconnect-grace-seconds, lobby-radius, restore-health-on-exit, teleport-to-arena-exit, allowed-commands, arena-rules
  • Default-Arena — enabled, display-name, icon, mode, kit, min-clans, max-clans, max-players-per-clan, recruitment-seconds, countdown-seconds, max-duration-seconds, shrink-at-remaining-seconds
  • Server-Kit — force-survival, clear-potion-effects-on-entry, require-empty-storage, require-empty-armor, require-empty-offhand, require-empty-cursor, block-inventory-containers, block-item-drop, block-item-pickup
  • WorldBorder — enabled, warning-distance, warning-time, portal-teleport-boundary
  • Rewards — recipient-scope, run-commands-for-offline-players, drop-overflow-items-at-exit
  • Scheduler — enabled, check-interval-seconds
  • Visuals — scoreboard, bossbar, actionbar, announcements
  • Spectator — enabled, allow-external-players, allow-eliminated-players
  • Lineup — require-leader-confirmation
  • History — enabled, max-records
  • Config — Icon
  • Storage — type, mysql, table

Changing settings safely#

  1. Back up the component configuration and persistent data before changing a live server.
  2. Change one feature area at a time.
  3. Reload only if the component documents reload as safe; otherwise restart the server.
  4. Test with a non-OP account that has exactly the intended clan role/permission.
  5. Watch the console from the first relevant warning/error, not only the final stack trace.
  6. On multiserver networks, repeat the check on every node and confirm shared storage/sync settings match.
Wiki Release 2026.09.5 · Canonical TribeCraft documentation.