Agree on the target and the result
Name the exact target and decide what the operation is meant to achieve. Ordinary rallies target Strongholds and the Crown Citadel; ordinary cities and reward Camps are not eligible. Clan Towers use their separate Tower rally rules. A win is not always permission to occupy the target.
Scout before assembling an expensive force. Share the report time along with the numbers so participants know how old the intelligence is. If the owner, defenses or protection changes while the rally is forming, revisit the plan rather than treating the first report as a reservation.
Read the roster before pressing Launch
An ordinary rally needs 2–20 contributors, and a clan can have up to five active rallies. Every contributor must be Ready before launch. Assembling rallies do not automatically expire, so an abandoned preparation can continue to occupy attention and capacity until it is dealt with.
Read the roster by ruler and contribution. Reinforcements and rally reservations are real troop commitments, not extra copies of soldiers who can simultaneously defend their source. Each member should check the garrison left behind before confirming readiness.
If the leader is waiting on one participant, resolve that participant’s status deliberately. Repeatedly trying Launch is less useful than discovering that a contribution was changed or never marked Ready.
Use the slowest contribution for timing
The rally travels together according to its slowest participant’s qualifying journey. Do not announce an arrival based only on the leader’s personal travel preview. Read the final rally timing with the actual members and troop counts included.
In an illustrative plan, one contribution would take twelve minutes and another twenty. Planning around twelve gives the defender less time on paper than the real rally allows. Recheck the estimate when the roster changes, and make sure allies assigned to defend your source cities understand the longer absence.
Each contributor brings their own preparation
Rally troops use their contributors’ applicable skills and equipment; the leader does not lend one universal attack build to every soldier. Attack-side values are committed at launch. Saving an attack preset without applying it beforehand does not prepare that contribution.
Have members inspect their live build and available troops before marking Ready. An old saved preset can leave newly earned points unspent when applied. If a member changes preparation, confirm the resulting state before launch rather than assuming a later equipment swap will improve the army already marching.
Plan the result as carefully as the departure
At launch, the server rechecks ownership, relationships, readiness and target eligibility. A rejection means the current state no longer satisfies the order; reopen the relevant panels before attempting a revised plan.
After the battle, read the report and inspect where survivors are stationed or returning. A Stronghold or Citadel victory makes the creator the personal controller, with allied survivors stationed as reinforcements. Tower capture instead creates a clan-owned holding. Arrange the next garrison and review the wall rather than sending every survivor straight into another operation. If the plan changes, use the eligible retreat or return controls. A rally return goes to its original city if still owned, to the participant’s Main City if that source is neutral or clan-owned, and attacks the source if an enemy now owns it. Follow that route in Kingdom Activity.
