Age of Origins Capital War Guide for Alliance Leaders
Attack only when you expect to win by roughly twice the opponent’s value in Kill Event scoring or three times their value in Void War scoring. A close win can still feed the opponent points. Capital War rewards coordination and scoring discipline, not raw alliance power.
When should we attack, defend or hold?
Do not ask whether a member can win. Ask whether that member can win by the required scoring margin. This distinction should control every target call.
| Situation | Decision | Reason |
|---|---|---|
| Expected Kill Event advantage is roughly 2x or better | Attack | The fight can produce net points. |
| Expected Kill Event advantage is below roughly 2x | Hold | A close result can feed the opponent points. |
| Expected Void War advantage is roughly 3x or better | Attack | The fight can produce net points. |
| Expected Void War advantage is below roughly 3x | Hold | Winning the fight is not enough. |
| Defense does not clear the same margin | Avoid the exchange | Defense scores fewer points than attack. |
The margin is the gate, not a rough goal. If the expected result sits near the line, hold. A close loss is bad, but a close win is not a useful fallback. Both can turn your troops into points for the other alliance.
Make this rule clear before the event so members do not treat every beatable city as an approved target. A member who sees a possible win should still wait for the value check and the attack call. Fewer attacks with a sound margin are better than many close fights.
Attack is the preferred choice because defense scores fewer points. Defense only makes scoring sense when it clears the same threshold: roughly 2x under Kill Event scoring or 3x under Void War scoring. Do not lower the standard because your member is defending.
Who should lead each rally?
Put the alliance’s strongest, best invested player at the front. Rally effectiveness follows the rally leader’s own stats, so leadership is a combat choice, not a reward, rotation or title.
The rally leader runs a hard hit formation. Never put a stagger formation on the rally leader. Stagger belongs only on staggered, non-rally attacks.
Use a short rally checklist:
- Confirm that the target clears the scoring margin.
- Assign the strongest, best invested available player as rally leader.
- Confirm that the leader has a hard hit formation.
- Keep stagger formations on staggered, non-rally attacks only.
- Set the landing order before members launch.
Do not let several members start separate actions because each thinks the target looks good. One clear leader, one target decision and one landing plan make the alliance’s power count as a coordinated hit.
How should we time a called attack?
Plan one narrow landing window. Members should launch at the times needed for their hits to arrive a few seconds apart, with the rally leader’s fleet landing first.
The order matters as much as participation. Do not replace a landing plan with a general call for everyone to attack. Each member needs to know whether they are part of the operation and when their hit should land.
Keep alliance chat quiet while the operation is live. Callouts must stay visible. Extra messages make it harder for members to follow the target, order and timing that were already set.
A useful call contains only what the group needs: the target, the rally leader, the required landing order and whether each member should join or hold. Once the call is active, members follow it rather than reopening the target debate in chat.
Which targets are worth attacking?
Choose by troop value, not by the size of the stack. A large stack of low tier troops scores poorly. A small stack of high tier elite troops scores heavily.
This changes how leaders should scan possible fights. A large troop count is not enough reason to attack, and a small troop count is not enough reason to ignore a target. First judge the value at stake. Then apply the scoring margin.
| Target signal | Leader response |
|---|---|
| Large stack of low tier troops | Do not assume high scoring value from size alone. |
| Small stack of high tier elite troops | Treat it as a heavy scoring target. |
| Likely result below the required margin | Hold, even if the fight looks winnable. |
| Likely result clears the required margin | Call the attack and coordinate the landing window. |
Target value and scoring margin must pass together. A valuable target is still a bad call if your attacker cannot clear the margin. A favorable fight against a poor scoring target may add little. The leader’s job is to reject either mistake.
How do we stop members from becoming points sources?
Review the roster before the event. Remove inactive or badly under-powered members when they cannot clear the scoring margin against likely attackers. Leaving them in the alliance gives the enemy a points source.
This is not a judgment about effort or loyalty. It is a scoring decision. If a member cannot produce the required advantage and is likely to give that advantage to an attacker, the roster itself creates risk.
Members also need a clear choice between attacking and staying shielded. A member who attacks cannot be shielded at that moment. Do not issue an attack call as though the same member can keep both states.
Troops can be hidden by sending a 30 minute rally at a dead or inactive city, or at a friendly farm. That keeps those troops off the map when an attack lands. Use this as a specific protection call for troops that should not be present for the incoming hit.
Before any operation, divide members into clear groups:
- Members approved to attack because they can clear the scoring margin.
- Members who should hold rather than take a close fight.
- Members who should keep troops off the map during an incoming attack.
- Members whose place on the event roster creates an avoidable scoring risk.
How should we standardize formation callouts?
TA, ATA, STA and SATA are common shorthand, but the terms do not have one safe meaning across the available guidance. Agree on one alliance naming standard before the event and write it in alliance chat.
Do not assume every member reads an acronym the same way. The written standard should make one confirmed split unmistakable: rally leaders use a hard hit formation, while stagger formations belong only on staggered, non-rally attacks.
What preparation belongs outside the operation?
Keep routine account work separate from combat calls. Members who use tools for farming Age of Origins accounts can cover resource farming and daily tasks as preparation. That support does not win Capital War and does not replace target choice, margins or timing.
Members can also check current Age of Origins codes before the operation. Once a call starts, the alliance should focus on the target, landing order and scoring rule.
FAQ
Is a normal win enough to approve an attack?
No. Attack only when the expected win clears roughly 2x the opponent’s value in Kill Event scoring or 3x in Void War scoring. A close win can feed the opponent points.
Should the rally leader use a stagger formation?
No. The rally leader uses a hard hit formation. Stagger belongs on staggered, non-rally attacks only.
Should we defend instead of attacking?
Prefer attacking because defense scores fewer points. Defense only makes scoring sense when it clears the same 2x Kill Event or 3x Void War margin.
Why remove an inactive or under-powered member?
A member who cannot clear the required margin against likely attackers can become a points source for the enemy alliance. Removing that risk before the event protects the alliance’s score.
