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

ClanLand practical usage guide#

ClanLand adds clan land claiming and protection with configurable PvP/TNT/liquid/mob rules, bossbar/hologram/map feedback, decay and persistent land data. 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: Claim land through the configured clan land command/GUI after meeting clan/permission/limit requirements. Enter/leave the claimed area and verify bossbar/hologram/map feedback. Test members, allies, rivals and outsiders against block, container, PvP, TNT, liquid and mob rules that you actually enable.

  1. Claim land through the configured clan land command/GUI after meeting clan/permission/limit requirements.
  2. Enter/leave the claimed area and verify bossbar/hologram/map feedback.
  3. Test members, allies, rivals and outsiders against block, container, PvP, TNT, liquid and mob rules that you actually enable.
  4. Configure decay only after normal claims and unclaims are working.

Administrator setup checklist#

  • Limits, permissions and protection flags should be tested by relationship type, not only with an operator account.
  • Map/hologram providers are optional integrations; validate each independently.
  • Back up land storage before changing world/chunk mapping or decay rules.

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#

  • Config — Land, Banner, Tasks, Icon, Permissions, logger, Storage, Modules

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.