Alliance-Break Timing: When 30 Seconds Is Worth the Trade

Direct answer: the break is a 30-second gamble, and you are the one who gets weaker

Break a live alliance only when you can name the concrete objective that fits inside the 30-second traitor window and you can still hold that window while your defense is halved and enemy attacks land 20% faster. Waiting for the alliance to expire costs you nothing and keeps the lull; renewing costs you nothing and keeps the lull longer. Breaking is the only option that costs you a real, self-inflicted vulnerability, so it is the only one that needs a payoff you can see in the next thirty seconds.

In v0.34 the player who clicks break becomes the traitor. For 30 seconds the ex-ally’s attacks on you are cheaper and faster, and your own defense is effectively halved, while your relation to the ex-ally drops by 100 and your relation to every nearby neighbor drops by 40. You are the exposed party for a short, known interval, not the ex-ally. If there is no objective inside that interval and you cannot survive the reduced defense, you are converting a multi-minute lull into a 30-second exposure with no payoff, and the correct move is to wait or renew instead. The rest of this guide turns that rule into a decision you can make in-match.

Think of the break as a short loan of your own defense. Waiting and renewing cost you nothing and keep the lull; breaking borrows thirty seconds of reduced defense and a hard relation drop that you have to repay with a concrete gain before the window closes. The three moves differ only in that cost. Renewing is free and keeps the lull for another full duration, so it is the right default whenever the alliance is still buying something you can finish. Waiting is also free and is the right default whenever the lull is no longer buying anything useful and the ex-ally is not yet committed elsewhere. Breaking is the only move that has a real cost, so it is the only move that needs a payoff you can name in the next thirty seconds. That is why the whole topic is about timing rather than about whether breaking is good or bad: breaking is good exactly when the payoff is real and the window is survivable, and it is bad in every other case. The decision you have to make in-match is never “is breaking a good idea in general”; it is “is there a real objective inside the next thirty seconds, and can I hold my reduced defense for those thirty seconds.”

Version boundary and the numbers that decide the timing

Every number in this guide is read from the v0.34.20 tag, released 2026-09-26, the latest non-TEST OpenFront build. The alliance and traitor rules were not changed anywhere in v0.34.15 through v0.34.20, so the v0.34-era values carry forward and this guide applies to the current build. The decisive values, read from the v0.34.20 game config, are: the traitor window is 30 seconds; while the traitor is the defender the attacker’s troop loss is scaled by 0.5 (so attacks on the traitor are cheaper and the traitor is defensively weakened); while the traitor is the defender the attack speed cost is scaled by 0.8 (so enemy attacks on the traitor take 20% less time to land); the breaker takes -100 relation toward the ex-ally; every nearby neighbor of the breaker takes -40 relation toward the breaker; a standard alliance request stays active 20 seconds with a 30-second per-target cooldown; and a standard alliance lasts 5 minutes, though a host can set a custom duration of 1 to 15 minutes, and a value of 0 disables alliances entirely.

The room settings are the boundary you must read before applying the guide. The 30-second window and the -100 and -40 drops are fixed for the current v0.34 build and do not change with the mode or the map. What changes is the alliance duration, which the host controls from 1 to 15 minutes or disables with 0, and the mode, which changes who the ex-ally is and how fast a reserve can swing to you. If the room has custom or disabled alliances, the default 5-minute lull this guide assumes does not apply, and the timing math shifts accordingly. If you are playing an older or a TEST build, the traitor values may differ, and you should confirm the numbers in that build before trusting the timing advice here. The single most important version fact is that the breaker, not the ex-ally, is the one weakened for the 30 seconds, because that is the fact the whole timing decision turns on. Two more version-boundary notes matter for the timing call. First, the -40 relation drop is not a rule that applies to the whole map; it applies only to the breaker’s nearby neighbors, which is the set of players close enough to the breaker’s position to be considered a threat, and the exact range is read from the v0.34.20 config. In a crowded FFA that set can include several players, so the -40 drop is effectively a small but visible relation hit to the neighborhood around you, and it is worth counting as a real cost when you weigh the break. In a sparse FFA or in Humans versus Nations the set is smaller, so the -40 cost is closer to zero and the -100 to the ex-ally is the dominant relation cost. Second, the alliance request numbers - the 20-second active request and the 30-second per-target cooldown - are the same numbers the alliance and betrayal strategy guide uses for the request and extension logic, and they are the reason that renewing a lull is nearly free in practice: a renewal request only costs you the 20-second request window and the 30-second cooldown on that one target, and it does not cost you any troops or any traitor window. That is exactly why the guide’s default hierarchy is break only when the payoff is real, renew when the lull is still useful, and wait when neither is true: renewing is the cheapest way to keep the lull alive, and breaking is the only move that costs you the 30-second window and the relation drops. Read the room’s actual settings - the mode, the map, and the alliance duration - before you apply the rest of this guide, because the 30-second window and the -100 and -40 drops are the constants, and everything else is variable.

