OpenFront Win Conditions: How a Match Actually Ends

Direct answer: which end condition decides your match

The core answer is that a match ends the moment one side’s share of the usable land crosses the live threshold, or the field collapses to a single surviving side, or an anti-stalemate timer forces a finish. In almost every public Free-For-All match, the threshold is 80 percent and the win check is a strictly greater-than comparison, so a side at exactly 80.00 percent has not won yet and one at 80.01 percent has. That single number is the thing you should be reading continuously, because it is the constant the rest of the game moves around. Three other end conditions can be live at the same time and none of them changes that base 80 percent figure: Overtime, which is enabled per-lobby and lowers the threshold by two percentage points per minute after the thirty-minute mark; the Doomsday Clock, which is enabled per-lobby and raises a separate pressure bar in seven waves up to a thirty-five percent ceiling so that a laggard side is drained and then destroyed; and the Ranked finish, where a 1v1 ends on the last surviving player and a 2v2 ends on the last surviving team, with a cancel rule that ends the game the instant one team is wiped while two or fewer players remain. The practical skill this guide exists to teach is reading your own screen and naming which of these five systems—threshold, elimination, Overtime, Doomsday, Ranked—is actually active right now, because the decision you make in the endgame is completely different under each one. A player who plays a slow threshold game while the Doomsday Clock is about to drain them loses the match they were winning, and a player who commits to the last elimination while Overtime is quietly lowering the bar throws away a finish they could have closed in the next thirty seconds.

This is why the guide is organized as a decision procedure rather than a list of rules. The first step is always to name the lobby’s mode, because Free-For-All and Team run different win checks and a Team match can win even though no single member individually crosses the line. The second step is to name which anti-stalemate systems the lobby turned on, because Overtime and the Doomsday Clock only exist when the lobby enabled them, and a public lobby that enabled neither will end purely on the threshold or on elimination. The third step is to read the live number, the share the server will compare against the threshold at the next check, and to estimate when the threshold will next move. Once you can do those three things you can answer the real question, which is not “am I winning” but “which of the five end conditions is the one that will actually end this match, and what is the single cheapest action that wins it under that condition.” The rest of the page walks through each of the five in turn and then works through two concrete scenarios that combine the threshold, Overtime, and the Doomsday Clock, because that is where most real matches live and where most players make the mistake of planning the endgame against the wrong condition.

The one threshold that decides most games: 80% of usable land

The base win threshold in the v0.34.24 ruleset is eighty percent, stored internally as eight thousand permille so the server can compare it without floating-point drift. The win check does not ask “did you own more land than anyone else”; it asks “does your share of the usable land exceed the live threshold.” The difference matters because the denominator is not the raw map. It is the usable land, meaning the land that is still owned and counting at the moment of the check. Land that has fallen out of play through a detonation or a collapse is excluded from the share everyone is chasing, which is why the question “does nuked land count toward my eighty percent” comes up so often and why the answer is that it stops counting for the original owner and, per the patch notes players have cited, also stops counting for the attacker who detonated it. The server computes each side’s share from the tiles it still owns and compares that share against the threshold with a strict inequality. A side at exactly 80.00 percent is not a winner, and a side at 79.99 percent is not a winner, so the final push is always about crossing a moving line, not about maximizing a score. In Free-For-All the win check runs per player, so one player crossing the line ends the match even if an ally or a rival also has land. In Team mode the check aggregates a player with every valid ally, so the team’s combined share is what is compared to the threshold, which is why a four-player team does not need four separate wins, it needs one shared finish line. Understanding that the threshold is a crossing event, not a ranking, changes how you plan: you do not need to be number one, you need to be above the line, and the line is the number to watch, not the rival’s army.

