GUIDES
OpenFront Replay Takeover: Continue a Finished Game and Test the Decision You Second-Guessed
Pause any OpenFront v0.36+ replay, pick a surviving player and a bot difficulty, and carry the match on as a singleplayer game to test one alternative decision before your next live match.
Direct answer: take over a surviving player and play the moment forward as singleplayer
In the default v0.36+ replay viewer, pause the match at the tick you want to test, press Continue game from here, pick one player who is still alive at that moment, choose how hard the other humans should be, and the game opens as a fresh singleplayer match seeded from the exact state at that tick. You play as the player you picked; every other real human in the original game is replaced by an AI opponent at the difficulty you selected, and you drive the rest of the match yourself to find out whether a different call would have worked. The original recorded result is untouched — you are not rewriting the multiplayer game, you are running a controlled experiment on the one decision you are unsure about, with the real opening that already happened in front of you.
The whole point is speed. Reviewing a replay tells you where a belief broke, but until now the only way to actually play the alternative was to start a brand-new game and try to recreate the same opening by hand, which is rarely possible in a fifty-player lobby and leaves the very part you want to test — the mid- or late-game position — uncontrolled. The takeover hands you the exact board you had, freezes your chosen player at the point of doubt, and lets you spend five minutes playing out the branch you are unsure about before you commit to it in your next live match. That turns a vague feeling of “I should have done X” into a concrete answer you can act on, and it does so without touching the original game, without waiting for a new lobby to line up, and without spending a full match just to reach the position again.
Use it the way you would use any experiment: bring one narrow question, one variable you want to change, and one way to tell whether the branch was better. Do not open a takeover to re-litigate the whole match. The tool is built for a single, bounded “what if” — the alliance you accepted at tick 400, the second front you opened at tick 900, the nuke you held back at tick 1500 — and it is most valuable when the answer changes what you will do next time. If you have no next match to apply the answer to, or if the question is really “why did I lose overall” rather than “was this one call right,” a plain replay review is the cheaper, more honest tool. The takeover is for the specific moment you still think about at the end of the night.
How to reach the takeover and what the control actually does
The takeover lives inside the replay viewer, which is now the default for every replay in v0.36 and later. You get there the same way you reach any replay: from a public profile’s Games history, from a shared game link, or from your own finished-match card, then open the replay. Once the viewer is playing, scrub the timeline to the tick where the decision you want to test was actually made — not where its consequences became obvious, but where the alternative was still on the table. Stop playback there. The bottom control bar of the viewer carries a Continue game from here action, marked with the controller/play icon, sitting alongside the seek, speed, and playback controls. Press it and the viewer opens the takeover modal.
The modal is deliberately small because it is asking exactly two things. First, select a player: it lists every takeover candidate at the paused tick with their name and a search box that appears when the lobby has more than five players, so in a 100-player record you can type a name instead of scrolling. Second, choose the bot difficulty for the other humans, with four options — Easy, Medium, Hard, and Impossible — and Medium selected by default. There is a Cancel button that returns you to the paused viewer with nothing changed, and a Continue button that stays disabled until you have picked a player, so you cannot accidentally launch with no one in control. When you confirm, the viewer leaves and a normal singleplayer game opens as if you had just joined a Solo match.
What happens under the hood is what makes the feature safe to trust. The viewer does not keep driving the old multiplayer connection or try to resume it. Instead it builds a snapshot of the recorded game state at your paused tick, with you bound to the player you selected and the difficulty you chose, and it starts that snapshot as a brand-new singleplayer match. That is why the game feels exactly like a real game the second it loads — you have a working economy, live borders, active structures, and opponents who are real AI players rather than frozen spectators. It is also why the original multiplayer game is never altered: the recorded match you opened is only ever read, and the new match is a separate singleplayer record. If you later want to watch the original result again, you still can; the takeover did not delete or edit it.
A few practical notes. The takeover works from any point you can scrub to, so you can test an early commitment or a deep endgame decision. Because the new match is singleplayer, the usual singleplayer rules and end conditions apply to the branch you are playing — victory is measured against that match, not against the original. And because the viewer you are using is the default one, make sure you are in it and not the classic viewer: the classic replay, which is still available as a toggle in Settings, has the watching controls but not the Continue game from here action. If your client is older than v0.36, the control will simply not be present, and the feature is not back-compatible with the classic shell.
Takeover versus “Continue to watch”: the two continue buttons are different things
The single most confusing thing about the new viewer is that there are two things people call “continue,” and they do completely different jobs. The one inside a live or recorded game that says you can keep watching the match is a spectator continuation: it keeps you in the viewing role, observing the recorded or live game proceed, with no control over anyone’s tiles, armies, or structures. The Continue game from here action in the replay viewer is a takeover: it ends the viewing role and starts a new game where you control one player. Confusing the two is the most common way players get the wrong expectation from the feature, so it is worth separating them cleanly before you rely on either.
The spectator continuation answers “let me keep following this match as a watcher.” It is about observation — you watch the game you are already watching go on, and everything that happens is still the game that happened. The takeover answers “let me play this exact board myself and see what a different choice does.” It is about intervention — you stop being a watcher, the game is re-seeded from the paused tick, and the humans who were playing become opponents your AI substitutes for. When a community thread asks whether the game “continues with real players” after you click continue, the answer is: if it is the spectator continuation, yes, it is the same recorded or live players continuing; if it is the takeover, no — the other humans are replaced by bots at your chosen difficulty, and only the player you selected is a real human controller (you, at your keyboard).
This distinction matters for the decision you are actually making, because the two tools serve two different jobs in your improvement loop. You watch a finished match to understand what happened and where your belief broke — that is the seekable replay viewer doing its job, and the spectator continuation keeps you moving through the timeline as an observer. You take over a finished match to test a specific alternative — that is this feature. If you take over when you only needed to watch, you burn real minutes controlling a player whose opening you did not earn and whose late-game situation you did not help create. If you only watch when you needed to test, you leave with the same unanswered feeling you started with, because watching never tells you what you would have done. Match the tool to the question: observe with the viewer, experiment with the takeover.
There is also a subtle ordering point. You can always fall back from a takeover to the original: if the branch you played gives you no useful answer, close the singleplayer match and open the same replay again — the recorded game is unchanged, so you can re-read the moment, scrub to a slightly different tick, or pick a different surviving player. The takeover is a side-quest, not a commitment. Treat it the way you would treat a quick study game in a chess app: it exists to sharpen one line, and the main game — your actual next live match — is where the lesson has to show up. Keep the two roles separate and the feature does exactly what it promises: a cheap, reversible way to play the decision you second-guessed, without ever putting the real multiplayer result at risk.
The surviving-player rule: who you can take over, and why
The candidate list in the takeover modal is not the full lobby. It is filtered to a specific subset, and understanding that subset is what keeps your experiment honest, because it determines which “what if” branches are even open to you. At the paused tick, the viewer lists a player as a takeover candidate only if that player is a real human (not a pre-placed bot) and, once the match is past the opening spawn phase, still alive at that exact moment. A player who has already been eliminated at the tick you paused on does not appear as a choice, because there is no surviving position to hand you — there is no economy, no connected land, no remaining structures to continue from. The rule is not an accident or a limitation you should work around; it is the definition of what “take over” means. You take over a player who still has something to play.
This has a direct consequence for how you choose your tick. If the decision you want to test was made by a player who later dies, you must pause the takeover before that death, at the moment the alternative was still live. You cannot pause at the moment of death and take over the corpse. So the tick you pick is the last point at which the branch you want to explore still existed for that player. In practice that usually means pausing a little earlier than the moment you are thinking about — at the decision, not at its outcome — so the player you take over is the one who was still standing when the call was made. The player panel and the timeline in the viewer let you confirm who is alive at the chosen tick before you commit, so there is no guesswork: if a name is not in the modal’s list, that player is gone at this tick and is not a valid takeover target.
There is also a bot rule to keep straight. Pre-placed or nation bots are never takeover candidates, only human players. That is deliberate: the takeover is about testing a human’s decision by replaying it with human-level judgment applied, not about taking over an AI that was already acting by rule. If the player you were trying to “what if” was itself a bot, there is no human decision to test — the bot’s move is whatever its policy produced, and continuing as that bot would just re-run the policy, not answer a question about your judgment. So when you see a lobby with a mix of humans and bots, the takeover list shows only the humans still standing, and you are always choosing between real opponents’ surviving positions.
The one edge case worth naming is the spawn phase. Very early in the match, before the opening is settled, the filter is relaxed so that players in the spawn phase are listed even if the usual “still alive” test would not yet be meaningful, because the opening is the one window where you legitimately want to re-test a spawn commitment or an early expansion. Once the spawn phase is over, the rule tightens to the surviving-players-only case. The practical takeaway: the deeper into the match you pause, the more the list converges on the players who are still in the fight, and the earlier you pause, the more of the original lobby is still available to choose from. Pick your tick with that in mind — the list of available players is a direct readout of who was still alive when you paused, so if a player you want to test is missing, move the tick earlier and try again.
Difficulty is the test variable, not a setting you guess at
The difficulty picker in the takeover modal is the part of the feature people underuse, and it is worth treating as seriously as the player choice, because it is the dial that decides what your experiment actually measures. The four options — Easy, Medium, Hard, and Impossible — set how competent the AI opponents are that replace the other humans at the difficulty you select. Medium is the default, and it is the right starting point for most tests, because it approximates “players who were playing the game the way they were playing it in the original match.” If you take over a mid-game position against Medium bots, you are asking: “given this board and opponents of roughly the strength that was here, does the branch I am testing hold up?” That is a fair, neutral baseline, and it is the one you should run first for almost any question.
Hard and Impossible exist to stress-test your call, and they answer a different question than Medium does. If you take over at Hard or Impossible, you are asking: “does this branch survive even against opponents noticeably stronger than the ones I was facing?” That is the right test when you are unsure whether your reading was just lucky — for example, if the original match had a few weaker neighbors you could trade with, and you want to know whether the same second-front push would have held against a stronger coalition. It is also the right test before you try the branch in a big or high-stakes lobby, because you are pre-asking whether it is robust rather than just workable. If your call collapses at Impossible, that does not mean it is wrong for a normal game; it means it is fragile, and you should know that fragility before you spend a real match finding out the hard way.
Easy is the opposite extreme, and it has a specific, honest use: sanity-checking that a branch is at least capable of working at all. If a branch does not win even when the opponents are deliberately weak, then something about it is structurally broken — a route that cannot be defended, an investment that never pays, a position with no exit — and no amount of your own play in a real match is going to save it. Easy is not the setting you use to “win” your test; it is the setting you use to find out whether a plan has a hidden fatal flaw before you even consider whether you could pull it off against real opponents. Running the same decision at Easy and at Medium and comparing the two is sometimes more informative than a single Hard run, because the gap between the two outcomes tells you how much of your result is your skill versus the board.
The discipline that keeps this useful is to run the same tick and the same player at more than one difficulty and note where the result flips. A branch that wins at Easy, is a draw at Medium, and loses at Impossible is a different, more useful finding than a branch that wins at all three, even though both “work” at Medium. Record which difficulty changed the outcome, because that is the information you carry into your next live match: not “the branch won” but “the branch holds against Medium opponents and is vulnerable to a Hard coalition,” which is exactly the kind of conditional judgment you need when your next lobby has a strong neighbor you can now recognize. Treat the difficulty as the variable you are holding constant or deliberately changing, never as a throwaway you pick by instinct, and the takeover becomes a small but real instrument for calibrating how your decisions behave against different strengths.
Scenario: the alliance you accepted and the second front you opened
Consider a concrete, numbered situation so the method is something you can actually run rather than a description of one. You played a fifty-player lobby on a mid-size map. You were the fourth-largest nation at the halfway point, allied with a larger neighbor to your north against a common enemy to the east. At roughly tick 700 (mid-game, your economy at about 40% of the leader’s), you accepted an alliance offer from the eastern enemy that promised a non-aggression pact in exchange for you opening a second front against a smaller, unaffiliated player to the south. You opened that second front. By tick 1100 the southern push had stalled, your northern ally had started absorbing the eastern front you had left thin, and you finished the match in the bottom third — a worse result than the alliance you started with would have produced. The question you keep replaying in your head is not “why did I lose” but a much narrower one: “at tick 700, should I have accepted that eastern alliance and opened the southern front at all, or should I have held the northern front and refused?”
That is a clean takeover target, because it is one decision (accept or refuse the eastern alliance at tick 700), one variable (whether you opened the southern second front), and one way to judge it (did holding the northern front and refusing the eastern deal produce a better mid- to late-game position). To run it, open the replay, scrub to tick 700 — the moment the offer arrived and the choice was live, not tick 1100 where the damage showed up — confirm in the player panel that you (your player) are alive and still the fourth-largest nation, and note who else is standing. Press Continue game from here, select your player, and set the bots to Medium, because the original lobby had opponents of roughly normal strength. The match now opens with you at exactly tick 700, the eastern alliance not yet accepted, the southern front not yet opened, and every other human replaced by a Medium AI. From here, you play the branch where you refuse the eastern deal and keep your northern front intact.
You now have a controlled answer rather than a memory. If, in the takeover, holding the northern front and refusing the eastern alliance leaves you larger at tick 1100 than the original result, the lesson is concrete: your acceptance of the eastern deal was the mistake, and the fix for your next match is a rule you can state — “I do not open a second front against an unaffiliated small player to appease a larger enemy while I hold an active front; I hold the front and let the small player absorb the pressure.” If, in the takeover, the refusal does not improve your position and the southern front would have been the better call after all, then the mistake was elsewhere (perhaps the timing of the second front, or the trade price you accepted) and you now know the alliance itself was not the error. Either way you leave with one falsified or confirmed belief and one next-match rule, which is the entire payoff of the experiment.
Run it a second time at Hard if the Medium result was a close draw, because the original lobby had a couple of stronger neighbors you traded with and you want to know whether the held-front branch survives a tougher eastern coalition. If the held-front branch wins at Medium but loses at Hard, your real finding is not “refuse alliances” but “refuse that alliance only when the eastern enemy is not at full strength,” which is a more honest and more useful rule than the broad one. This is what a good takeover produces: not a verdict on the match, but a calibrated, conditional answer about the one decision you were unsure about, ready to be applied the next time the same shape of choice appears in a live lobby.
Scenario: the nuke you held back at the last warning
A second scenario with different numbers and a different kind of decision, because not every “what if” is an alliance or a front — some are timing calls on a single structure. You were playing a Cold War lobby, and you held the only MIRV on the map for most of the match, repeatedly choosing not to fire it. At the Doomsday-clock warning near the end (territory share below the 40% line, the 30-second warn ticking down), you finally launched your MIRV at the leading nation’s capital. The strike landed, but by then the clock had already decided the game: you won the city and lost the match, finishing second. The nagging question is not whether the MIRV was powerful enough, but a timing one: “at the tick where I first held the MIRV above the launch threshold, was firing earlier — say three warnings before the clock forced the issue — actually the better call, or did holding it for the maximum damage work out and I just misread the endgame?”
This is a takeover target too, and it is a good test case because the decision is a single launch timing with a clear measurable. Scrub the replay to the tick where your MIRV first crossed the launch threshold and you could have fired but chose to hold. Confirm you are alive and holding the weapon, and note the territory-share line and who was leading at that tick. Press Continue game from here, select your player, set the bots to Medium, and play the branch where you launch at that earlier tick instead of holding to the end. The experiment is: did launching three warnings earlier change who was leading at the Doomsday threshold, or did it just trade an earlier win for the same loss?
The numbers you should read during the takeover are the territory-share line and the Doomsday-clock position at the moment you launch, compared to the original. If launching early puts you above the threshold when the clock crosses the line, the holding was the mistake and the fix is a rule — “I launch the MIRV at the first tick it crosses the launch threshold, not when the clock forces my hand, because the clock decides the game before the strike can change the lead.” If launching early does not change who leads at the threshold, then holding was not the error; the match was decided before your nuke could matter, and the real lesson is about the territory-share line earlier than either launch point — the point where you should have been contesting land instead of saving the weapon. Either outcome is a cleaner, more actionable answer than “I should have used the nuke sooner,” because it tells you the exact tick the decision mattered and what to watch for at that tick in your next match.
Because this is an endgame test, the takeover is especially valuable here: the original endgame was decided by the clock, and the only way to know whether a different nuke timing would have changed it is to actually play the clock from the launch point, which you cannot do by re-watching. Run it at Medium first, then at Hard if the early-launch branch was a photo finish, to see whether a stronger leading nation (one that would not have been caught by your earlier strike) changes the answer. The payoff, again, is one calibrated timing rule for your next Cold War lobby, not a rehash of the match you already lost — and the takeover is the only tool that lets you get that answer without replaying the entire match from spawn.
Failure and counterplay: when the takeover misleads, and how to defend against it
The takeover is a powerful experiment, but like any experiment it can produce a confidently wrong answer if you misuse it, so the failure modes are worth naming explicitly before you start trusting the tool. The first and most common failure is testing the wrong tick: pausing at the moment a mistake became obvious rather than at the moment the alternative was still available, so the player you take over is already in a lost or locked position and every branch you play is doomed before you start. The fix is to scrub back to the last tick where the decision was live, confirm in the player panel that your chosen player is alive and not already surrounded, and only then press Continue. If the takeover opens into a position that feels un-winnable, the tick was too late, not the decision.
The second failure is letting the bots write your lesson. Because the other humans become AI at your chosen difficulty, the continued game will not reproduce the way the original humans played — a bot does not betray an ally, does not trade the way a specific human did, and does not make the exact mistakes that player made. So a branch that “wins” against Medium bots is not proof it would have won against those specific players, and a branch that “loses” is not proof it would have lost. The takeover answers “does this branch hold up against opponents of roughly this strength,” not “would the original match have gone differently.” Counterplay: treat the takeover as a robustness test, not a simulation of the original. If you need to know what those specific players did, re-watch the original; if you need to know whether your decision was sound, take over.
The third failure is difficulty inflation or deflection: choosing a difficulty that makes the answer pre-determined. Easy makes almost any branch look viable; Impossible makes almost any branch look doomed. Both are useful as the sanity-check extremes described earlier, but if you only ever run Easy, you will overrate your plans, and if you only ever run Impossible, you will underrate them. The counterplay is to always run Medium as the neutral baseline first, and to run the extremes only when you specifically need the fragility or the structural-flaw information, recording which difficulty changed the result. The lesson you carry into your next match should be conditional on strength, not a blanket “this works” or “this never works.”
The fourth failure is branch sprawl: taking over to re-litigate the whole match, opening ten different second fronts and three different alliances in one continued game until the experiment stops being an experiment and becomes a different, improvised match. The takeover is for one variable. If you find yourself wanting to change the spawn, the build order, and the alliance in the same continued game, you have left the tool’s purpose, and the answer you get will not be attributable to any single decision. The counterplay is to hold everything constant except the one call you are testing, run it, close the match, and if you have another question, open a fresh takeover from the same or an earlier tick for that next single variable. Keep the experiment single-variable and the answer stays interpretable; let it sprawl and the whole point — a clean test of one decision — disappears.
Mode and map adjustments: where the takeover shines and where to be careful
The takeover behaves differently across game modes and map sizes, and reading those differences is part of using the tool well rather than blindly. In big lobbies — the 50- to 100+-player records where the takeover first became possible to actually select a player by name — the feature is most powerful, because the opening you want to test is too large and too specific to recreate by hand, and the search box in the takeover modal is the only practical way to pick one surviving human from a crowded record. The cost is that the continued match is a large singleplayer game with many AI opponents, which is slower to reach the mid-game position you care about and where the difficulty setting matters more, because “Medium” across fifty AI players is a very different opponent field than “Medium” across five. In a 100-player record, run the branch at Medium and assume the AI field is roughly the strength of the original lobby; do not treat a single Medium AI as a stand-in for the specific human you were trading with, because that human’s idiosyncratic play is exactly what the bot will not reproduce.
In small lobbies and team modes, the takeover is faster and cleaner, because the continued match is smaller and the decision you are testing is usually between a small number of surviving players, so the candidate list is short and the experiment reaches the interesting position quickly. Team modes add one wrinkle: the takeover binds you to one player, so if the decision you want to test was a team decision (a coordinated push, a shared economy space allocation), you are testing only your own player’s half of it, and the teammate behavior you would normally rely on is now an AI at your chosen difficulty. That is still a useful test of whether your call was sound given a cooperative teammate, but it is not a full test of the team decision, because the AI teammate will not coordinate the way your human teammate did. For team-mode “what ifs,” use the takeover to test your own individual commitment and use the team economy space and four-islands team coordination guides for the shared-decision part, which the takeover cannot fully simulate.
Map size and terrain change what you can actually test, because the takeover preserves the real board, including its terrain. On a map with heavy water, a takeover that tests a naval second front is faithful to the original water layout, which is exactly what you want — you are testing the landing against the real coast, not a recreated one. On a map where a specific neutral pocket or rail hub defined the mid-game, the takeover preserves that hub, so the branch you play is contested over the same real chokepoint. The caution is that the continued match is singleplayer, so mode-specific global rules (the Doomsday clock, overtime, the territory-share threshold) run as they would in a singleplayer game, and the end condition you are testing against is the singleplayer one, not a multiplayer tie-break. If your “what if” depends on a multiplayer-only end condition that would not fire the same way in singleplayer, note that the takeover is testing the branch (does this decision improve my position) rather than the exact ending (does this win the multiplayer match), and adjust the lesson accordingly.
The one genuine caution is version and shell. The takeover exists only in the default v0.36+ replay viewer; the classic replay viewer, still available as a toggle, has the watching controls but not the Continue game from here action, and clients older than v0.36 have no takeover at all. So before you plan a takeover, confirm you are in the default viewer on a v0.36-or-newer client, and that the tick you want is in a replay recorded on a client whose state the snapshot can build. If the takeover button is absent, you are in the wrong shell or on an older client, and the fix is to switch to the default viewer or update — not to assume the feature is broken. With those boundaries respected, the takeover is a reliable, reversible instrument across modes and maps, and the adjustments above are what let you read its answers correctly instead of taking them at face value.
When to take over versus rewatch, review, or start fresh: a decision frame
The takeover is the most expensive of the replay tools, so the last thing to internalize is when it is worth the effort and when a cheaper tool is the honest choice. Use this frame, and you will spend the tool’s minutes on the questions where they actually pay off instead of burning continued matches on ones a rewatch would have answered.
| Tool | When it is the right answer | What it answers |
|---|---|---|
| Rewatch / seekable viewer | You need to see what happened, find the moment, or read the state; no change to test | ”Where did my belief break, and what was the state then?” |
| Replay review (TRACE) | You need the earliest controllable error and one next-match change, no live branch to play | ”Which single decision was wrong, and what one rule do I apply next?” |
| Replay takeover (this feature) | You have one specific decision you are unsure about and a branch you want to actually play | ”Does the alternative call hold up against opponents of this strength?” |
| Start a fresh game | You have no specific decision to test, or the position is too early/complex to re-seed | ”General practice and feel, not a controlled answer” |
The rule that separates the takeover from the others is whether there is a branch you want to play, not just a fact you want to find. If your question is “what was the territory-share line at the end?” or “did my ally betray me at tick 500?”, that is a fact, and the seekable replay viewer or a plain rewatch answers it in minutes with no match to run. If your question is “was the decision itself sound,” and you want to know whether a different call would have produced a better position, that is a branch, and only the takeover can play it. If your question is broad — “how do I get better at mid-games?” — there is no single branch to test, and a replay review that names one variable and one next-match rule is the more honest, less wasteful tool, because the takeover needs a narrow target to be interpretable.
Practically, the takeover is worth it when three conditions are all true: you have one named decision (an acceptance, a launch, a front, a trade) that you still think about after the match; the alternative was still available at a tick you can scrub to (the player is alive and the branch was open); and you have a next live match where the answer changes what you will do. If all three hold, the five or ten minutes of a continued match buy a calibrated, conditional answer that no amount of re-watching can give you, and that is money well spent. If only two of the three hold, run the cheaper tool first: no next match, and the lesson has nowhere to land, so review the match instead; no tick where the branch was open, and the player is already gone, so you cannot take over and must rewatch; no named decision, and the experiment has no variable, so review for the one variable first and come back to the takeover once you have it.
The frame also tells you when to stop. A takeover that produces no clearer answer after one or two runs at Medium (plus one extreme if the result was close) is not going to get more useful with more runs; the branch is either robust or it is not, and the tool has told you which. At that point close the continued match, write the one conditional rule you learned, and let your next live match be the real test. The takeover is a study aid, not a substitute for playing, and the moment its answer stops sharpening is the moment to put it down and go play the match where the lesson actually counts.
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