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

ClanChest practical usage guide#

ClanChest adds shared clan inventory storage with multiple pages, configurable page modes, role restrictions and safer multiserver access. 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: Open the shared storage through the configured /clan chest command/GUI action. Unlock or buy additional pages if page purchasing is enabled. Use NORMAL pages for regular shared storage, LOCKED pages for role-restricted access, DEPOSIT_ONLY pages when members may add but not remove, and CATEGORY pages when the page is intended for filtered/category storage.

  1. Open the shared storage through the configured /clan chest command/GUI action.
  2. Unlock or buy additional pages if page purchasing is enabled.
  3. Use NORMAL pages for regular shared storage, LOCKED pages for role-restricted access, DEPOSIT_ONLY pages when members may add but not remove, and CATEGORY pages when the page is intended for filtered/category storage.
  4. Leaders can be configured/implemented with broader management access; test each clan role before production use.

Administrator setup checklist#

  • Define each page name, icon, description, unlock requirement and mode in the addon configuration.
  • Keep visual GUI slots separate from actual stored item layout; do not repurpose storage slots as cosmetic buttons.
  • For shared MySQL/multiserver environments, use the addon locking/synchronization behavior and avoid running different page definitions on different nodes.

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.