One consequence of the usable-land denominator is that the threshold is a share, not a tile count, and it moves whenever the total usable land changes. When a region is detonated or a base collapses, the denominator shrinks for everyone, which can push a side’s share up without that side having captured a single new tile. This is why a player who is losing on raw tiles can suddenly cross the line the moment a big chunk of a rival’s land goes out of play, and it is also why a player who leads in raw tiles can lose the share race if a rival detonates a large neutral block that was counting toward the rival’s denominator as well. The practical read is that the percentage the server shows you is the number to trust, not your own mental count of tiles, because the percentage already reflects every piece of land that is and is not currently usable. And because the comparison is strictly greater-than, the exact boundary matters: a side at 79.99 is not winning, a side at 80.00 is not winning, and a side at 80.01 has already won, so the endgame is a race to be the first to cross a line that may be moving in real time as land changes hands and as Overtime or the Doomsday Clock reshapes the denominator.

The five ways a match actually ends

There are five distinct end conditions in the v0.34.24 build and the reason players get confused is that they are described as one thing, “the game ends,” when they are really five different triggers the server can fire. The first is the territory threshold, which is the default and the most common: a side’s usable-land share crosses the live threshold and the match ends immediately with a victory. The second is elimination, the last-side-standing path: the server removes eliminated players from the winner electorate first, so in a Free-For-All that keeps collapsing the match can end with a single nation remaining and everyone else gone, and in Team mode it ends when one team still holds land and the other has been fully wiped. The third is Overtime, which is only present when the lobby enabled it: after minute thirty the threshold stops being a fixed eighty and begins to fall two points per minute, so a match that would otherwise stall at seventy-five percent eventually finds a winner because the line is coming down to meet the leader. The fourth is the Doomsday Clock, also lobby-gated: a separate pressure bar rises in seven waves from zero to a thirty-five percent ceiling, and any side whose share drops below the live bar is warned, then drained of troops, then destroyed by a territory-rot deadline, which forces a finish when nobody is willing to commit to the threshold. The fifth is the Ranked finish, which only exists in ranked lobbies: a 1v1 ends on the last surviving player and a 2v2 ends on the last surviving team, with a cancel rule that ends the game the moment one of two teams is emptied while two or fewer players remain. For the deeper look at how a Team side’s 80% threshold aggregates across its members see the team victory threshold guide. The table below is the reference a player can use at the end of a match to name which of the five is live, because the right endgame move is completely different under each one and the screen gives you the signals to tell them apart.

End condition	When it is live	What triggers the finish	What the number on screen is
Territory threshold	Default, every match	A side’s usable-land share exceeds the live threshold	Base 80%, falling if Overtime is on
Elimination	Default, when the field collapses	One side (player or team) remains with land, all others gone	Your remaining share versus zero rivals
Overtime	Only if the lobby enabled it	The threshold sinks 2 points per minute after minute 30	The falling threshold, not a fixed 80%
Doomsday Clock	Only if the lobby enabled it	A side falls below the rising 35% ceiling bar	The live Doomsday bar, rising in waves
Ranked finish	Only in ranked lobbies	1v1 last man, 2v2 last team, or the 2v2 cancel rule	Last surviving side, no threshold needed

Reading the win check: what the server actually compares

The most useful thing you can internalize is that the win check is a comparison, not a timer, and the comparison is made against a threshold that can be moving. For a Free-For-All match the server computes each player’s share of the usable tiles and asks whether that share is strictly greater than the live threshold; the first player to cross it wins and the match stops. For a Team match the server does the same but the share is aggregated: it takes a player’s tiles and adds every valid ally’s tiles and compares that team total against the threshold, which is why a teammate still holding land matters to your finish line and why a team can win even though no single member individually exceeds the threshold. The word strictly does real work here. Because the comparison is greater-than and not greater-than-or-equal, a side sitting at exactly eighty percent is, for all practical purposes, one tile away from winning and one tile away from not winning, and that boundary is where endgame games are decided. The threshold itself is resolved from the base eighty percent and then, if Overtime is active and the game is past minute thirty, reduced by two percentage points for each minute elapsed, with a floor of one percent so the threshold never vanishes. The whole Overtime process is also bounded by a hard one-hundred-seventy-minute game duration, so even a perfectly stalled lobby cannot run forever. What this means for reading your screen is that the number you should trust is the share the server is about to compare, which is your usable-land percentage, and the line it will compare against, which is the threshold, and if you can name both at any moment you know whether you are about to win, about to be caught, or safe for one more push.