Decision framework: break now, wait, or renew

The whole timing question resolves to three moves, and each has a clear condition. Break now only when both of two tests pass at the same time. The first test is the objective: a concrete thing you can finish inside the 30 seconds, such as the ex-ally’s base being exposed because its reserve is committed elsewhere, your own border having just become secure so a strike can slip through, or a port or trade route you can open that the ex-ally cannot answer in time. The second test is survivability: your own reserve is held at home and your second route is open, so that when the ex-ally turns with a cheaper and faster attack you can still hold for the 30 seconds. If either test fails, breaking is a net loss, because you are paying a full 30-second exposure for a payoff that either does not exist or you cannot bank.

Wait when the ex-ally is already massing or orienting toward you and no objective sits inside the window. Breaking in that moment removes the lull that was holding the ex-ally at bay and hands the ex-ally a cheaper, faster attack path onto you for the 30 seconds, which is exactly the moment you cannot afford it. Let the alliance expire naturally and you keep the lull with no traitor cost, and you decide again when the border actually changes. Renew when the alliance is still buying a specific action you have not finished and you can name it. Renewing costs you nothing in troops and no traitor window, and it keeps the multi-minute lull alive, so it is almost always better than breaking to save a fraction of a minute. The practical order to check is: is there an objective inside 30 seconds? Can I hold the 30 seconds? Is the alliance still buying something I can finish? The first yes that does not come with a survivability problem tells you the move; if the objective is missing or the window is not survivable, the default is wait, and if the lull is still useful, renew.

One useful way to keep the three moves from blurring together is to treat them as different costs, not different goals. Wait costs you the lull you would have had; renew costs you nothing and keeps the lull; break costs you the 30-second window and the relation drops but gives you the chance to take a specific thing the lull would not have let you take. So the question is never “which move do I want” but “what is the cheapest move that still gets the objective I actually have.” If the objective is still being bought by the lull, renew is the cheapest move that gets it, and you do not pay the 30-second window for nothing. If the objective has vanished and the lull is no longer buying anything, wait is the cheapest move, and you keep the option open. Only when the objective is real, it is inside the window, and the lull would not let you get it is break the cheapest move that gets it. That ordering - renew, wait, then break only when both the objective and the survivability tests pass - is the whole framework, and the rest of this guide is just applying it to specific positions.

Scenario A: FFA midgame, ex-ally’s reserve is committed elsewhere

Read the position first. You are in a standard FFA with the default 5-minute alliances. Your alliance with the player on your east border has 90 seconds left. That ex-ally has committed its reserve of about 140 troops to a strike on the player two seats north of you, so its own home base is defended only by the garrison it left, roughly 60 troops, and the base sits about 6 tiles from your east border. Your own position is a coastal start: you have just finished your first port and your factory is coming online, you hold about 90 troops at home, and your land border to the west is thin but not threatened because the player to your west is focused on the north fight as well. Your relation to the ex-ally is friendly and to the west neighbor is neutral.

The objective inside 30 seconds is clear and concrete: the ex-ally’s base is exposed by its own committed reserve, and a 60-to-90 troop push from your home can take that base before the 140-troop reserve turns around, because the reserve is many tiles away and cannot return in 30 seconds. The survivability test also passes: your 90 troops are held at home and your coastal second route is open, so even if the ex-ally’s garrison answers, you can hold your home for the 30-second window while the push lands. So the decision is to break now. You click break, you become the traitor for 30 seconds, you take -100 relation to the ex-ally and -40 to the west neighbor and any other nearby player, and you push the 60-to-90 troops into the exposed base. The timing works because the 30-second window overlaps exactly with the window in which the ex-ally is weakest, and because your own reduced defense matters less when the ex-ally cannot swing its reserve back in time. This is the case where breaking is the right move: a real objective, inside the window, with a survivable window. Note the two things that made this position break-able rather than wait-able: the ex-ally’s own committed reserve is the reason its base is exposed, and your held reserve is the reason you can survive the 30-second window. Remove either of those two facts and the decision flips. If the ex-ally’s reserve had not committed to the north fight, its base would not be exposed and there would be no objective inside the window, so the answer would be to wait or renew. If your own 90 troops were out in the open instead of held at home, you could not hold the 30-second window against the ex-ally’s garrison and any nearby -40 neighbor, and the answer would again be to wait. The break is only affordable when both the exposure you want and the defense you need are present at the same time, and that coincidence is rare enough that most of the time the right answer is the free move, not the costly one.

