Wiki Release: 2026.09.5 · UltimateClans: 9.1.4 · Documentation branch: 9 · ClanNexus
ClanNexus practical usage guide#
ClanNexus adds clan nexus/land centerpiece addon with territory data, map/hologram integration, sentinel behavior and persistent nexus state. 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: Use the addon command/GUI to create or manage the clan Nexus according to its configured requirements. Configure nexus type/behavior, territory/map display and any sentinel options before enabling combat behavior. Verify claim/unclaim and region-entry behavior with a test clan.
Recommended in-game workflow#
- Use the addon command/GUI to create or manage the clan Nexus according to its configured requirements.
- Configure nexus type/behavior, territory/map display and any sentinel options before enabling combat behavior.
- Verify claim/unclaim and region-entry behavior with a test clan.
- If sentinel mode is used, test activation, target behavior and idle state with online members before increasing combat values.
Administrator setup checklist#
- Map/hologram/entity implementations are optional integrations; a missing provider should degrade predictably rather than be treated as a storage error.
- Keep nexus/terrain persistence backed up before changing structure or region definitions.
- Tune sentinel activation and online-member requirements for performance on servers with many inactive clans.
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—date_format_short,money_format,gui,Nexus,map,Icon,Permissions,logger,ModulesStorage—type,mysql,user,pass,databases
Changing settings safely#
- Back up the component configuration and persistent data before changing a live server.
- Change one feature area at a time.
- Reload only if the component documents reload as safe; otherwise restart the server.
- Test with a non-OP account that has exactly the intended clan role/permission.
- Watch the console from the first relevant warning/error, not only the final stack trace.
- On multiserver networks, repeat the check on every node and confirm shared storage/sync settings match.