There is a subtle but important second comparison the server performs every tick that players usually never see, which is the check that decides whether a side has been eliminated and whether the match is about to be forced to a finish by the last-side-standing path. The elimination path and the threshold path run side by side: the threshold path ends the match the moment a side crosses the line, while the elimination path ends it the moment the field collapses to a single surviving side with the others removed from the winner electorate. In a match that is close on the threshold but wide open on elimination, the two paths are racing each other, and the player who understands that both are live can choose which one to trigger. The win check is also the single place where the mode difference is enforced, because the same threshold logic is applied per player in Free-For-All and per aggregated team in Team, and the same elimination logic removes individual players in Free-For-All but removes a whole team only when no valid member still holds land in Team. This is why the same screen can look like a comfortable lead to a player who is thinking in raw tiles but is actually a narrow threshold race to a player who is reading the share, and why the mode and the anti-stalemate toggles are the two settings that change which of the five end conditions is the one that will actually decide the match.

Overtime: when the threshold stops being 80%

Overtime is the mechanism that converts a stalled match into a finished one by lowering the win line instead of by culling anyone. In the v0.34.24 defaults it is disabled, starts at minute thirty, and drops the threshold by two percentage points per minute, which means the line falls from eighty percent to seventy-eight at minute thirty-one, to seventy-six at thirty-two, and so on. Because it drops by two per minute rather than by one per thirty seconds, the practical cadence is that the threshold moves every minute and each move is a full two-point step, so you should plan the endgame in one-minute windows, not in half-minute windows. The threshold has no floor, so in a long Overtime match the line can keep sinking far enough that even a side with a modest share eventually crosses it, which is the entire point: Overtime guarantees that a leader who simply holds will, if the game goes long enough, win on their own, and a challenger who cannot close the gap by force will eventually watch the line come down to them. The one-hundred-seventy-minute hard cap sits on top of all of this, so the latest the threshold-based finish can occur is bounded. The decision Overtime creates is a three-way fork. If you are the leader, your job is to protect the share that is about to become a win and avoid a trade that drops you under the line, because the line is coming to you and you do not need to take more risk. If you are a challenger who can close the gap, the falling line is a deadline, and you should attack the cheapest tiles that would push you over before the next drop lets the leader settle into an uncontested lead. If neither you nor the leader can move, the match is in the holding pattern where the line is doing the deciding, and the player with the larger share at the moment the threshold crosses them is the one who wins without firing another shot. Reading whether Overtime is live is the first question you should ask at minute twenty-five in any match you are not clearly winning. A useful habit is to do the Overtime arithmetic out loud at the half-hour mark: if the threshold is at eighty and you are at seventy-four, the line will reach you in two minutes, so you have exactly two minutes of margin and you should treat the next push as the deciding one. If you are at seventy and the line is at eighty, you have a five-minute cushion, which is enough to commit to a single decisive attack rather than a scattered probe. The other side of the ledger is that a leader who is at eighty-two and the challenger at seventy-eight should expect the challenger to get a four-minute window before the line crosses them, so the leader should use those four minutes to lock down the expensive tiles and deny the challenger the cheapest path to the line rather than chasing the challenger into a trade that would drop the leader below the falling line. If Overtime is live and you want the deeper read on how to hold a falling line, see the dedicated winning on overtime guide, which walks the threshold-sink case by case.

The Doomsday Clock: a rising bar that forces a finish

