Coordinate armies without losing who owns them

Roles control coordination, not personal kingdoms

Clan leaders and officers can review applications, manage permitted roles, and remove members. Leaders and officers may form rallies. Every member can inspect the current rally state and use the controls allowed by their participant status.

Membership creates allied relationships on the map. Clanmates cannot treat allied cities as normal enemy targets. They can instead reinforce eligible holdings, coordinate objective control, compare progress, and communicate through the clan systems and the War Room.

Leadership is most useful when responsibility is explicit: who owns the objective plan, who can supply nearby support, which cities must remain defended, and when an operation is no longer worth additional troops.

Reinforcements join the garrison behind one wall

A reinforcement march transfers troops to an allied eligible holding without changing their owner. In a city or objective siege, those troops join the combined garrison and use their sender's applicable live soldier-defense package. They do not create an extra wall, copy Stoneworks, or adopt the holding owner's skill allocation.

Reward camps are different. They have no wall or level, and every stationed or reinforcing troop contributes exactly 1.00 defense power. Skills and objective support do not change camp defenders.

Assignments reserve capacity while troops travel

Each ruler may maintain two reinforcement assignments with each clanmate, limited to one contribution per holding. An ordinary city reserves at most five reinforcement contributors. That reservation begins when the support march launches, so a slow inbound march still occupies a contributor slot.

Allied Strongholds and reward camps do not use the ordinary city's five-contributor limit. The per-clanmate assignment rules still provide a readable boundary for each pair of rulers.

Use capacity deliberately. A token reinforcement can occupy the same contributor slot as a meaningful defensive package. Before sending, compare travel time, the incoming threat, and whether another clanmate is better positioned to fill the limited city slot.

Survivors try to return to their source

The sender can recall stationed reinforcements. The holding owner can send allied troops home. Battle losses are applied while they defend the position. Surviving troops normally return to the exact city or Stronghold they originally left.

If that source holding has been captured before departure or before the return march arrives, the server redirects surviving troops to the sender's current Main City. Assignment capacity remains occupied until the return arrives unless no troops survived.

The War Room forms one combined objective attack

A Leader or Officer can form a Rally against an enemy Stronghold or the Crown Citadel. Any active clan member may join with one army from one city. Each Rally supports 2–20 participants, and a clan may maintain up to five active Rallies. There is no expiry or automatic launch timer.

1. Select an eligible objective and choose Rally.
2. Commit troops from an owned city or Stronghold.
3. Open Clan → War Room or Kingdom Activity → Rallies.
4. Review the Ready participants and any troops still inbound.
5. The creator or Clan Leader manually launches the Ready force; incoming contributions turn back.

Forming Rally details and the final objective remain private to current clan members. Other players can still see contribution marches traveling toward the creator's assembly city. Committing troops does not remove an active Royal Peace Shield.

Launch with the Ready force

Members may withdraw before launch. Launch is blocked with an explanation if fewer than two eligible participants are Ready (three for Tower targets), the creator has no Ready troops, a member or assembly holding has become invalid, or the objective is no longer eligible and hostile. The launch confirmation lists inbound contributions that will turn back from their current positions. Arrived troops defend the assembly holding until launch; combat casualties reduce the force available to the rally.

After launch, the combined force appears as one incoming attack and travels at the slowest participant's locked march speed. Every participant keeps that ruler's own attack skills, Common Gear, and applicable bonuses. Only the creator may spend a Recall Horn on the launched combined army. If the creator leaves, is removed from, or changes clans, the server recalls the whole Rally automatically.

Losses are divided proportionally by troops contributed. A defeated Rally has no surviving attackers. On victory, the creator controls the Stronghold or Citadel and the creator's survivors hold it; allied survivors become individually attributable reinforcements stationed there. Every participant receives the same Rally outcome with clearly labeled individual committed troops, losses, survivors, and attack power.

A practical Rally checklist

• Choose an objective whose bonus supports the clan's current problem.
• Set a clear manual launch condition.
• Confirm the required Ready contributors, including the creator, and review who will turn back.
• Remember that the slowest contribution sets the combined march speed.
• Assembled troops defend locally until launch; review the garrison that will remain afterward.
• Read the shared participant report as a team before repeating the plan.