Scenario B: HvN, the Nation is massing on your border

Now read a position where the same instinct to break is the wrong move. You are in Humans versus Nations. Your alliance with the Nation to your north is 40 seconds from expiring. The Nation is not committed elsewhere: its AI queue is orienting a reserve of about 120 troops toward your northern border, and you can see the stack forming because the Nation is weighing the border it can safely beat and the retaliation a break would invite. Your own position is an enclosed inland start: your home is a compact cluster of about 8 tiles, your reserve of 70 troops is held at home, but your only second route is a narrow isthmus to the south that a Nation push can cut if it comes fast enough. Your relation to the Nation is friendly, to the two neighboring players is neutral, and to the human to your east is slightly positive.

There is no objective inside 30 seconds. The Nation’s reserve is not committed to a far target; it is forming on your own border, which means the only thing a break does is remove the lull while the Nation is already pointing at you. The survivability test fails: your enclosed start has no easy second route, the isthmus can be cut, and your 70 troops against a 120-troop Nation push that is cheaper and 20% faster for 30 seconds is not a fight you hold. Breaking here would take -100 relation to the Nation, turn the Nation fully hostile, and give the Nation a cheaper, faster attack path onto an enclosed player with no second route, for exactly the 30 seconds the Nation is already massing. The decision is to wait: let the 40 seconds expire, keep the lull, and hold the isthmus while the Nation’s queue decides. If instead the Nation had committed its reserve to a far objective and its home were exposed, the math would flip toward breaking, but with the Nation massing on your own border the only affordable moves are to wait and to keep the lull alive, and if you need the lull to finish a specific build you renew rather than break. The lesson is that the same 30-second window is a weapon in one position and a liability in the next, and the difference is whether the ex-ally’s reserve is committed elsewhere or pointed at you, which is the single fact to read before every break call in this mode.

Failure modes and the counterplay that fixes each one

The most common failure is breaking while your own attack stack is out in the open. You press break to take the ex-ally’s border, but your troops are committed more than 10 tiles from home and your own border is thin, so the ex-ally’s counter has a short path onto you while you are already weakened. Breaking then converts a survivable lull into a 30-second exposure you cannot close, and the -100 relation and the -40 neighbor drops mean the ex-ally and every nearby player are suddenly hostile and will attack the one exposed, weakened target on the map. The counterplay is simple: do not commit to the break until your reserve is held at home and your border is secure, or until a second route is open. If your stack is out, wait until it returns, then re-evaluate the window.

The second failure is breaking to gain a small border and then stalling for the full 30 seconds, which wastes the window. The break buys you a moment, not a minute: if you do not commit to a concrete objective inside the 30 seconds, you expire at -100 with no advantage while the ex-ally regroups, and the nearby players who took the -40 hit can now attack you with less risk. The counterplay is to name the objective before you break, not after, and to abandon the break the moment the objective is gone. If the base you meant to take is no longer exposed, or the border you meant to open is no longer open, the 30-second payoff is gone and the break is just a cost.

The third failure is breaking in Humans versus Nations without reading the Nation’s queue. The Nation is not a human who can make a promise; it is an AI that weighs the border it can safely beat and the retaliation a break would invite, and it can swing a reserve faster than a human across a compact map. If the Nation is massing on your border and you break, the -100 hostile Nation has a cheaper and faster attack path onto you for 30 seconds and can land it because the queue is already oriented toward your border. The same break that is survivable in FFA, where the ex-ally’s reserve is committed elsewhere, is fatal in HvN when the Nation is oriented at you. The counterplay is to check the Nation’s current orientation and reserve position before you break, and to break only when the Nation is committed to a far objective and its reserve cannot reach your border inside the 30-second window.

Mode and map adjustments that change the timing

The 30-second window and the -100 and -40 drops are the same in every mode and on every map, but the surrounding conditions change when a break is affordable. In a standard FFA with the default 5-minute alliances the lull is short, so breaking must line up with an immediate objective because there is little lull left to bank; waiting wastes the lull, but a break without a payoff is a 30-second exposure you can never recover. In FFA the -40 neighbor drop also reaches more nearby players, and each of them is a potential attacker on you during the weakened window, so on a crowded FFA map a break is more visible and more likely to draw a nearby attack at the worst possible time.

In a custom room the host sets the alliance duration from 1 to 15 minutes, and that setting is the single biggest timing lever. In a 15-minute room the lull is long, so waiting is much more attractive: you can bank several objectives before the lull ends, and a break that only saves a fraction of a minute is a bad trade against keeping the whole lull. In a 1-to-2-minute room the lull is so short that waiting is nearly worthless, and the break is almost as good as the lull itself, which pushes the timing toward breaking earlier. Read the room’s actual duration before you decide, because the same position that says wait in a 15-minute room says break in a 2-minute room.

