GUIDES
Reacting to an Ally's Betrayal: Your 30-Second Counter-Window
When a teammate or ally betrays you in OpenFront v0.34, the betrayer — not you — is marked the traitor and weakened for 30 seconds. Decide whether to strike back during that window, hold and embargo, or re-ally, with the 0.5 loss / 0.8 speed debuffs, the 5-minute embargo, and the -100/-40 relation drops.
Direct answer: when your ally betrays you, the betrayer is the one who gets weaker
In v0.34 the player who clicks “break” or “betray” is the one marked a traitor for 30 seconds — you are not. During those 30 seconds their defense cost is cut by half, so the troops they have to lose to defend your attack are halved, and attacks land on them 20% faster, while your relation to them has already dropped by 100. The counterintuitive part is that this means your counter-attack on the person who just stabbed you is the cheaper and faster one, not theirs. This is the mirror of the alliance-break timing question, which is written from the side that breaks the alliance — this guide is the other half of that conversation, the side that gets broken. So the immediate move is rarely “defend and hope.” It is “strike back now, while the one who betrayed you is the weakened one, if you have enough troops to actually break through.” If you do not have enough troops to break through, the correct move is to stop, defend, and let the 5-minute embargo freeze their economy while you rebuild.
The reason the instinct to tuck in and defend is the wrong default is that it hands the betrayer the one window in the game where they are mechanically weaker. A player who breaks an alliance is gambling that the 30 seconds of their own reduced defense cost is worth the territory or the escape, and that bet is only as good as their ability to use the window. If you simply fold, you remove the only pressure that could make the bet fail, and the betrayer walks away with a gain they paid for with a debuff that was supposed to make the move expensive. The whole guide rests on that single reversal: the moment you see the betrayal, the tactical initiative transfers to you for 30 seconds, not to them. The rest of the guide turns that reversal into a decision you can make in the five seconds after the betrayal happens, and it walks through what changes mechanically, what the 30 seconds actually break down into, the three defensible moves, how to act inside and after the window, the embargo and the relation drops, mode and map adjustments, and the failure modes that turn a survivable betrayal into a lost game. If you only take one line from it, take this one: when your ally betrays you, the question is never “how do I survive this” but “how do I make them pay for the 30 seconds they just created.”
What actually changes when the betrayal lands: the traitor flag and who gets debuffed
The single most important thing to understand about a betrayal is which side becomes the traitor, because everything else follows from it. When a player breaks an alliance they are with, the game sets that player’s isTraitor flag true for 30 seconds and records a BrokeAlliance event that names the breaker as the traitor and the other player as the betrayed one. The betrayed player — you — does not get the flag. So the “traitor” label in the HUD, the small icon above the player’s name, and the in-game Alert Frame that pops when you are betrayed all refer to the other side being marked, not you being punished. This is the part most players get backwards: they see a betrayal and assume they are now the exposed one, and they immediately tuck in and defend. You are not the exposed one for those 30 seconds. The person who betrayed you is, and the game is telling the whole map that they are.
The traitor flag does three mechanical things to the marked player, and each one works in your favor during the window. First, while their isTraitor is true, any attack you launch against them gets a traitor loss modifier applied: the defending traitor’s troop cost in the combat calculation is multiplied by 0.5 before troops are traded, so the defender sheds about half as many troops as a non-traitor would against the same attack. Second, the same flag applies a 0.8 modifier to the attack’s tick progression against them, meaning each tile of their territory resolves in 0.8 of a normal tick — roughly 20% faster than a normal attack of the same size. Third, the relation to their ex-ally (you) drops by 100 and their relation to each adjacent neighbor drops by 40, and a 5-minute temporary embargo on trade between you is set. All of these attach to the breaker, and they are exactly the three numbers the in-game tooltip warns the player about when they choose to betray: the 30-second mark, the 50% defense debuff, and the 5-minute trade pause. The upshot is that the window after a betrayal is the one moment in the game where the person who just made a hostile move is simultaneously more expensive to defend against (for the attacker) and easier to crack, and everyone else on the map can see which player that is by the icon and the relation line. That is not a small advantage to hand back. If you are not going to use those 30 seconds, someone who was already planning to take that player is, and the traitor flag makes them the obvious target.
The 30-second counter-window, broken into five second-markers
The 30-second window sounds like it gives you time to think, but in practice it is really five decision points you hit in fast succession, and the players who win the betrayal are the ones who treat it as a countdown rather than a discussion. At second zero the betrayal lands: the icon appears above their name, the Alert Frame pops if it is on, and the relation line turns fully hostile. Your job in the first two seconds is only to confirm the betrayal is real and not a misread of the HUD — check that the icon is on their side and that the relation between you is now at the hostile floor. A false positive (you think they broke and they did not) costs you the chance to hold the lull and to strike them at the cheap rate, so the confirmation step is cheap and worth it, and it also keeps you from committing an attack that would read as an unprovoked first strike if they never actually broke.
By second five you need to have decided one of two things: either you are going to commit troops to strike them back in this window, or you are not. The decision hinges on a single question — do I have enough troops right now that a strike, with the traitor’s defense cost halved, will actually break through and take real territory, rather than just bleeding my army? If yes, the attack belongs in the next few seconds, not after the window, because the 0.5 and 0.8 multipliers disappear at second thirty and the strike suddenly costs normal rates. By second ten you should have the attack queued if you decided to strike, because a large attack takes time to travel and resolve and you want it to be landing while the debuff is still live; an attack that is still en route at second twenty-five is an attack that lands at normal cost. By second fifteen the first tiles should be flipping and you confirm the strike is working. By second twenty you are deciding whether to reinforce the strike or hold your remaining army in reserve for the second wave after the window. At second thirty the traitor flag clears, the debuff is gone, and whatever is left of the decision is now a normal attack or a normal defense, not a traitor-window strike. The mental model to carry is that the window is not a time to plan — it is a time to commit an attack you should already have sized, or to deliberately choose not to attack at all. Players who try to think through a whole strategy inside the 30 seconds miss the window, and the window is the only part of the betrayal that is on your side.
The core decision: counter-attack, hold and embargo, or re-ally
There are really only three defensible moves in the first thirty seconds, and the guide is about choosing between them, because any fourth move is a blend of one of these or a half-measure that fails at all of them. Move one is the counter-attack: you launch a sized strike on the traitor now, while their defense cost is halved and attacks land 20% faster, aiming to either eliminate them or take enough territory that the betrayal stops buying them anything. This move is the right one when your troop ratio to the traitor is close enough that the 0.5 loss modifier is the difference between breaking through and stalling, and the alternative to striking is letting the strongest player on the map get a free 30-second window to extend their lead. Move two is hold and embargo: you do not counter, you fortify, and you let the automatic 5-minute embargo on trade between you do its work — their economy is now cut off from you for five minutes, so they are bleeding the value of that alliance while they have no trade to make up for it, and you use those five minutes to rebuild your army. Move three is re-ally: if the betrayal was a single bad move by an otherwise useful ally (a misclick, a panic break to escape a losing position), you may let the 30 seconds pass, the embargo run, and then re-offer the alliance once the immediate hostility has cooled.
The choice between the three is driven by one variable more than any other: your troop ratio to the traitor right now, and the distance between you and the traitor. If you can break through with the 0.5 loss modifier and the traitor is close enough to reach in the window, move one is almost always right, because the traitor-window is the cheapest you will ever get to crack a strong defender and the alternative is that you just let the strongest enemy on the map become weaker for free. If you cannot break through — you are outgunned or you just spent your army elsewhere, or the traitor is far away and you physically cannot reach them in 30 seconds — move two is right, because a half-strike you cannot finish is worse than no strike, and the embargo lets you recover while they are frozen and paying for the break in real time. Move three is right only when the ally is still strategically worth keeping and the betrayal did not cost you enough to make them a net liability; in a tight FFA or in team mode, re-allying the person who just broke you is usually the wrong call, because the 70% land-share win threshold in team modes means a teammate who breaks you can threaten your team’s win even without eliminating you. For the broader diplomatic calculus of when an alliance is even worth holding in the first place, the diplomacy and betrayal strategy page covers the offensive side of the same question, and the recovery playbook covers what to do after you have already lost the position. The decision is never “is retaliation good in general” — it is “can I finish this in thirty seconds, and if not, do I freeze them or forgive them.”
What to do in the 30 seconds and what to do after
Concretely, the 30 seconds split into two cases, and the sequence you run is different in each, so it is worth memorizing both so you are not improvising against the clock. In the counter case your sequence is: confirm the traitor icon (seconds 0-2), decide and size the strike against the traitor’s actual troop count (seconds 2-5), queue the attack so it lands within the window (seconds 5-15), watch it flip territory (seconds 15-30), and then commit the rest of your army if the first wave is working. The sizing rule that decides this case is simple and it is the most important one in the whole guide: you want an attack large enough that, with the traitor’s troop cost halved, the defender cannot survive the first contact. A small nibble that the traitor shrugs off just burns your troops for the -100 relation you are already paying, and it does not open the territory. The strike has to actually open something, and if you are not sure it will open, the answer is that you are in the other case, not a smaller version of this one.
In the hold-and-embargo case your sequence is different and, counterintuitively, the more common right answer, because most betrayals happen against a player who is already outgunned or who has just spent their army elsewhere. You stop, you pull any in-flight attack that is not going to land within the window, you harden the border the traitor is on, and you let the 5-minute embargo run. While the embargo is live, the traitor cannot trade gold or troops with you, so their income from that alliance is gone and they are paying for the break in real time. You use those five minutes to top up your army, move troops from the safe side of your map to the contested border, and build a port or a defense post on the traitor’s edge so that when the embargo expires you are the one who is ready to push, not the traitor who is trying to capitalize on the -100 relation. At minute five the embargo expires on its own, and the question of the counter or the embargo is replaced by the question of the normal game. The most common failure in the 30-second window is the half-attack: the player panics, sends 30% of their army “to show something,” watches it stall against a traitor who still has 70% more troops, and now has a weakened army, a -100 relation, and no territory. The window rewards decisiveness and punishes half-measures, and the discipline to hold when you cannot break through is the same discipline as the discipline to strike when you can. If you are going to strike, strike to break through. If you are not going to break through, do not strike at all.
The 5-minute embargo and the trade freeze
A betrayal does not just set the 30-second debuff; it also sets a 5-minute temporary embargo on trade between the two players, which is where the real economic damage lives and which most players ignore because the traitor icon grabs all the attention. The embargo means that for five minutes (or until you become allies again, whichever is first) the traitor cannot trade with you. In v0.34 trade is how allies share gold and top up each other’s armies, so an embargo on the traitor means the alliance’s core benefit — mutual resource support — is cut for five minutes, and the traitor has to make up that income from their own economy alone. This matters in two directions, and the direction that matters to you depends on which of the two of you was leaning on the other. If you are the stronger of the two, the embargo hurts the traitor more, because they were the one relying on your larger economy to stay viable, and five minutes of no gold coming in from you is a real hit they have to absorb with their own income while they are also fielding a 30-second debuff and a -100 relation. If you are the weaker of the two, the embargo hurts you more, because you were the one leaning on the traitor’s economy, and you have to make up five minutes of missing income from your own, thinner economy, which is why the “hold and embargo” move is the more dangerous of the three when you are the smaller player and why the counter-attack is the one you should reach for if you have the ratio.
Either way, the embargo is a fixed 5-minute cost the traitor just incurred by breaking, and it stacks on top of the 30-second debuff and the -100 relation, so the total price of the betrayal is the debuff plus the freeze plus the relation floor, not any one of them. That is why the “hold and embargo” move is so powerful in the counterintuitive case where you cannot counter: you do not have to win a fight to make the betrayal expensive. You just have to survive the 30 seconds and let the 5-minute trade freeze do the punishing, and the freeze does its work whether the traitor is strong or weak, close or far. The embargo also interacts directly with the re-ally move: if you re-offer and the traitor accepts, the embargo clears immediately because you are allies again, so re-allying cancels the trade penalty on both sides. That is a real cost of the re-ally option — you are not just forgiving the betrayal, you are also giving back the 5-minute economic punishment the break earned, and you are re-opening the gold and troop flow that the traitor is now dependent on. Before you re-ally you should be clear that the traitor’s value to you outweighs both the forgiveness and the cleared embargo, because once you accept the alliance the freeze is gone and the traitor has a full five minutes of trade to recover the ground they lost in the window, and you have just handed them the recovery you should have been forcing.
Relation drops, the neighbor ripple, and the AI targeting
The betrayal also drops the traitor’s relation with everyone around them, and the ripple beyond the two of you is where the strategic consequences compound, because the -100 to you is not the only relation that moves. The traitor’s relation to you drops by 100 — the full hostile range — so you are now at the same relation level as an open enemy, and the traitor’s relation to each of their adjacent neighbors drops by 40. That -40 is the part most players miss. A neighbor the traitor was friendly with (say at relation 60) is now at 20, which is no longer friendly; a neighbor they were at relation 40 with is now at 0, which is the neutral floor and the start of the hostile range. The traitor has effectively made new enemies or weakened relationships with every bordering player just by breaking one alliance, and those neighbors can see the relation line move in real time, which is a diplomatic signal that outlasts the 30-second debuff by a long way. This has two practical consequences for you, and both of them work in your favor even if you are not the strongest player on the board.
First, the traitor is now a less safe target for their other enemies in a different way than the -100 suggests: if the traitor was already under pressure from a third player, the -40 to that third player’s neighbor relations does not directly help you, but the traitor’s overall diplomatic position is worse and more players on the map now have a reason to pressure them, which means the traitor has to split their army to cover more borders and is less able to concentrate against you. Second, and more directly useful to you, the -100 to you means that any player who can see the relation map now knows you and the traitor are at full hostility, which both discourages anyone from trying to broker a truce you do not want and makes the traitor a legitimate target for you in front of the whole map — you are not the aggressor, the traitor broke first and the relation floor proves it, so you do not carry the diplomatic stigma of the first strike. There is also a mechanical AI component worth knowing: while a player’s isTraitor flag is true, the game’s AI targeting weights that player higher as an objective, so NPCs and AI-driven behaviors are more likely to focus the traitor during the window. In practice this mostly shows up in FFA games with AI opponents or in the auto-targeting of NPC behaviors, but it reinforces the same point the 0.5 and 0.8 multipliers make — the 30-second window is the one moment where every system in the game is slightly biased toward the traitor being the one who gets hit, and that bias is available to you as the betrayed player, and it is one more reason the “do nothing and defend” default is the worst of the three moves.
Mode and map adjustments: FFA, team, and coastal maps
The 30-second traitor window is the same in every mode and on every map — the 0.5 loss modifier, the 0.8 tick modifier, the 30 seconds, the 5-minute embargo, and the -100/-40 relation drops do not change with mode or map. What changes is how reachable the traitor is and whether a counter-attack is even possible, because those depend entirely on the board and on the win condition of the mode you are in, and they are the first thing to check before you commit to the window. In a large Free-for-All with dozens of players, the traitor is usually far enough away that a 30-second counter is rarely reachable by land, and the hold-and-embargo move is the default right answer: you cannot physically get to them in the window, so you freeze them and recover, and you only counter if you happen to be bordering them or have a boat route that lands inside the window. The large-FFA default is patience plus the embargo, and the counter is the exception that you reserve for the rare case where the traitor is adjacent and outgunned.
In a small FFA with four to eight players, the traitor is almost always adjacent, so the 30-second counter is genuinely reachable and the decision is sharper — you almost always have to pick between striking now and embargoing, because the window is short relative to the map and the traitor is right there, and holding without striking means you are simply waiting for them to use the 30 seconds you did not. In team modes, a teammate betraying you is the most expensive betrayal in the game, because the betrayal also breaks your team’s shared economy and the 70% land-share threshold that decides team wins means a teammate who breaks you can directly threaten the team’s win condition even if they do not eliminate you. In a two-person team the betrayal is essentially a solo FFA between you and the traitor for the rest of the game, and the 30-second window plus the 5-minute embargo become the main tools you have to stay competitive, and the counter-attack is the one you reach for more often than in any other mode because the traitor is the only other member of your team and the distance is always short. Coastal and island maps change the reachability question again: if the traitor is separated by water, a boat attack may be the only way to counter within the 30 seconds, and the 0.8 speed modifier makes that boat attack land 20% faster than normal, which can be the difference between landing inside the window and missing it entirely. The map’s geography, the mode’s win condition, and the traitor’s distance from you decide which of the three moves — counter, hold-and-embargo, re-ally — is even available to you, so always check the board, the mode, and the water before you commit to the window.
Failure modes and how to recover from a botched counter
The two failure modes that turn a survivable betrayal into a losing position are the half-attack and the over-extension, and they are the two mistakes that players make more often than the traitor actually punishes them, because both are self-inflicted and both are recoverable if you catch them fast enough. The half-attack is sending a strike too small to break through, which costs you troops, the -100 relation, and the 30-second window while giving the traitor territory or a time buy, and it is the failure that most often ends the game because it converts the 30-second window — the one moment that was on your side — into a moment where the traitor extends their lead. The over-extension is sending a strike so large that you commit most of your army to the traitor, and when they survive the first contact (because they had more troops than you estimated or they had a defense post you did not see), you are now out of army and exposed to the rest of the map, with a -100 relation and no reserve to fall back to. Both failures share the same root cause: sizing the counter-attack from the emotion of the betrayal rather than from the traitor’s actual troop count and their visible defenses.
The recovery from either failure is the same, and it is available as long as you survive the first contact, so catching the failure early is the whole game. Stop the attack. Do not throw more troops at a traitor who is clearly outgunning you; throwing a second wave into a losing first wave is how a half-attack becomes a total loss. Pull your remaining army back to your strongest border and hold. The 5-minute embargo is still running whether you attacked or not, so the trade freeze is doing its work while you recover, and you should be using those five minutes to rebuild your army and reposition rather than to chase the traitor. Rebuild your army over the next few minutes, move your port and your key defenses, and wait for the traitor to either come to you or to run out of the momentum of the betrayal. A player who breaks an alliance and then cannot finish you is usually the one who loses the next ten minutes, because the -100 relation and the -40 neighbor drops have made them the soft target on the map and their army is spread across the attack they launched. Your recovery is patience plus the embargo: let them over-extend, let the trade freeze starve their economy, and let the map’s other players do the pressuring. The one non-recoverable failure is the half-attack in a small FFA where the traitor was adjacent and you committed only half your army — that one tends to end the game, because the traitor converts the 30-second debuff into a real territorial gain and you are now the one who is behind with no window left to recover, and the only move left is the long game of outlasting them while they spend their army on the gain they took.
Quick reference: the betrayal numbers in one table
The table below is the cheat sheet for the whole guide, and it is the thing to have in your head when the betrayal lands, because the 30-second window does not leave time to recall a paragraph. Every number in it is verified against the v0.34.24 tag source and the in-game tooltip, and every row maps to one of the three moves — counter, hold-and-embargo, or re-ally — so reading the table against your own troop ratio and your distance to the traitor tells you which move is available to you.
| Situation | Number | Effect on you as the betrayed player |
|---|---|---|
| Traitor duration | 30 seconds | The betrayer is the marked, weakened one; you are not |
| Traitor defense loss modifier | 0.5 | Attacks you send at the traitor trade about half the defending troops |
| Traitor tick (speed) modifier | 0.8 | Your attack on the traitor lands about 20% faster per tile |
| Embargo on trade | 5 minutes | The traitor cannot trade gold or troops with you for 5 minutes |
| Default alliance duration | 5 minutes | A normal alliance lasts 5 minutes before it must be renewed |
| Relation to ex-ally | -100 | You and the traitor are now at full hostility |
| Relation to each neighbor | -40 | The traitor’s other bordering relations drop by 40 |
| Team land-share threshold | 70% | In team modes a teammate’s betrayal can threaten the team’s win |
| Alert Frame | in-game setting | Pops when you are betrayed or attacked over land |
The table tells you three things in one glance, and those three things are the whole decision. The 30-second row tells you the window is short and belongs to the person who just broke you, not to you as the one being punished. The 0.5 and 0.8 rows tell you that striking back is the cheaper and faster move during the window, and that is the reason the counter-attack is the first move to reach for when you have the ratio and the distance. The 5-minute embargo row tells you that even if you do not counter, the betrayal still costs the traitor five minutes of trade, which is the reason the hold-and-embargo move is the correct default when you cannot reach the traitor in the window or you are outgunned. The -100 and -40 rows tell you that the traitor has made new enemies and is the soft target on the map, which is the reason the long game favors you after a botched counter. The 70% row tells you that in team modes the betrayal is more expensive than in FFA, and the Alert Frame row tells you there is a setting that warns you the moment the betrayal happens so you do not waste the first two seconds confirming what the HUD already told you. Read the table against the board, pick the move, and commit or embargo before the window closes — that is the guide in one line.
Related content
Use OpenFront v34.3 costs, troop growth, route payback, and stop signals to choose City, Port, Factory, defense, or a liquid reserve without copying a fixed script.
- OpenFront AFK Teammate Takeover: Absorb a Disconnected Ally for Zero Troop Loss
A Team-mode decision guide for what a teammate's disconnect does to your win/loss position, when absorbing their land is free, when it is a trap, and what the 30-second mark and the ranked 2v2 rules actually change.
Sep 23, 2026
- How Nations Aim Their Nukes: Smarter Targeting, No Wasted Blasts
A strategy guide for the upcoming AI Nation nuke targeting change: Nations now compute how much of a blast hits enemy land before firing (atom 25%, hydrogen 40% minimums), they skip a spot where another player's nuke is already landing, and they never nuke a target that would hit friendly land. What changes in your decision, the coverage gate, the anti-double-nuke rule, the failure mode and the mode/map adjustments.
Oct 8, 2026
- Alliance-Break Timing: When 30 Seconds Is Worth the Trade
Decide whether to break a live alliance now, wait for it to expire, or renew it, using the 30-second traitor window, the 0.5 defense and 0.8 speed debuffs, and the -100/-40 relation drops in OpenFront v0.34.
Sep 30, 2026