GUIDES
Nuke Warning Circles: Reading the Amber vs. Red Blast Radius
OpenFront nuke warning circles: what white, amber, and red blast-radius circles mean, when each appears, and how to read them before committing a strike.
Short answer: The blast-radius circle under your nuke ghost is your pre-flight alliance check. White means the strike will not break any alliance. Amber (yellow) means it will end an alliance, but only with an ally who is already a traitor or already disconnected — so it severs a broken bond and does not mark you a traitor. Solid red means the strike would make you a traitor by breaking an alliance with a current, connected, loyal ally. Only Atom and Hydrogen bombs draw this circle; MIRV does not.
You have probably felt the circle change color under your cursor and then ignored it, or worse, trusted a white circle that turned red two tiles to the left. Since v0.36.0 that warning has real meaning, and since v0.36.2 the red state no longer flashes, so what you see is what you get. This guide explains the three colors, the exact rule that decides each one, and how to read the circle fast enough to use it in a live match instead of after the fact. If you already understand when a nuke breaks an alliance but not what the circle is trying to protect you from, that is exactly the gap this closes, and the nuke alliance threshold guide covers the numbers side while this one covers the visual side.
What the nuke warning circle actually tells you
The circle appears the moment you pick up an Atom or Hydrogen bomb and aim it, and it redraws on every tile you hover. It is not a damage forecast and it is not a SAM-defence estimate. It is a single question answered for you: if I drop this bomb exactly here, do I break an alliance, and if so, at what cost to my own standing? The answer comes in three colors, and each one maps to a different decision you are about to make, so the value of the feature is not that it tells you something new but that it tells you the one thing you could not see, fast enough to change your finger.
The white circle is the “safe re: alliances” state. It means no allied player has enough territory or any structures inside this blast to cross the break threshold. If you are mid-alliance and the circle is white, dropping the bomb here will not sever your alliance and will not cost you honor. That is a genuinely useful signal, because the default assumption for a nuke over contested ground is that it is dangerous, and the white circle is the one case where you are allowed to assume the alliance is untouched. Before the readable warnings existed you made that call by eyeballing the blast against the map and hoping, and the cost of a wrong guess was a traitor mark you did not intend, one that every other player then spent the rest of the match trying to exploit. The circle collapses that hope into a verdict, which is the real reason to learn it: it removes the one variable you cannot see from inside the game, the exact alliance consequence of the exact tile you are about to fire on, and hands you a color you can read in a frame.
The amber and red circles are the two warning states, and the difference between them is the entire reason the feature exists. Both mean an alliance ends. The only question is whether ending it makes you a traitor. If the answer is no, the circle is amber; if the answer is yes, it is red. Getting that distinction right before you commit is the difference between a clean exit from a dead alliance and an open act of betrayal that every other player in the match now has to factor in, so a single misread can cost you the trust of the whole room, not just one partnership.
The three colors, decoded
Here is the full mapping, because the exact colors matter for a fast read. White is a neutral, no-warning state and corresponds to the game’s internal “none” result. Amber is the alliance-break-without-traitor state, rendered as a warm yellow (the client’s alliance color, a saturated amber at full red with a strong green channel). Red is the traitor state, rendered as a hot red (the client’s traitor color, strong red with green and blue knocked way down). Two players who have already nuked each other show the same red they would show for a fresh betrayal, because the underlying “this is a hostile break” signal is the same, and the client does not distinguish a fresh betrayal from a continuing one when it picks the warning color. The same rule applies if you and a rival have been fighting and the alliance between you was never formal in the first place: the color encodes the consequence to your own standing, not the history between the two of you, so a red circle is a statement about what will happen to you if you fire, and not about how the other player “deserves” it.
Practically, the read is a one-second glance. White, go — the alliance is untouched. Amber, proceed with your eyes open — you are about to cut an alliance that is already effectively dead, and you are not taking the traitor penalty. Red, stop and decide — you are about to become the person who nuked a standing ally, and the match will treat you accordingly. You do not need to know the exact territory count to use this; you need to know which of the three you are looking at and what each one costs, and that is a habit you can build in a single practice lobby because the feedback is immediate and unambiguous.
| Circle color | Internal state | What the strike will do | Your standing after |
|---|---|---|---|
| White | none | No alliance break; no allied structure or enough allied territory in the blast | Unchanged |
| Amber | breaksAlliance | Breaks an alliance only with an ally already marked a traitor or already disconnected | Unchanged (no new traitor mark) |
| Solid red | traitor | Breaks an alliance with a current, connected, loyal ally | Marked a traitor |
A common misread is to treat amber as “safe” the way white is. It is not safe in the sense that nothing changes; an amber circle still ends an alliance, still drops your shared-economy income from that partner, and still tells every spectator and every opponent exactly which bond you are dissolving, which is why the color was chosen to look like a caution and not a clearance. Amber is only safe relative to red: it is the cheaper of the two breaks, the one that does not brand you, and the circle is giving you that ranking. The only mistake is to read it as a binary pass/fail instead of a three-level severity, and the moment you start reading it as three levels instead of one, the feature stops being decoration and becomes your pre-flight checklist.
Why the circle only shows for Atom and Hydrogen bombs
The warning circle is deliberately limited to the Atom and Hydrogen bombs. If you pick up a MIRV and aim it, you will see the flight trajectory and the impact marker, but you will not get the color-coded alliance warning on the ground. That is a real gap in the pre-flight picture, and it matters most exactly when you least expect it, which is in the endgame, when the MIRV is your main pressure tool and the alliances around you are the most fragile and the most worth protecting at the same time.
The reason is mechanical. The alliance-break check runs against a fixed blast magnitude, and the client only wires that check into the Atom and Hydrogen bomb previews. The MIRV’s warhead footprint is computed differently, and the range-warning pass simply does not receive a value for it, so the circle falls back to “none” and draws nothing. In code terms the check returns no warning for any unit that is not one of those two types, and a MIRV warhead is not one of them, so the absence of a circle on a MIRV is a hard-coded “not evaluated” and not a “evaluated as safe.”
The practical consequence is that “no circle” is not the same as “safe circle.” When you plan a MIRV strike you are flying blind on the alliance question, so you have to do the reasoning the circle would otherwise do for you: look at whether any allied structures or a large block of allied territory sit in your intended impact zone, and assume the break is at least as likely as it would be for a comparable Atom. The moment you rely on a white circle as your alliance check, remember that that check exists only for the two single-warhead bombs, and treat a missing circle on the MIRV as a missing check, not a passing one.
There is also a scale reason. The Hydrogen bomb is the biggest nuke in the game by an order of magnitude, and it is precisely the one where an accidental alliance break would be most catastrophic, so it is the one that most needs the warning. The Atom is the everyday nuke and the one you will most often be tempted to use mid-alliance, because it is cheap enough to drop and the temptation is right there under your cursor. Both are covered. The MIRV, which you reach for in endgame pressure, is the tool where the developers accepted that you carry the responsibility yourself, and the honest read of that is that the feature is built for the bombs you use most often in alliance play, not for the one you use to close a match.
Amber vs. red: the traitor-mark rule
The whole feature hinges on one rule, and it is worth stating plainly: nuking any ally breaks your alliance with them, but only betraying a connected, non-traitor ally marks you a traitor. Those two sentences are doing different work, and the circle is the visual split between them. The first sentence is the mechanical fact, and it is absolute, so a nuke over an ally is always an alliance event. The second sentence is the honor rule, and it is conditional, so the same mechanical event can be either a clean break or a betrayal depending on the state of the specific ally. The circle exists to show you which of the two you are about to trigger, because from inside the game the two look identical, a nuke over a partner’s land, and only the internal state of that partner decides the cost.
Internally, the game splits your allies into two buckets before it draws the circle. The first bucket is allies who are already flagged as traitors or who have already disconnected from the match; those are “no new mark” allies, and the alliance they still have with you is, in the game’s bookkeeping, already broken. The second bucket is everyone else, the current, connected, loyal allies, whose bonds are intact and whose betrayal you would be the one to commit. The circle then asks the break question twice, once per bucket, and the color is decided by which bucket the break would fall into.
If the strike would break an alliance with someone in the loyal bucket, the circle is red, because breaking that specific bond is what the game treats as a betrayal and what triggers the traitor mark on you. If the strike would not touch a loyal ally but would break an alliance with someone in the no-mark bucket, an ally already marked a traitor or one who has disconnected, the circle is amber, because ending that bond is still an alliance break but it does not attach a new traitor mark to you. If neither bucket’s break threshold is crossed, the circle is white.
This is why amber can look surprising. You may have believed that any nuke over an ally is a betrayal, and then see amber and wonder why the game is treating you so lightly. The answer is that the bond was already broken in the game’s eyes: the other player is already a traitor, or they are gone, and the amber is the game telling you the specific cost you would pay is severing a bond that is already severed, not taking the traitor penalty for the first time. If you are curious about the full etiquette of turning on a partner once the bond is dead, the reacting to ally betrayal guide walks through the social side, because a red and an amber break can land on the same target with very different reactions from the room.
The 100-tile break test and the structure override
The circle does not decide red or amber on a guess; it runs a concrete numeric test. For the ally set in question it asks two questions, and either one being enough flips the break. The first is whether this bomb would destroy any of that ally’s structures inside the blast. The second is whether that ally’s weighted territory inside the blast exceeds a threshold of one hundred. The test is run separately for the loyal allies and for the no-mark allies, and the structure override is absolute.
The structure override is the more important of the two for most players, because it is binary and non-negotiable: destroying a single allied structure anywhere in the blast breaks the alliance with that ally, regardless of tile count. A command center, a SAM site, a factory, one structure in the ring does it. This is why a nuke that looks like it is clearing open water or neutral ground can still flip to amber or red the moment an allied building sits at the edge of the impact zone, and it is also why the circle can read a warning even when the territory count looks far below the line, because the structure check runs first and returns true on its own.
The weighted territory count is the part players most often get wrong. Every tile of an ally’s land inside the bomb’s inner radius counts as a full unit, while every tile in the outer ring of the blast counts as half a unit. So the one hundred is not a raw tile count; it is a weighted one, and a wide blast with a thin outer rim can quietly add up past the line even when the core looks small. The inner radius is where the damage is real and the tiles count at full weight, and the outer ring is the fall-off where tiles only count at half.
The magnitude the test uses depends on the bomb. The Atom’s footprint is a moderate inner circle with a wider outer ring, the Hydrogen bomb’s is enormous by comparison, and the threshold is a fixed one hundred for all of them. Because the threshold is fixed while the blast size varies, a Hydrogen bomb over the same position that an Atom might pass as white will almost always cross the line for a loyal ally. The circle is the only thing that reconciles those two facts fast enough to matter in a match, and it is also the thing that makes the nuke alliance threshold guide concrete, because that guide explains what the one hundred means and this one explains the color it produces.
Flashing red is gone: the v0.36.2 fix
There is a version-boundary detail that changes what the red circle looks like, and it is easy to miss if you learned the warning in the middle of the v0.36 cycle. When the readable nuke warnings landed in v0.36.0, the traitor state did not draw a steady red circle; it flashed red and white. The intent was to make the danger unmistakable, to make it the one warning you would never scroll past without registering, but the flash produced a real and documented failure mode: players read the white phase of the flash as the “no warning” state and dropped a bomb they thought was safe, and the game had no way to tell them they had misread a strobe for a verdict.
The official release note for the feature in v0.36.0 describes the design as a yellow circle when a strike only ends an alliance with a traitor or disconnected ally, and a red one when it would make you a traitor, and the flashing was the way that red was rendered at first. Then in v0.36.2 the client stopped the flash and made the circle solid red, with the stated reason that the flashing “was easy to mistake for white.” The change is one line in the render settings, the removal of the flash frequency, but it is a decisive one for the feature’s job, because a pre-flight check that you can misread a single frame of is not doing its job at all.
So the correct mental model for v0.36.2 and later is that a red warning is a continuous, solid red circle. If you see red and it is not flickering, that is the steady state, not a glitch, and you should read it with the same confidence you would read a white circle, because the game is now holding its color steady exactly so you can. If you are reading an older recording or a walkthrough made before the fix and the red circle pulses, the same logic still applies: treat any red, flashing or solid, as the traitor state, because the meaning never changed, only the way it was drawn.
If you have ever hesitated over a pulsing red circle and lost the window, this is the version where that hesitation is no longer rewarded by a clearer signal, and the version where the game finally matches the job the feature was built to do. The circle now holds its color so you can read it and then still read it a second later when your finger is on the fire control, which is the entire difference between a warning you can act on and a warning you can only argue about afterward.
Reading a circle mid-game: five scenarios
Let’s ground the three colors in situations you will actually face, because the abstraction only pays off under a timer. Each scenario below is a concrete, plausible position, and the point is to build a feel for which color means which decision before the moment actually arrives, so the habit is in place when it matters.
Scenario A — the standing ally. Two-team match, you and your partner are both connected and loyal. Their capital, with a command center and a SAM site, sits inside your Atom’s inner radius, so the structure check alone would already break the bond. The circle is solid red. Nuking here ends a live, loyal alliance and marks you a traitor, and it is also the one case where the circle is telling you to put the bomb down, or to accept that the match has just become an open rivalry that the rest of the room will watch closely.
Scenario B — the ally already marked a traitor. Same two-team match, but your partner nuked your base early and is already carrying the traitor flag while still connected, so the alliance they still have with you is broken in the game’s bookkeeping. Their now-hostile territory sits in your blast, and the circle reads amber, not red. You are ending the bond, but the game already knows the bond is broken, so you do not take the traitor mark, and this is the cleanest way to turn on someone who has already turned on you without stacking a second betrayal on top of the first.
Scenario C — the disconnected ally. Your partner has left or AFK’d and the game has flagged them as disconnected, so their territory moves into the no-mark bucket. Their large block of territory overlaps your intended strike, and the circle reads amber. You are still severing an alliance and still losing any shared economy from that player, but because they are disconnected the break does not brand you, and amber here is the “they are gone, finish the job” signal.
Scenario D — the aim shift. You line up an Atom over neutral ground that clips roughly ninety of your loyal ally’s inner tiles and no structures, so the circle holds white because ninety is under the hundred threshold and nothing structural is in the ring. You nudge the target two tiles over so a single allied factory enters the blast, and the circle flips to red because the structure override is absolute. That two-tile nudge is the whole value of the feature: it turns a static “is this safe” question into a live “where exactly is the safe line” readout, and it is the moment the warning earns its keep.
Scenario E — the Hydrogen scale. You reach for a Hydrogen bomb, whose blast is an order of magnitude wider than the Atom’s, so almost any loyal ally with real territory nearby crosses the hundred-tile line instantly and the default near allies is red. You either strike far from allies, or you wait until the alliance is already broken and the same strike would only read amber. The circle is what makes you plan that timing rather than discover it after the fact, and it is the reason the biggest bomb in the game is also the one where the warning matters most.
When the circle misleads you: failure modes and counterplays
The warning is a strong pre-flight aid, but it has edges, and knowing them keeps you from over-trusting the one thing that looks authoritative, because the circle is the last thing you check and the thing you are most likely to take on faith. Every edge below is a real way the color can send you the wrong message, and every one of them has a one-line counterplay.
First, the circle is a moving target. It reflects the blast of the ghost unit at the tile you are currently hovering, and it recomputes the instant you step the ghost one tile. A white circle at one position is a promise about that position only, and the reliable habit is to check the circle at the exact tile you intend to fire on, not at a nearby one, and to re-check if you drift while lining up, because a drift of two tiles is exactly the amount that can flip a white to a red through a single allied structure.
Second, the disconnected-ally case can look deceptively calm. Once an ally disconnects, their entire territory moves into the no-mark bucket, so even a huge allied zone that would be red while they are present can read amber after they leave. That amber is not “nothing happens”; it is “you are severing an alliance and losing shared economy without the traitor penalty,” and reading amber as a cost rather than as a green light is the whole trick of using the circle correctly in team play.
Third, the weighted count is not a tile count. Outer-ring tiles only count at half weight, so a broad, shallow blast can cross the hundred threshold even when the dense core looks small, and the opposite is also true. When the circle is near a boundary, trust the color over your visual estimate of how much territory is inside, because your eye is a poor estimator of weighted counts and the color is a precise one.
Fourth, the MIRV gives you no circle at all, and no circle is not the same as a white circle. For a MIRV you carry the alliance reasoning yourself, so treat “no warning drawn” as “no warning given,” not “no risk,” and run the same structure-and-tile check in your head that the Atom preview runs for you.
Fifth, the circle is a pre-flight aid, not a prediction. It does not model the thirty-second window in which your ally can react, and it does not tell you how an opponent will interpret the break. It answers the one question it is built for, will this break an alliance and will that break brand me, and hands the rest of the decision back to you, so the circle is a checkpoint, not a verdict on whether you should fire at all.
The counterplay to every one of these is the same discipline: read the circle at the exact firing tile, treat amber as a cost and red as a commitment, and never let the absence of a circle on a MIRV substitute for the reasoning the Atom and Hydrogen previews give you for free.
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