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

ClanLand#

ClanLand adds clan land claiming and protection with configurable PvP/TNT/liquid/mob rules, bossbar/hologram/map feedback, decay and persistent land data. 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: 4.0.1
Documentation release: 2026.09.5
Minimum UltimateClans version: 9.0.0

What you can do with it#

Claim land through the configured clan land command/GUI after meeting clan/permission/limit requirements
Enter/leave the claimed area and verify bossbar/hologram/map feedback
Test members, allies, rivals and outsiders against block, container, PvP, TNT, liquid and mob rules that you actually enable
Configure decay only after normal claims and unclaims are working

How it works#

Claim flow#

ClanLand turns configured terrain/claim rules into clan-owned regions. A claim command identifies the current location/chunk/region according to the addon mode, validates clan permissions/limits and protection integrations, then persists the land. Join/leave listeners drive enter/exit messages and bossbar/hologram/map updates where enabled.

Before players can claim, configure claim limits/costs, allowed/blocked worlds or regions and any map/hologram/protection integration you want to expose. Test both claiming and unclaiming with the lowest intended clan role.

First setup#

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

bossbar.yml
commands.yml
config.yml
gui.yml
language/Lang_EN.yml
polymart.yml

Recommended in-game workflow#

Claim land through the configured clan land command/GUI after meeting clan/permission/limit requirements.
Enter/leave the claimed area and verify bossbar/hologram/map feedback.
Test members, allies, rivals and outsiders against block, container, PvP, TNT, liquid and mob rules that you actually enable.
Configure decay only after normal claims and unclaims are working.

Useful command entry points#

/{_clan} {_land}
/{_clan} {_land} {_claim}
/{_clan} {_land} {_unclaim}
/{_clan} {_land} {_list} (-gui)
/{_clan} {_land} {_teleport}
/{_clan} {_land} {_show}
/{_clan} {_land} {_ban}
/{_clan} {_land} {_unban}
/{_clan} {_land} {_banned} (-gui)
/{_clan} {_land} {_trust}
/{_clan} {_land} {_untrust}
/{_clan} {_land} {_trusted} (-gui)
/{_clan} {_land} {_rename}
/{_clan} {_land} {_setspawn}
/{_clan} {_land} {_view} (-gui)
/{_clan} {_land} {_settings} (-gui)
/{_clan} {_land} {_flag} set

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:

Land.home_noclaim
Land.home_claim
Land.land_info
Land.land_banned
Land.land_members
Land.confirm_unban
Land.confirm_untrust
Land.confirm_abandon
Land.home_land
Land.land_ajust
Land.land_flags
Land.anvil_land_rename

What administrators should configure#

Limits, permissions and protection flags should be tested by relationship type, not only with an operator account.
Map/hologram providers are optional integrations; validate each independently.
Back up land storage before changing world/chunk mapping or decay rules.

Configuration map#

config.yml — Config (Land, Banner, Tasks, Icon, Permissions, logger, Storage, Modules)
bossbar.yml — Bossbar (enabled, teleport, start, finish, canceled, claimed, view)

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
Claim command says location is unavailable	World/region disabled, claim overlap, clan limit or permission requirement blocks the chunk	Check world/region lists, existing owner, clan claim limit and role permission.
Protection works for blocks but not PvP/TNT	Those protections use separate listeners/settings	Review the PvP/TNT sections and test with non-OP accounts.
Bossbar/hologram missing	Display module/provider disabled or integration unavailable	Check addon display settings and provider detection.
Land disappears unexpectedly	Decay rule or clan deletion/unclaim lifecycle removed it	Review decay timing and storage logs before restoring from backup.

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