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

HuskClaims extension#

What it is for#

This extension is a protection integration. Its role is to allow compatible clan features to coordinate with HuskClaims ownership/regions. Extensions are adapters: they do not replace the external plugin and usually do not provide a separate player command system of their own.

Installation#

1. Install and start the external plugin/provider first.
2. Place the matching TribeCraft extension JAR in the UltimateClans extension location used by V9.
3. Restart the server, or use the supported extension reload flow when appropriate.
4. Use /uclan extension list or /uclan extension view to confirm the adapter is loaded. The supplied Core command tree also supports all, download, update and reload.
5. Test the feature that consumes the extension. For example, a hologram extension is only proven by creating/updating a hologram from a clan addon that uses holograms.

How to verify it is actually being used#

• Confirm the external provider is enabled before UltimateClans finishes loading integrations.
• Confirm the extension appears active in the extension manager.
• Trigger one simple supported operation.
• Check the first integration-specific warning if the operation falls back or fails.

Troubleshooting#

Extension is listed but feature still does not work#

The adapter can be loaded while the external provider is misconfigured or the consuming addon/module has that feature disabled. Verify all three layers: provider → extension → consuming feature.

Extension is inactive after an update#

Check provider/API compatibility and use the extension build intended for the current UltimateClans branch. Do not copy an old V8 integration JAR into V9.

Multiple providers are installed#

If more than one economy/hologram/map implementation is present, verify which implementation UltimateClans selected. Test with only the intended provider if selection is ambiguous.

Network/multiserver difference#

Install/configure the provider and matching extension consistently on every server where that feature runs. A map renderer might intentionally run only on one node, but that should be a deliberate setup.