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

ClanWar practical usage guide#

ClanWar adds organized clan-versus-clan wars using arenas, invitations, kits, event rules, rewards and match state. 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: Create/select an arena with the addon wand/admin flow, then define the required positions/spawns. Configure a kit or arena inventory rules when the war mode requires one. Configure invitation/acceptance behavior and match limits.

  1. Create/select an arena with the addon wand/admin flow, then define the required positions/spawns.
  2. Configure a kit or arena inventory rules when the war mode requires one.
  3. Configure invitation/acceptance behavior and match limits.
  4. Start/accept a war with test clans, verify teleport, PvP, block rules, winner detection and return flow before enabling rewards.

Administrator setup checklist#

  • Keep arena definitions and kit IDs stable after players begin using them.
  • Configure commands/rewards only after winner detection is verified.
  • Review block protection and restoration behavior for arenas that are not disposable.

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#

  • Configdate_format, War, Icon, Permissions, logger, league

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.