The Doomsday Clock is a second, independent anti-stalemate system and it works in the opposite direction from Overtime: instead of lowering the win line, it raises a pressure bar that punishes the low-share side. For the full wave-by-wave walk of the Clock’s presets and speed settings see the dedicated Doomsday Clock guide. In the v0.34.24 build the clock stays at zero percent for the first ten minutes, which is deliberate, because the early game is supposed to be decided by combat and by whoever is expanding, and a stalemate-breaker that fires in the first ten minutes would punish a side that is simply behind on spawn. After the ten-minute grace the bar climbs in seven waves up to a thirty-five percent ceiling, and in Free-For-All the waves land at two, four, seven, eleven, seventeen, twenty-five, and thirty-five percent, and on the Normal preset they are fully reached at roughly twelve and a half, sixteen and a half, twenty, twenty-four, twenty-seven and a half, thirty-one, and thirty-five minutes, with the other presets compressing that ladder faster. In Team mode the same ladder is raised, to three, six, ten, fifteen, twenty-one, twenty-eight, and thirty-five percent, because a side survives while either of its members is above the bar, so equal pressure collapses the team field more slowly. Four speed presets change how fast the ceiling is reached: normal arrives at thirty-five at thirty-five minutes, slow at forty-five, fast at twenty-five, and veryfast at fifteen, so the ceiling time is the knob that controls how long a laggard gets. The ceiling is thirty-five percent specifically because in the eighty-five tournament games the design team measured, the runner-up’s end-of-game share never exceeded twenty-one point six percent, so a bar above roughly sixteen percent catches the same players while a higher ceiling would start dooming the leader. When a side’s share falls below the live bar the side gets a thirty-second warning, then its troops begin to drain, and if it is still below the bar when the rot deadline passes its territory is destroyed, which ends or reshapes the match. The decision under the Doomsday Clock is whether to win by force before the bar reaches your share, or to keep your share above the rising line long enough that the clock is the one squeezing your opponent instead. The key number to read under the Clock is the gap between your share and the live bar, because that gap is the amount of land you can afford to lose before the thirty-second warning starts, and the warning is visible on screen so you always know exactly how much margin you have. The Doomsday Clock and Overtime can both be live in the same lobby, and when they are the endgame carries two moving lines at once, a falling win threshold and a rising doom bar, which is the most complex end state in the game and the one where the player who can read both lines simultaneously wins the match they are already winning. The practical read is to compute both gaps at the same time: your gap to the win line tells you how close you are to winning, and your gap to the doom bar tells you how close you are to being drained, and the endgame decision is the single action that widens the first gap while keeping the second one from closing.

Ranked end states: 1v1 last man, 2v2 last team, and the cancel rule

Ranked matches use the same underlying win check but add their own end states, and the reason players who only play public Free-For-All have never seen them is that ranked is a separate mode not offered in every lobby. In a ranked 1v1 there are exactly two players and the match ends when one of them is eliminated or when one crosses the threshold; because there are only two sides, the elimination path is the realistic finish, and the threshold is the alternate finish, so a 1v1 player is effectively always playing a last-man race with a threshold as a fallback. In a ranked 2v2 the win check aggregates the team the same way a Team match does, so the finish is the last surviving team rather than the last surviving individual, and a side can lose even while a member still holds land, because what ends the match is the team being emptied. On top of that the v0.34.24 build encodes a cancel rule for 2v2: when ranked is enabled and there are exactly two valid teams and two or fewer players remain, the server runs an empty-team check, and the moment one team has no valid player with land the game ends and the other team is declared the winner. This is the 2v2 equivalent of the last-man rule and it exists so that a 2v2 does not drag on after one side is already dead. The practical implication is that in ranked the end state you are reading is named by the mode, not by the threshold: a 1v1 player should be asking “am I the last one alive or am I about to cross the line,” and a 2v2 player should be asking “is my team still fully alive and is the rival team about to be emptied.” None of these ranked end states appear in a casual public Free-For-All, so a player who has only played public matches will see a threshold finish or an elimination finish and will not understand why a ranked player is talking about last teams and cancel rules. Knowing which mode you are in is the first thing that tells you which end state to read. A practical way to keep this straight in a ranked match is to name the end state out loud at the start: a ranked 1v1 is a last-man race with the threshold as a fallback, and a ranked 2v2 is a last-team race with the cancel rule as the trigger. In either case the end state is determined by the mode, not by the threshold, so the screen reading you should be doing is different from a public Free-For-All match. In a 1v1 you are watching your own survival and the rival’s survival, and the threshold is only the alternate path if one side crosses the line before the other is eliminated. In a 2v2 you are watching both members of each team, because the team is the unit that ends the match, and the cancel rule means that the instant one team has no valid player with land the match is over and the other team is declared the winner. This is the end state that trips up players who have only played public matches, because in a public Free-For-All the match never ends on “the last team” and there is no cancel rule, so a ranked player’s language about last teams and cancel rules refers to a system that simply does not exist in the public lobbies they are used to.

