Wiki Release: 2026.09.5 · UltimateClans: 9.1.4 · Documentation branch: 9 · ClanNexus

ClanNexus#

ClanNexus adds clan nexus/land centerpiece addon with territory data, map/hologram integration, sentinel behavior and persistent nexus state. 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: 5.0.1
Documentation release: 2026.09.5
Minimum UltimateClans version: 9.0.0

What you can do with it#

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

How it works#

ClanNexus addon model#

ClanNexus is the UltimateClans addon that places persistent clan Nexus/land structures into clan territory. It is distinct from the standalone UltimateNexus plugin. The addon manages claim/unclaim, structure placement, saved Nexus state, region/chunk activation, hologram/map integration and the optional dynamic Sentinel behavior.

A Nexus should be configured/claimed only where the clan has valid land/region rights. For Sentinel mode, movement/combat activation is intentionally conditional so inactive/empty clan territory does not continuously consume server resources.

First setup#

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

chat.yml
commands.yml
config.yml
gui.yml
language/Lang_EN.yml
polymart.yml
structures/structures.yml

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.

Useful command entry points#

/{_clan} {_nexus}
/{_clan} {_nexus} {_claim}
/{_clan} {_nexus} {_unclaim}
/{_clan} {_nexus} {_delete}
/{_clan} {_nexus} {_go} (tag|player)
/{_clan} {_nexus} {_sethome}
/{_clan} {_nexus} {_info} (tag|player) (-gui)
/{_clan} {_nexus} {_view} (-gui)
/{_clan} {_nexus} {_power} (tag|player) (-gui)
/{_clan} {_nexus} {_map}
/{_clan} {_nexus} {_trust}
/{_clan} {_nexus} {_untrust}
/{_clan} {_nexus} {_trusted} (-gui)
/{_clan} {_nexus} {_ban}
/{_clan} {_nexus} {_unban}
/{_clan} {_nexus} {_banned} (-gui)
/{_clan} {_nexus} {_settings}
/{_clan} {_nexus} {_show}

See Commands in the sidebar for the full command reference and configured aliases/permissions.

GUI areas#

The installed GUI configuration contains screens/sections such as:

Nexus.home_noland
Nexus.home_hasland
Nexus.nexus_delete_confirm
Nexus.nexus_settings
Nexus.nexus_banned
Nexus.nexus_trusted
Nexus.nexus_terrains

What administrators should configure#

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.

Configuration map#

config.yml — Config (date_format_short, money_format, gui, Nexus, map, Icon, Permissions, logger, Modules); Storage (type, mysql, user, pass, databases)
chat.yml — Chat (commandunknownplayer, commandunknownadmin, wildernessenter, nexuscreate, nexusenter, nexusbanned, nexusinside)

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
Nexus exists in storage but is not visible	Map/hologram/entity provider or structure rendering is unavailable	Check implementation detection and the first Nexus-specific startup warning.
Sentinel does not activate	Online-member/region activation requirement, combat disabled or no eligible target	Enter the region with an eligible member and verify sentinel/combat settings.
Old Nexus remains after clan removal	Delete/unclaim lifecycle did not complete or stale storage exists	Use the addon delete/unclaim flow, then inspect persisted Nexus/terrain records before manual deletion.
Map marker is stale	Map integration update task/provider is unavailable or state has not synchronized	Verify map implementation and force the supported update/reload path.

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