GUIDES
OpenFront Terra Nullius: How Much Force to Commit to Unowned Land
A practical v0.34.22 mechanics guide for the neutral-land capture decision: the fixed per-tile fuel cost, the speed floor where more troops stop helping, the terrain table, border-width as a free speed lever, and why fallout double-taxes unowned land. Includes two worked scenarios and a repeatable force-commit table.
Direct answer: unowned land is a fixed fuel charge, not a ratio fight
On unowned land there is no defender, so the per-tile troop cost is a fixed fuel charge, not a ratio: a human pays mag/5 troops per tile (16 Plains, 20 Highland, 24 Mountain) and a bot half that. The size of your committed force changes how fast the frontier moves and how far it can reach, but it does not change what you pay per tile. More troops stop buying speed once committed troops pass 400× the tile cost (about 6,600 / 8,000 / 10,000 for the three terrains). Fallout on the target makes it both slower and more expensive to take.
That last sentence is the whole guide, and it is the thing players almost never have numbers for. When you click a tile that another player or a bot already owns, the code takes a ratio path: attacker and defender bleed into each other, the attacker’s share of the combined magnitude decides the outcome, and the loss scales with both sides. That is the territory of the attack ratio guide and the land combat guide. But when you click a tile that belongs to nobody, the code drops the ratio entirely and switches to a defender-null branch, and the numbers it uses are completely different. The defender magnitude is zero, so there is no “percentage of my army should I send” slider in the same sense; instead the question becomes a budget question: how many tiles can this committed force pay for before the push starves, and how quickly does it pay them. Every section below builds that budget model from the source, because the unowned-land decision is one of the few places in the game where the player-visible attack bar is hiding a fixed per-tile price that does not depend on how much you sent. The practical consequence is that “commit more troops to expand faster” is only half true: committing more makes the frontier sweep faster up to a hard speed ceiling, and it extends how deep the push can reach, but it never lowers the per-tile invoice, and past the ceiling it buys nothing at all. There is a fourth consequence that the first sentence implies but the player rarely checks, and it is the reason this decision is a budget rather than a rate: the per-tile invoice is paid whether or not the tile you take is worth the troops it cost, so a long, low-value neutral fringe can quietly drain a committed force even when the push is winning every individual tile. The unit of planning is therefore not “how many troops do I send” but “how many tiles do I need, at this terrain’s price, and do I want to pay for them with this much of my army.” That single reframe is the spine of the whole guide, and every section below is a refinement of it: the speed model tells you the commit size that hits the ceiling, the terrain table tells you the price of each tile, the border term tells you the free lever on speed, the fallout section tells you the multiplier that can run three to five times the clean invoice, and the two scenarios show the same committed force succeeding on Plains and starving on scarred Highland.
Version boundary: what v0.34.22 documents and what is stable
Everything on this page is read from the v0.34.22 tag of the OpenFrontIO repository, which is commit 4e83752 dated 2026-10-01. That is the version boundary you should trust for the neutral-land capture model. The release immediately after it, v0.34.23, published 2026-10-05, is a graphics-crash recovery fix and contains no gameplay-balance change to the combat, terrain, or capture systems, so the effective player-facing rules described here are unchanged between the two releases. The upstream main branch is further ahead with unreleased work on other systems, but none of that touches the terra-nullius constants, the mag/5 and mag/10 per-tile losses, the 2000×tileCost/attackTroops clamp, or the ordering of the fallout branch relative to the defender-null branch, so anchoring to the v0.34.22 tag is both safe and complete for this topic.
Three facts are genuinely version-sensitive and worth stating so you know exactly which release they were verified against. First, the three constants TERRA_NULLIUS_COST_SCALE = 2000, TERRA_NULLIUS_MIN_COST = 5, and TERRA_NULLIUS_MAX_COST = 100 are the v0.34.x values; if a future release rescales the 2000 multiplier or moves either clamp floor, every speed-floor troop threshold on this page shifts proportionally. Second, the per-tile loss of mag/5 for a human attacker and mag/10 for a bot attacker is the current terrain-magnitude rule, and it is the reason the three terrains cost 16 / 20 / 24 troops per tile for a human push; a change to the terrain magnitudes or to that division would rewrite the whole fuel table. Third, the ordering detail that the fallout branch runs before the defender-null branch, and that falloutDefenseModifier applies even when the defender is null, is the current behavior and it is what makes irradiated unowned land a double tax on expansion; if a future release reorders those branches or stops applying the modifier to a null defender, the scar no longer taxes expansion and the whole “nukes deny expansion” argument collapses. If you read a guide or a forum post quoting a different scale factor, a different floor, or a different per-tile division, treat that figure as superseded by the v0.34.22 source read used here. One more boundary note is worth recording because it is the most common source of stale community numbers: the v0.34.x line is the generation in which the unowned-land path was given its own named constants and its own clamp, so pre-v0.34 community advice that describes “expansion speed” only in terms of the attack percentage is talking about a different code path and should not be transplanted to the current rules. The constants are the part of the model most likely to be silently changed in a balance pass, which is exactly why every threshold on this page is given as a multiple of the tile cost and the scale factor rather than only as a bare troop number: if the 2000 becomes a 1500 or the floor moves from 5 to 4, the formula 400 × tileCost for the speed floor and 20 × tileCost for the slow ceiling change in a predictable way, and you can recompute the whole table in seconds instead of trusting a number that no longer matches the build you are playing.
The unowned-land cost model: a fixed per-tile fuel charge
The single most important structural fact is that on unowned land the attacker’s troop loss does not depend on the size of the committed force. In the defender-present path, the loss is a function of the ratio of the two magnitudes, so a bigger attacker takes more of the fight and a smaller one takes less; the more troops you send, the more troops are at stake per tile. In the defender-null path there is no second magnitude, so the code cannot form that ratio, and the loss instead falls back to a terrain-based constant: the attacker loses the terrain magnitude divided by five for a human, and divided by ten for a bot, on every unowned tile it takes. The committed force size does not appear in that per-tile number at all. That is the “fuel” model, and it is the exact opposite of the intuition players carry over from contested fights.
To make this concrete: Plains has a magnitude of 80, so a human attacker loses 80/5 = 16 troops per Plains tile, no matter whether it sent 400 troops or 40,000. Highland is magnitude 100, so it is 20 troops per tile. Mountain is magnitude 120, so it is 24 troops per tile. A bot attacker pays half of each, so 8, 10, and 12 respectively. The practical way to think about it is as a range budget: your committed force is a fuel tank, and each unowned tile you take is a fixed amount of fuel burned. If you commit 4,000 troops and each Plains tile costs 16, that force can pay for about 250 Plains tiles before it is spent; commit 4,000 troops into Mountain at 24 per tile and the same force pays for only about 166 tiles. The force did not get “weaker” on Mountain; the invoice just got higher, so the same tank reaches less far. This is why the same army that sweeps a flat open region looks unstoppable can stall on a Mountain front, and it is why the force-commit decision is really two decisions in one: how deep does the push need to reach, and does this committed size have enough fuel for that many tiles at this terrain’s price. The early expansion rhythm guide asks when to switch targets; this section fixes the cost of each target tile, which is the input that tempo guide needs but does not compute.
The speed model: where “more troops” stops buying speed
The second structural fact is that committed force does control annexation speed, but only up to a hard ceiling. The annexation of an unowned tile advances on a tick fraction, and the code computes that fraction as 2000 × tileCost / attackTroops, clamped between 5 and 100, then divided by borderSize × 2. The 2000 × tileCost / attackTroops term is the part that responds to your committed force: the more troops, the smaller the fraction, the faster the tile flips. But the clamp has a floor of 5, and that floor is the maximum speed. Once 2000 × tileCost / attackTroops would go below 5, the clamp snaps it to 5 and the annexation runs at its fastest possible rate, and sending any additional troops does not lower the fraction below 5, so it does not make the frontier move any faster. The committed troops that reach that floor are 2000 × tileCost / 5 = 400 × tileCost. On Plains (tile cost 16.5) that is about 6,600 troops; on Highland (tile cost 20) about 8,000; on Mountain (tile cost 25) about 10,000.
The other end of the clamp is the ceiling of 100, which is the slowest annexation. That ceiling is hit when 2000 × tileCost / attackTroops reaches 100, which is at 2000 × tileCost / 100 = 20 × tileCost committed troops: about 330 on Plains, 400 on Highland, 500 on Mountain. Below that, the push is pinned at the slowest possible rate and is exactly the “tiny nibble” stall players describe in the community threads, where a small percentage keeps clicking and the border barely creeps. Between the two floors, speed rises smoothly with committed force: a Plains push at 1,500 troops is noticeably faster than one at 700, but a Plains push at 8,000 is exactly as fast as one at 12,000, because both are past the 5-floor. So the decision is not “send more to go faster”; it is “send enough to hit the speed floor you want, and no more unless you need the extra fuel for depth.” The dead zone at the top is where the common mistake lives: players who send a huge army into flat open land and assume the extra troops make the border crawl faster are, past 6,600 Plains troops, paying the per-tile invoice for thousands of troops that do not change the annexation rate at all. A clean way to internalize the two floors is to think of the committed force as sitting on a speed curve with three regions. Below the slow ceiling (under about 330 / 400 / 500) the push is pinned at the maximum fraction of 100, which is the slowest annexation, and that is the region where “I’m attacking but the border is frozen” is literally correct: the tile advances one tick-fraction at a time and the fraction is at its worst. Between the two floors the speed rises smoothly and predictably with committed force, and this is the region where every extra hundred troops you commit makes a real, visible difference to how fast the frontier sweeps. Past the fast floor (over about 6,600 / 8,000 / 10,000) the speed is pinned at the minimum fraction of 5, the fastest annexation, and the region is flat: the curve has hit its floor and no additional troops buy any more speed, so the only reason to commit in this region is the fuel the extra troops provide for reaching deeper, never the rate at which the tiles arrive. The practical rule that falls out of the curve is to aim at the fast floor for the terrain you are pushing, add only as much beyond it as the depth of the push requires, and stop. If you are not racing against an opponent on that exact neutral front, committing well past the fast floor is pure waste: the troops are alive, they are in the fight, and they are not moving the border any faster.
The terrain table: fuel and speed-floor per tile
Because both the fuel and the speed floor scale with the terrain, a single table captures the whole neutral-land decision and it is the reference to keep open while you are planning a push. The numbers below are the v0.34.22 terrain magnitudes and tile costs, the human mag/5 and bot mag/10 per-tile losses, and the committed-troop thresholds that hit the 5-floor (fastest) and the 100-floor (slowest) of the clamp.
| Terrain | Magnitude | Tile cost | Human loss / tile | Bot loss / tile | Speed floor (fastest) at | Speed ceiling (slowest) at |
|---|---|---|---|---|---|---|
| Plains | 80 | 16.5 | 16 | 8 | ~6,600 troops | ~330 troops |
| Highland | 100 | 20 | 20 | 10 | ~8,000 troops | ~400 troops |
| Mountain | 120 | 25 | 24 | 12 | ~10,000 troops | ~500 troops |
Reading the table left to right, the first two columns are the raw terrain inputs and the middle two are the fuel: Mountain burns 1.5× the per-tile troops of Plains for a human (24 vs 16), so a Mountain front is the most expensive to take and the one that starves a committed force fastest. The last two columns are the speed thresholds and they move with the tile cost: Mountain needs about 10,000 committed troops to reach the fastest annexation, where Plains needs only about 6,600, and Mountain’s slow-nibble ceiling is 500 troops where Plains’ is 330. The two most useful inferences come from combining the columns. First, the same committed force is a better deal on flatter ground: a force that hits the fast speed floor on Plains at 6,600 troops is still below the speed floor on Mountain at that same count, so a Mountain push with 6,600 troops is both more expensive per tile and slower than the same 6,600 on Plains. Second, the depth range shrinks on rougher ground: the 4,000-troop example from the cost section reaches about 250 Plains tiles but only about 166 Mountain tiles, so the same army owns a shorter front on Mountain. The table is the tool for the two questions the whole guide answers: is this terrain worth the per-tile invoice, and does my committed size have the fuel and the speed to take the stretch I want? Two more readings of the table are worth internalizing before you use it in the game. The first is the bot column, which is why the neutral land you face is not always a neutral land you are fighting: a bot attacker pays only mag/10, so the same 200-tile Mountain stretch that costs you 200 × 24 = 4,800 troops of fuel costs a bot only 200 × 12 = 2,400, and a bot can therefore commit to a neutral push and still carry a larger reserve than you can for the same front, which is the mechanical reason a bot can out-expand you on rough ground even when you are winning every contested border. The second reading is the ratio between the two speed columns: the fast floor is always exactly 20× the slow ceiling for a given terrain (because 400×tileCost versus 20×tileCost), so the “useful” band where committed force actually buys speed is a factor of 20 wide, and that tells you the granularity of the decision: there is a wide middle range where your commit matters a great deal, and the two edges where it does not. When you are choosing a commit size for a specific push, the move is to pick a number near the fast floor for the terrain, check that the fuel column times the number of tiles you want stays under that number, and only push higher if the fuel math says you will not reach the goal.
Border width and shape: the free speed lever
The term that is easy to overlook is the /(borderSize × 2) at the end of the tick-fraction formula, because the attack bar does not show it and the player does not choose it as a number. But it is the single free lever on annexation speed, and it works in the player’s favor in a way that rewards keeping a broad, even front. borderSize is the number of tiles of your edge that are adjacent to the unowned land, and the formula divides the whole tick fraction by twice that number. A wider border therefore shrinks the tick fraction and speeds up the annexation, so the same committed force sweeps an empty sector faster from a broad front than from a narrow spearhead. This is the mechanical reason experienced players keep the neutral border wide and even instead of concentrating the push on one long thin line: the broad front is doing twice the work per tick.
The interaction with shape is what makes this a real decision rather than a footnote. If your border with the unowned land is a long, thin line, borderSize is small and the annexation runs at the fraction’s full, slow value; if you have rounded your position so the same troops face a short, deep, wide front, borderSize is large and the same troops annex much faster. The limit case is the annexation enclosure guide: when you fully enclose a target and complete the pocket, the capture resolves at essentially zero troop cost and does not pay the per-tile fuel at all, which is the extreme end of “shape beats force.” For plain neutral land you cannot always enclose it, but you can still manage the border width, and the table of trade-offs is simple: a narrow spearhead is where you are choosing depth over speed and you are paying the slow-fraction penalty on purpose; a broad front is where you are choosing speed and you are burning your committed fuel across more tiles at once. The decision couples with the fuel budget, because a broad front spends the fuel tank faster (more tiles advancing in the same tick) even though each tile arrives sooner, so a broad front on a long campaign can starve sooner than a narrow one that creeps but conserves. The repeatable rule: widen the front when you are racing to lock down a region before an enemy can take it, and narrow the front when the enemy is the one rushing and you want the same force to reach further and last longer.
Fallout on unowned land: the double tax
The sharpest non-obvious interaction is that fallout taxes unowned-land capture, not just defended capture, and it taxes it twice. The source orders the fallout branch of the capture logic before the defender-null branch, and falloutDefenseModifier is applied even when the defender is null. That means an unowned tile that carries fallout is penalized in the same way a defended one is, even though there is no defender to be multiplied. Two effects land on the player at once. First, the speed is hit: the modifier raises the annexation cost, so the tick fraction is larger and the tile flips more slowly, meaning the same committed force creeps across a scarred stretch at a reduced rate. Second, the fuel is hit: the effective per-tile cost is multiplied by the fallout defense modifier, so each irradiated tile burns more of the committed force’s tank than a clean tile of the same terrain would.
The modifier itself is falloutDefenseModifier, which returns 5 - 2 × globalFalloutRatio — between three and five, highest when the map is least irradiated. So a scar is its most punishing to cross right after the first nuke, when the global ratio is near zero and the multiplier is 5, and it relaxes toward 3 as more of the map becomes irradiated. That ordering has a concrete strategic consequence for expansion, separate from the denial effect: a nuke does not only deny the player it was aimed at, it raises the expansion invoice for anyone, including you, who must push through the scar. The no man’s land fallout guide covers this from the retake-and-win-denominator side; this section is the expansion side, which is the part that bites when you are the one expanding and the scar is in your path. The Doomsday Clock compounds it: its “rot” hands tiles to nobody and stamps them with fallout, so a map can accumulate unowned, irradiated land with no player firing a single nuke, and that rot land is exactly the double-taxed case — it costs more per tile and annexes slower than clean unowned land. The practical rule: treat a nuke scar or a rot zone as a region where your effective per-tile fuel is 3 to 5 times the clean value and your annexation is correspondingly slower, so a push that is comfortable on clean Plains at a given troop count can starve in the same stretch of scarred Plains at the same count, and the correct response is to either commit more fuel, route around the scar, or convert it first.
Scenario 1: a Plains push at the speed floor vs a Mountain push at the same troops
Assume a mid-game player who has consolidated and is ready to expand into a neutral region, with a committed force of 8,000 troops and a goal of taking a stretch of about 200 tiles before the next enemy contact. The assumptions are a single committed force, no enemy army on the target, a border width that holds steady at a moderate value, and no fallout anywhere on the front. On a Plains front, the per-tile fuel is 16, so 200 tiles cost 200 × 16 = 3,200 troops of fuel, leaving the 8,000-troop force with 4,800 to spare after the push, and because 8,000 is already past the Plains speed floor of about 6,600, the annexation runs at the maximum 5-tick rate the whole way. The push is fast and the force still has a large reserve to defend the new border. The same 8,000 troops now pushed into a Mountain front tell a different story. The per-tile fuel is 24, so 200 tiles cost 200 × 24 = 4,800 troops, leaving only 3,200 to spare, and because the Mountain speed floor is about 10,000, the 8,000-troop force is below the fastest rate, so the annexation is slower even before the fuel problem. The net result: the same army that finishes a Plains push quickly and safely reaches the same 200 Mountain tiles more slowly and ends with a smaller reserve. The decision the scenario teaches is that terrain must be priced before the commit: if the goal is 200 Mountain tiles, the correct call is to commit about 10,000 to hit the speed floor and still carry a reserve, or to shorten the push, or to accept the slower rate. The counter-move for a player who sees the opponent committing 8,000 to a Mountain front is to contest the border rather than the tiles, because a Mountain front at 8,000 troops is running below its speed floor and the frontier is moving slowly enough that a smaller defensive line can contest it; the player pushing through scarred Mountain terrain at 8,000 has a still worse position, because the fallout doubles the effective fuel per tile on top of the already-high Mountain invoice, which is the failure the next scenario works out. There is a clean way to use this scenario as a pre-commit check, and it is worth stating as a repeatable procedure: before you commit to a neutral push, write down three numbers — the terrain, the number of tiles, and the committed force. Multiply the terrain’s per-tile fuel by the tile count to get the total fuel the push will cost. Compare that to the committed force: if the total fuel is more than about 70 to 80 percent of the committed force, the push will end with little or no reserve and you are one surprise enemy contact away from being unable to defend the new border, so either raise the commit, shorten the tile count, or accept the reserve risk. Then check the committed force against the terrain’s fast floor: if it is below the fast floor, the push is also running slow, and the two problems compound, which is the Mountain-at-8,000 case. The whole check is two multiplications and two comparisons, and it turns the “should I push” question, which players usually answer by feel, into a fuel-and-speed calculation with a clear pass or fail.
Scenario 2: pushing through a nuke-scarred neutral corridor
Now the same 200-tile stretch is a neutral corridor that a nuke has scarred, and the player must push through it because the road to the objective runs the length of the scar. Assume a Highland corridor (magnitude 100, tile cost 20, clean per-tile fuel 20 for a human), a committed force of 8,000, and a moderate, stable border. On the clean Highland the push costs 200 × 20 = 4,000 fuel, leaves 4,000 reserve, and at 8,000 troops is at the Highland speed floor of about 8,000, so it annexes at the maximum rate. Now apply the scar. With the map barely irradiated, falloutDefenseModifier is near 5, so the effective per-tile cost is multiplied by up to 5, which means the 200-tile push now costs toward 200 × (20 × 5) = 20,000 troops of fuel — far more than the 8,000 committed — and the annexation runs at the slow end of the fraction. The 8,000-troop force cannot clear a fully-scarred 200-tile Highland corridor at that modifier: it would starve well before the far end. Even at the relaxed 3× modifier the cost is toward 200 × 60 = 12,000, still more than the committed force. The decision here is not “send more troops and grind it out,” because the fuel is a fixed invoice that the force is too small to pay; the decisions are to route around the scar, to convert the scar first (a water nuke, or clearing it), or to commit a force sized to the scarred cost — on the order of 12,000 to 20,000 depending on the actual fallout ratio — which is a large fraction of a late-game army and therefore a real commitment. The counter-move for the defender is the mirror image: a scar you place in an enemy’s expansion path is an expansion tax you do not have to actively hold, so a small, well-placed nuke that forces the opponent to either commit 20,000 troops to push through or reroute is worth far more than its blast damage. This is the same three-and-five-times logic the which nuke to commit guide uses for the blast, applied to the expansion path instead of the target. One subtlety keeps the numbers from being worse than they look, and it is the reason the scenario says “up to” rather than a single flat multiplier: the falloutDefenseModifier scales with the global fallout ratio, so a scar is most punishing to cross when it is the only irradiated patch on a clean map (global ratio near zero, multiplier near 5) and relaxes toward 3 as the rest of the map becomes irradiated. That means the worst-case scar you can push through is early-game, when one nuke has made the first scar on an otherwise clean board; by the time the map is full of scars the per-tile invoice on any given scar has dropped toward the 3× case, and the same 8,000-troop force that could not clear a 200-tile Highland scar early might just barely manage it late. The planning move this gives you is to price a scar push against the current global fallout ratio, not against a worst-case constant: read the Doomsday Clock, estimate the global ratio, multiply the clean per-tile fuel by 5 − 2 × globalFalloutRatio, and re-run the scenario-1 fuel check. If the result is that your committed force cannot cover the scarred stretch, the decision is not to grind but to route, to convert the scar, or to commit a force sized to the scarred cost, and that decision should be made before you commit, because a force that starves in the middle of a scar is exactly the force the enemy is hoping you will commit.
Failure modes, countermeasures, and mode and map adjustments
The failure modes all trace back to treating unowned land like contested land, and each has a direct counter. The tiny-nibble stall is committing below the slow ceiling (under about 330 / 400 / 500 for Plains / Highland / Mountain), pinning the annexation at the 100-floor and watching the border barely creep; the counter is to either commit past the speed floor you want or to narrow the front so the slower rate still covers the goal. The overcommit drain is sending a huge army into flat open land past the speed floor and assuming the extra troops speed the push; they do not, and the extra troops are pure per-tile fuel that could be held in reserve, so the counter is to commit to the speed floor plus just enough fuel for the depth you want, and hold the rest. The starved Mountain is taking the Plains commit count into a Mountain front and ending with no reserve and a slow frontier; the counter is to price the terrain first and either raise the commit or shorten the push. And pushing through fallout is committing a clean-land force into a scarred corridor and starving at the 3-to-5-times invoice; the counter is to route around, convert first, or size the force to the scarred cost.
The mode and map adjustments shift the numbers but not the model. Difficulty changes the bot per-tile loss: the bot attacker already pays mag/10 instead of mag/5, and a harder bot difficulty raises the bot’s troop growth and the size of the forces it commits, so the same neutral front that a lower-difficulty bot nibbles at a slow rate becomes a bot that commits past its own speed floor and sweeps fast; the practical read is that on higher difficulties you are racing a bot that expands the neutral land faster, so your own commit has to hit its speed floor sooner to keep the neutral border. Map composition shifts the whole table: a Mountain-heavy map raises every per-tile fuel and every speed-floor threshold, so the same committed force reaches less far and more slowly than on a Plains-heavy map, and the correct standing posture on a Mountain map is a higher default commit and a narrower front. The repeatable closing rule is the one every section points at: on unowned land, size the commit to hit the speed floor you want, keep enough fuel for the depth you want at this terrain’s invoice, widen the front when you are racing and narrow it when you are being raced, and price fallout as a 3-to-5-times multiplier on the whole invoice. The related guides to read next are the early expansion rhythm guide, the attack ratio guide, the annexation enclosure guide, and the no man’s land fallout guide.
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