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

ClanLeague practical usage guide#

ClanLeague adds seasonal clan league progression with leagues, seasons, scheduled state changes, points, GUI, persistence and placeholders. 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: Define league tiers/requirements and season behavior before players begin earning points. Start or load a season, then add/earn points through the supported event/command integrations. Open the league GUI and verify clan placement/progression.

  1. Define league tiers/requirements and season behavior before players begin earning points.
  2. Start or load a season, then add/earn points through the supported event/command integrations.
  3. Open the league GUI and verify clan placement/progression.
  4. Test season rollover/reset behavior on a copy of production data before using it live.

Administrator setup checklist#

  • Keep league IDs and season storage stable; renaming identifiers can orphan historical data.
  • Check timezone/date settings used by scheduler/season logic.
  • If another addon contributes league points, test that integration separately.

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, timezone, League, Season, Icon, Permissions, logger
  • Storagetype, mysql, user, pass, databases

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.