TribeCraft Wiki · Release 2026.09.8
Wiki Release: 2026.09.8 · UltimateClans: 9.1.4 · Documentation branch: 9 · Banner

Banner#

Banner adds clan banner creation/display management with GUI and unlock/permission rules. The pages in this section explain what players see in-game, what administrators need to configure, the normal setup flow, and the most common problems you may need to diagnose.

Compatibility#

  • Component version: 1.2
  • Documentation release: 2026.09.8
  • Minimum UltimateClans version: 9.0.0

What you can do with it#

  • Open the banner management GUI/command
  • Choose/edit the clan banner pattern/colors, save it, then verify the clan display uses the new banner
  • Configure unlock/role requirements if banner editing should not be available to every member

How it works#

The Banner module lets a clan own/manage a banner representation used by supported GUI/display features. Members with the configured clan permission can open the banner editor/GUI and save a banner; the module then exposes that saved banner through its public API to other parts of UltimateClans.

First setup#

Before enabling the feature for players, review these installed files:

  • commands.yml
  • config.yml
  • gui.yml
  • language/Lang_EN.yml
  • language/Lang_ES.yml
  1. Open the banner management GUI/command.
  2. Choose/edit the clan banner pattern/colors, save it, then verify the clan display uses the new banner.
  3. Configure unlock/role requirements if banner editing should not be available to every member.

This feature is mainly automatic or accessed through the parent plugin/GUI, so it does not need a large standalone command tree.

GUI areas#

The installed GUI configuration contains screens/sections such as:

  • General.banner_home
  • General.banner_home_pre
  • General.banner_delete
  • General.banner_upload

What administrators should configure#

  • Test banner material/pattern compatibility on the supported Minecraft versions.

Configuration map#

  • config.yml — Config (date_format_short, Icon, Permissions, Unlocker, Banner)

The Configuration page lists the available paths and defaults from the installed configuration, with notes on what each area controls.

Before going live#

  1. Back up the component data/configuration.
  2. Start the server and confirm the component is detected without startup errors.
  3. Test with a non-OP player and the lowest clan role that should have access.
  4. Exercise the complete flow once, including the failure/deny path, not only the happy path.
  5. Restart the server and verify that persistent state survives.
  6. If the network is multiserver, repeat the test from a second node and verify storage/synchronization.

Troubleshooting quick reference#

SymptomLikely causeWhat to check
Banner editor does not openPermission/unlocker or GUI module requirement is unmetCheck role permission and module load status.
Pattern/color is lostUnsupported legacy mapping or save failureTest a simple pattern and inspect storage/log output.
Members can edit unexpectedlyRole permission is too broadReview Banner permission configuration.

For a longer diagnostic flow, open the Troubleshooting page for this component.