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

RivalAlly#

RivalAlly adds clan alliance and rivalry requests, relationships, limits, GUI and placeholders. 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.5
Minimum UltimateClans version: 9.0.0

What you can do with it#

Use ally/rival commands to send/manage a relationship request
Accept/deny from the target clan where required
Verify relationship effects in other modules/addons that consume ally/rival state

How it works#

Relationship model#

RivalAlly maintains alliance and rivalry state, including requests, acceptance/denial, removal, limits and GUI search/listing. Other features consume this relationship state for PvP, rewards, FarmCoins combat categories and similar behavior; changing RivalAlly does not automatically override every addon's own relationship settings.

First setup#

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

commands.yml
config.yml
gui.yml
language/Lang_EN.yml
language/Lang_ES.yml

Recommended in-game workflow#

Use ally/rival commands to send/manage a relationship request.
Accept/deny from the target clan where required.
Verify relationship effects in other modules/addons that consume ally/rival state.

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.rival
General.ally
General.clan_rival_search
General.clan_ally_search

What administrators should configure#

Set relationship limits, invite expiration and role permissions deliberately.

Configuration map#

config.yml — Config (date_format_short, Rival, Ally, Permissions, unlocker)

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
Ally request cannot be accepted	Request expired, limit reached, clans already related or permission missing	Check active request, relationship limits and clan state.
PvP behavior does not match relationship	The protection/combat addon has its own ally/rival setting	Check the consuming module/addon, not only RivalAlly.
Duplicate relationship appears on network	Cross-server state is not synchronized	Verify shared storage/multiserver sync.

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