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#
Banner workflow#
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.ymlconfig.ymlgui.ymllanguage/Lang_EN.ymllanguage/Lang_ES.yml
Recommended in-game workflow#
- 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.
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_homeGeneral.banner_home_preGeneral.banner_deleteGeneral.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#
- Back up the component data/configuration.
- Start the server and confirm the component is detected without startup errors.
- Test with a non-OP player and the lowest clan role that should have access.
- Exercise the complete flow once, including the failure/deny path, not only the happy path.
- Restart the server and verify that persistent state survives.
- If the network is multiserver, repeat the test from a second node and verify storage/synchronization.
Troubleshooting quick reference#
| Symptom | Likely cause | What to check |
|---|---|---|
| Banner editor does not open | Permission/unlocker or GUI module requirement is unmet | Check role permission and module load status. |
| Pattern/color is lost | Unsupported legacy mapping or save failure | Test a simple pattern and inspect storage/log output. |
| Members can edit unexpectedly | Role permission is too broad | Review Banner permission configuration. |
For a longer diagnostic flow, open the Troubleshooting page for this component.