Age of Origins Capital War is the final phase of Nation Progress, and it starts the Saturday one week after your nation enters that phase. The alliance that occupies the Capital wins the Presidency. In the fights around it, attack only when you expect to win by roughly twice the opponent’s value in Kill Event scoring or three times in Void War scoring. A close win can still feed the opponent points.
Capital War opens the whole nation: the fog clears and every city can be reached. The alliance holding the Capital names the President, who hands out titles with recruitment, building, research and gathering buffs. Coordination and scoring discipline decide it more than raw alliance power.
- Saturday one week after the final Nation Progress phase begins
- 30-minute rallies at dead cities or farms hide your troops
- 4 Nation Progress phases, and Capital War is the last
Rather not do this by hand? The Age of Origins bot runs it on every account.See how it works
What is Capital War in Age of Origins and when does it start?
Capital War is the last of the four Nation Progress phases, and that phase has no tasks except the Capital. When your nation enters it, the game announces Capital War for the Saturday one week later. That week is your alliance’s preparation time.
When the phase opens, the poisonous fog clears and the nation becomes fully open to PvP. Distance stops protecting anyone. Only one alliance can occupy the Capital and win the Presidency.
Do not teleport into the Capital itself. Troops move far slower inside it, so stage nearby and march in. No reliable guide publishes how long you must hold the Capital, so check your nation’s Capital War screen.
When should we attack, defend or hold?
Ask whether a member can win by the required scoring margin, not only whether they can win. This question should control every target call. The margins below come from Packsify’s Capital War guide for alliance leaders.
| 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 | A close defensive fight still hands the attacker points. |
Treat the margin as a hard gate. If the expected result sits near the line, hold. A close loss is bad, and a close win is no 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 beat many close fights.
In Battle Frenzy, the usual kill event, attack is the better choice: a defender earns about a third of the points an attacker gets for the same kill. Void War pays attack and defense kills the same, so a well-held garrison scores as hard as a hunting march. In both, do not lower the margin because your member is defending.
Who should lead each rally?
Put the alliance’s strongest, best invested player at the front. The whole rally fights with the leader’s officers, research and formation, so pick the leader for combat, never as 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 rally timer turns each member’s march time into a send order and a countdown.
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. Points scale with troop tier, so a large stack of low tier troops scores poorly and 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.
Make this call on scoring alone, without judging effort or loyalty. 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. Rallied troops are not at home, so they cannot be killed there 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 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 run the Age of Origins bot on farm 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.
A farm account keeps the main city fed, and our Age of Origins accounts page sells them ready-made.
Age of Origins Capital War FAQ
When does Capital War start in Age of Origins?
On the Saturday one week after your nation enters the final phase of Nation Progress. The game announces it when that phase begins.
What does the winning alliance get?
The alliance that occupies the Capital wins the Presidency. The President appoints officials, and their titles give buffs such as recruitment, building, research and gathering speed.
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?
In Battle Frenzy, prefer attacking: defenders earn about a third of the attacker’s points. In Void War, defense kills pay the same as attack kills, so a strong garrison is a scoring position too.
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.
Facts checked October 31, 2026 against: ageoforiginshandbook.com guides (verified August 2026), the aozcodes.com Nation Progress FAQ and packsify.com (Capital War strategy, July 28, 2026).
Prefer BoostBot on Google so our code lists and guides show up first when you search.
Add BoostBot on Google