Scenario one: a 76.4% leader with Overtime live and three minutes left of margin

Assume a public Free-For-All with Overtime enabled, the match is at minute thirty-two, the threshold has already fallen to seventy-six percent, and you are the leader at seventy-six point four percent with a single rival at forty-one percent. The numbers that matter are that you are only four tenths of a point above the line, that the line will drop to seventy-four in the next minute, and that your rival is nowhere near threatening the threshold. The correct read is that you are already winning on the line and the only thing that can take it from you is a trade that drops your share under seventy-six, so the decision is to stop expanding into contested land and defend the share that is about to become an uncontested win. A player who keeps attacking the forty-one percent rival here is spending troops to gain a tile or two of a share they do not need, while the rival’s counter-arc can push your share under the falling line. The three-branch fork applies cleanly: commit the last reserve only if you can name a specific border tile that converts and still leaves a reserve that absorbs the counter-strike; reposition behind a mutual-nuke standoff if you cannot name that objective but can fund a high-level SAM ring that intercepts the last arc before it reaches your core; and hold liquid and let the threshold settle, which is the right branch here because Overtime is enabled and you are the leading side, so the falling line is closing the match for you. The countermeasure if the rival tries a desperate last push is that your defending share is already above the line, so a push that fails does not change the outcome, and a push that succeeds must cross the forty-nine point six percent of land you must lose to drop under the line, which is far more than a single desperate arc can take. The skill is recognizing that at minute thirty-two with Overtime live, the leader’s job has switched from winning to not throwing, and the number that tells you that is the gap to the falling line, not the rival’s army size. The arithmetic is the whole skill here: the leader knows the line is at eighty and falling two points a minute, so at minute thirty-two the line is at seventy-six, and a leader at seventy-four has two minutes of margin before the line catches them, which is enough to lock the two or three most expensive tiles and refuse to trade. A challenger in the same situation who is at seventy and the line at seventy-eight should read that as a five-minute window to attack the cheapest tiles that push them over the falling line, because waiting longer lets the leader settle into an uncontested lead that the falling line will hand to them for free. The same arithmetic runs the other way for the challenger: if you are the one behind, the falling line is not a threat but a shrinking target, and every minute of safe territory you defend is a point of threshold you force the leader to chase instead of consolidating, which is why a patient tile-by-tile defence is the correct posture when the margin is this thin.

Scenario two: two teams at 52% and 48% under a rising Doomsday bar

Now assume a Team match with the Doomsday Clock enabled, the clock is at its twenty-five percent bar, your team’s combined usable share is fifty-two percent, and the rival team’s combined share is forty-eight percent. The numbers that matter are that both teams are above the twenty-five percent bar so neither is being drained yet, that the next bar is twenty-eight percent, and that the ceiling is thirty-five percent, so the clock is about to start squeezing anyone who falls under twenty-eight. The read here is completely different from Scenario one: there is no threshold finish coming quickly because neither team is anywhere near eighty percent, so the end of this match will be forced by the clock, and the clock punishes the lower share. That means your advantage is real but it is measured in distance from the bar, not in distance from the threshold, and the decision is to keep your team above the next bar while the clock does the work of draining the rival if their share slips under twenty-eight. The wrong move is to treat this like a threshold game and spend troops to chase tiles you do not need, because a trade that drops your team under twenty-eight puts you on the drain and the rival becomes the one watching you rot. The correct branch is to protect the share that keeps you above the rising bar, push only at the borders where a gain also lowers the rival’s share below the bar, and use your reserve to intercept the rival’s attempts to climb back above twenty-eight. If the rival’s share is at forty-eight and the next bar is twenty-eight, the rival has twenty points of margin, so the clock is not immediately going to save you; the clock gives you time, not a free win, and you still have to hold your own share above the line. The countermeasure to the rival clawing back is that every tile they take above the bar is a tile you must be able to retake before the next bar lands, and the map shape decides whether that retake is cheap or expensive. The lesson is that under the Doomsday Clock the end state you are reading is distance from the rising bar, and the decision is about keeping your share above it, not about crossing a threshold. The same read applies to the trailing team at forty-eight: the gap to the bar, not the gap to the leader, is the number that determines whether the next wave or the opponent’s arc ends the game first, so the trailing team’s correct move is to hold a reserve that can convert one contested border before each bar lands rather than to spend it all in a single doomed push that leaves them below the next level with nothing left to defend.