On larger maps the -40 neighbor drop reaches more third parties, and your reserve has farther to move, so a break is more visible, takes longer to close, and leaves you exposed for a longer effective time; the 30-second window is the same, but your ability to survive it is lower because you have fewer nearby troops and a longer reposition. On smaller and compact maps the opposite holds: the neighbor drop reaches fewer players, your reserve can reposition quickly, and the 30-second window is easier to hold, so breaking is more often affordable. In No-alliances mode the break is unavailable, the whole guide’s timing question does not apply, and your play reduces to pure attack and defend timing; in that mode the only relevant fact here is that the ex-ally is always hostile and there is no lull to spend. In every mode, the timing answer is the same three tests, and only the surrounding numbers change: is there an objective inside 30 seconds, can you hold the 30 seconds, and is the lull still worth keeping.

Decision table for the break-now call

Use this table to resolve the call in one read. The columns are the situation you are in and the move it points to, with the 30-second traitor window as the constant you are spending.

Situation in-match	Move	Why it is the right call
Ex-ally’s reserve committed to a far target; its base exposed by about 60 troops and 6 tiles from you; your reserve held at home	Break now	A concrete objective is inside the 30 seconds and you can hold the reduced-defense window at home; the break overlaps the ex-ally’s own weakest moment.
Ex-ally massing a reserve on your own border; no objective inside the window; your start is enclosed with no open second route	Wait	Breaking removes the lull while the ex-ally already points at you and gives it a cheaper, faster attack path onto a player who cannot hold the 30 seconds.
Alliance still has several minutes left and you have a specific build or move you have not finished	Renew	Renewing costs no troops and no traitor window and keeps the multi-minute lull alive, which is almost always better than breaking to save a fraction of a minute.
Custom 15-minute room; lull still long; no objective inside 30 seconds	Wait or renew	A long lull makes waiting cheap; a break that saves little time is a bad trade against keeping the whole lull.
Custom 1-to-2-minute room; lull nearly over; an objective just became available	Break now	A very short lull makes waiting nearly worthless, so the break is almost as good as the lull and the payoff is real.
FFA crowded map; you would take -40 from several nearby players	Prefer to wait	Each nearby player is a potential attacker during your weakened window; the extra visibility makes the 30-second exposure harder to hold.
Compact map; few nearby players; your reserve can reposition in a few tiles	Break is more affordable	Fewer -40 targets and fast repositioning make the 30-second window easier to hold, so the break is more often a net gain.

The table is a read, not a rule: if two rows seem to apply, the survivability row wins, because a break you cannot hold for 30 seconds is a loss no matter how good the objective looks. When in doubt, the default is the move that costs you the least: renew if the lull is still useful, wait if it is not, and break only when both the objective and the survivability tests pass together.

Pre-break checklist and a completion test

Run this list in the few seconds before you click break; it is the same as the framework above but in the order you check it in-match. First, name the objective in one sentence: what exactly does the 30-second window buy you, and is that thing still true right now? If you cannot say it in one sentence, do not break. Second, check survivability: is your reserve held at home and is your second route open? If your stack is out in the open and your border is thin, the answer is wait or renew, not break. Third, check what the alliance is still buying: if it is still buying a specific action you can finish, renew, because renewing is free and keeps the lull. Fourth, read the room’s actual alliance duration: in a 15-minute room waiting is generous, in a 1-to-2-minute room it is nearly worthless, and that changes the break-versus-wait call. Fifth, read the map: how many neighbors will take the -40 drop and how far does your reserve have to move to hold or to reposition? Sixth, read the mode: in Humans versus Nations the Nation’s queue and orientation decide whether its reserve can reach you in 30 seconds.

Write the completion test before you click, the way the Nation decision guide does for the request: if I break, I finish this one objective by second 25 and I retreat to this position; if the ex-ally counter-attacks, my held reserve answers it from this position. If you cannot fill that sentence with a real objective and a real retreat position, the break is not ready. This checklist is the same logic as the Nation alliance decision page applied to the moment of breaking, and it complements the general alliance and betrayal strategy rules for request timers and extension rather than replacing them. The one line that carries the whole guide is this: the break is a 30-second gamble in which you are the one who gets weaker, so you break only when a real payoff is inside the window and you can hold the window, and otherwise you wait or renew. If you can run this checklist in the few seconds before the click and any step comes back with a no, the default is the free move, and you have saved yourself a 30-second exposure you cannot afford. That is the whole discipline of the timing call: the objective, the survivability, the lull still being useful, the room duration, the map, and the mode, in that order, with the free move as the fallback whenever the costly one cannot be justified.