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.
| Holding | Reinforcement defense | Wall behavior |
|---|---|---|
| Regular city | Sender's eligible soldier-defense package | Shares the city's one wall |
| Stronghold or Citadel | Sender's eligible soldier defense plus current objective rules | Shares the objective's one wall |
| Reward camp | Exactly 1.00 per troop | No wall exists |
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 eligible Stronghold, Crown Citadel, or reward camp. The rally holds up to three rulers: the rally leader and two allies. There is no automatic launch timer. The leader decides when to launch or cancel.
- Select the eligible objective and choose Rally.
- Commit troops from an owned city or Stronghold.
- Open Clan → War Room or Kingdom Activity → Rallies.
- Review participant slots, assembled troops, inbound totals, and arrival times.
- Wait for the intended contributions or launch with the assembled force.
Forming rally details and the final objective remain private to current clan members. Other players can still see contribution marches traveling toward the leader's assembly city. Committing troops immediately removes the contributor's active Royal Peace Shield; cancellation or withdrawal does not restore it.
Only assembled troops leave with the rally
Allies may withdraw before launch. If the leader launches while a contribution is still inbound, that contribution turns around automatically and does not join the attack. This makes the inbound timer a real coordination constraint instead of a cosmetic status.
After launch, the combined force appears as a normal incoming attack and the objective becomes visible to the defender. The rally uses the leader's march bonuses while each participant keeps the attack strength captured for that contribution. Only the rally leader may spend a Recall Horn on the launched combined army.
After battle or recall, allied survivors return toward their source holding or redirect to the Main City if that source is no longer available. The resulting reports preserve each contributor's role so a clan can review whether the assembly size, launch timing, and target selection worked.
A practical rally checklist
- Choose an objective whose bonus supports the clan's current problem.
- Set a clear launch condition instead of waiting indefinitely.
- Check every contribution arrival before launch.
- Warn members that commitment removes an active Peace Shield.
- Keep enough local defense to survive the counterattack.
- Read the final report as a team before repeating the plan.