Failure modes, counterplay, and mode or map adjustments

The most common failure under each end condition is the same in shape: misreading which system is live and playing the endgame for the wrong one. Under the threshold, the failure is a player who is at seventy-eight percent in a no-Overtime lobby and holds, because the bar is not coming down and holding is a losing default when the line is fixed at eighty. Under Overtime, the failure is a leader who keeps expanding into contested land at minute thirty-three and trades away the four-tenths gap to the falling line, or a challenger who waits for a perfect attack instead of taking the cheap tiles before the next drop lets the leader settle. Under the Doomsday Clock, the failure is a side at twenty-four percent with the bar at twenty-five who assumes the clock is not their problem because they are “above the leader’s opponent,” when in fact they are already under the bar and the drain has started. Under Ranked 2v2, the failure is a player who thinks the match is over when their teammate is wiped but their own land remains, when the cancel rule already ended it the moment the team was emptied. The counterplay in each case is the same discipline: name the system, name the number, then make the move that protects that number. Mode changes the system you read: in a Free-For-All you read your own share against the threshold or the bar, in a Team match you read your team’s aggregated share, and in Ranked you read the last-side or cancel condition. Map shape changes the cost of the move: on a compact map the endgame borders are short and the last push is cheap, so the threshold finish comes faster and the holding pattern is shorter; on a normal map with water or mountains the final tiles are expensive to take, so the Overtime and Doomsday finishes are more common because nobody can afford the last push, and the falling line or the rising bar does the deciding. The adjustment is to let the map tell you whether the finish will be a push you can afford or a timer you must survive, and to match your endgame to that, because the end condition that is live is only half the picture, and the map decides whether you can finish it on your terms or have to wait for the system to finish it for you.

How to read your own end state in the next match

The checklist to run every endgame is short, and running it in order is the whole skill. First, name the mode: is this Free-For-All, Team, or Ranked, and if Ranked, is it 1v1 or 2v2, because the mode tells you which end states are even possible. Second, name the live systems: is Overtime enabled, is the Doomsday Clock enabled, and at what minute is each of them, because a lobby can have both, neither, or one, and the decision you make is different under each combination. Third, read the two numbers: your usable-land share and the live threshold or bar, and the gap between them, because that gap is the only number that tells you how close the match is to ending. Fourth, ask which end condition is about to fire first: is the threshold about to cross your share, is your share about to drop under the Doomsday bar, is the field about to collapse to a last side, or is a Ranked cancel about to trigger. Fifth, make the move that protects that number, which for a leader means defending the share that is about to become a win and for a challenger means attacking the cheapest tile that changes the outcome before the next step of the timer does it for the leader. The table below is the quick reference for naming the live system from the screen.

What you see on screen	Which end condition is live	What to do next
Your share near 80% and no timer moving	Territory threshold	Push the last tiles that cross the line
Threshold falling each minute after 30	Overtime	Leaders hold, challengers take cheap tiles before the next drop
A separate bar rising and your share near it	Doomsday Clock	Stay above the bar; drain the rival if they fall under it
Rival teams emptying, you in a 2v2	Ranked cancel	Confirm your team is still fully alive
Everyone but you gone	Elimination / last side	Survive; the match is ending on the last side standing

If you can name the mode, the live systems, and the two numbers in under ten seconds, you are reading the end state the way the server is computing it, and the endgame stop being a guess. That is the entire point of this guide: the win condition is not one thing, it is five systems, and the player who can name which one is live at minute twenty-five wins the match the player who is still guessing about loses.