Territory Size and Attack Speed: When a Big Empire Should Push

Direct answer. A large territory can make a land attack arrive faster, but it does not make every attack safe. In v0.34.24, owned-tile count feeds a smooth logistic bonus into the attack tick fraction; maximum Troops is a different variable. Read both territories, the active attack stack, terrain, border width, defender density, and the reserve you leave behind. Full-send only when the speed advantage buys a named objective before the opponent can answer.

The decision this page owns

The question is not “does a big country attack faster?” The useful question is “does the territory-size advantage change this particular commitment enough to justify sending more of my current army?” Those are different questions because OpenFront displays several quantities beside each other. Your Troops bar tells you current units. The bar’s endpoint is your maximum capacity. Your owned tiles determine borders, income, and one of the attack modifiers. The attack slider chooses the active stack. None of those four numbers is a substitute for another.

This distinction explains the recurring community report that two players with about 200,000 Troops can fight at visibly different speeds. One player may have a larger owned area, a wider active border, or a defender with a larger territory. Another may be attacking Mountain tiles or a dense capital while the first is crossing Plains into a thin AI nation. A spectator who sees only the country totals calls that randomness. The engine is reading a ledger the interface does not summarize in one number.

Use the territory modifier as an advantage in time, not as permission to ignore risk. A large attacker bonus reduces the tile’s tick fraction. A large defender bonus also reduces the tick fraction for an attack into that defender. Terrain tile cost, the ratio between defender Troops and the active attack stack, the defender’s Troops per tile, a Defense Post, fallout, traitor status, and the current border size still multiply or divide the result. A huge empire can therefore be fast into a mountain choke and still lose too many Troops to finish it. Conversely, a medium empire can look slow on a protected ridge but win because it preserved a counterattack reserve.

The practical decision has three outputs. First, choose whether the objective is worth a short burst: one City, a river line, a port, a trapped pocket, or a retreat route. Second, choose the smallest active stack that reaches that objective while leaving a response force. Third, choose the stop signal before you click. The territory bonus is useful when it shortens the time between commitment and the stop line. It is wasteful when it merely lets an unbounded attack run farther into a new frontier.

The rule also changes in an emergency. If an enemy has accepted a betrayal and launched a MIRV, a large territory may make your full-send land attack arrive sooner than the missile. That can be a real escape line, especially when the enemy’s target is a border that you can cross and the attack route is wide. It is not a universal MIRV counter: the missile’s flight path, SAM coverage, your target’s terrain, and whether your attack actually reaches a structure before detonation still matter. Treat the speed bonus as one clock in a race, not as an invulnerability button.

Version boundary: v0.34.24 and the closed exploit

This guide is written for the formal v0.34.24 release, published on 2026-10-06. The release’s player-facing fix closed an exploit that let players repeatedly send attacks at targets they did not border and grow past the troop cap. That detail matters because old clips and community tests may show a bar rising after invalid attacks. In the current release, a target must be a real adjacent route for the attack to do normal work; an invalid click is not a regeneration strategy and should not be used to test the territory modifier.

The territory-size calculation itself is in the v0.34.24 Config.ts attack logic. It uses a smooth logistic function of log(numTiles), with a midpoint of 300,000 owned tiles and steepness 2.5. There is no “large country” switch at one exact border. The curve is almost flat for small territories, bends around the midpoint, and approaches a floor for very large territories. The loss-side attacker depth is 0.7, so its bonus approaches 0.3 for an enormous attacker. The defender loss-side depth is 0.3, approaching 0.7. The speed-only attacker depth is 0.73, approaching 0.27. Those are component multipliers, not a promise that the whole attack is 73% faster.

The release also carries the v34 attack model: the attacker loss uses a clamped defender-to-active-stack ratio, a base term, defender Troops per tile, and both territory loss bonuses. The tick fraction uses terrain tile cost, a separate ratio speed cost, the attacker speed bonus, the defender speed-side bonus, border size, and any traitor or Defense Post effects. The same source keeps troop regeneration in a separate function. That is why maximum Troops does not directly make a tile advance faster, and why the v0.34.24 exploit fix does not change the legitimate speed formula.

Apply the version boundary when reading replays. A v0.33 or early v0.34 clip can have a different combat pace or an invalid-attack artifact. Do not calibrate a current full-send from an old video that never identifies its release. If a result seems impossible, record the tag, map, terrain overlay, active attack amount, defender tile count, and whether the target was adjacent. Those facts let you separate a version change from a missing input.

There is one more practical version check: separate a release note from an upstream main change. A commit that is visible on GitHub but not in v0.34.24 is evidence for a future build, not a current combat rule. The public release is the right boundary for a player-facing recommendation, while the tagged source is the right place to verify a coefficient. When you compare two replays, compare the release first, then the map and mode, and only then the troop totals. This prevents a clean-looking experiment from mixing a v34 clip with a main-branch behavior. It also keeps the guide honest when a later patch changes a single multiplier without changing the general SCALE method.

What the owned-tile logistic actually does

The implementation computes a bonus that starts near 1 for a small territory, decreases smoothly as owned tiles grow, and approaches a lower floor for a very large territory. Because the tick fraction is multiplied by this bonus, a smaller number means a faster capture cadence. The defender’s territory enters the same speed-side product: attacking a large defender can be faster than attacking a tiny defender, all else equal. That is counter-intuitive but deliberate. Late games need a way for a large empire to keep moving instead of turning every border into a permanent freeze.

Owned tiles	Attacker loss-side component	Attacker speed component	Defender loss-side component	Reading
50,000	about 0.99	about 0.99	about 0.99	Small territory; size barely changes the result
300,000	0.65	0.64	0.85	Midpoint; the curve is doing visible work
1,000,000	0.33	0.30	0.71	Large empire; attack time and loss base are discounted
4,194,304	about 0.30	about 0.27	about 0.70	Near the floor; further growth adds little

The table is not a replacement for a battle forecast. At 300,000 tiles, an attacker’s speed component is roughly 0.64 instead of the small-territory value near 0.99. If the defender is also at the midpoint, the two size components multiply to about 0.64 × 0.85, or 0.54, before terrain, ratio, border size, and other effects. That means the attack can consume about half the size-adjusted tick fraction of a small-versus-small comparison. It does not mean the player can send half as many Troops, because troop loss has its own density term and the active stack still determines the ratio.

Owned tiles are also not the same as map share in a simple linear sense. The function uses logarithms, so adding 50,000 tiles to a 50,000-tile country has more effect than adding 50,000 to a million-tile empire. The midpoint is a decision landmark, not a target to grind toward blindly. If gaining the next region opens a safe border and a second income route, it may be worth more than the speed multiplier. If it creates three new fronts, the territory bonus may be paying for a problem you just manufactured.

Border size is another reason screenshots mislead. The tick fraction divides by the number of tiles on the active attack front. A broad contact can advance more tiles per tick, but it also gives the attack more possible directions and can expose a longer frontier. A narrow contact can be slower per visible tile while remaining strategically safer. Always compare the route you need, not the speed of one animation segment.

Scenario one: a large attacker takes a bounded route

Assume a World-style FFA at minute thirty. You own 420,000 tiles, have 1,200,000 current Troops, and your opponent owns 80,000 tiles with 300,000 Troops spread across 150 tiles. The route to their exposed City is 24 Plains tiles followed by a short Highland edge. Your slider would send 20%, or 240,000 Troops, leaving 960,000 at home. The visible comparison says four times the army. The useful comparison says the active stack is 240,000 against a 300,000 defender, the target route changes terrain after 24 tiles, and your territory is already above the logistic midpoint.

The size read is favorable. Your attacker speed component is close to the large-territory bend, while the defender’s 80,000 tiles provide only a small defender-side discount. The route is not magically free, but the attack should reach its first stop faster than the same stack from a 50,000-tile country. That makes a bounded capture reasonable if the City removes a dangerous border or secures a rail corridor. Set the stop line at the City or the Highland edge before sending. Do not let the green attack line continue through the opponent’s core simply because the animation is moving quickly.

Now change the slider to 40%, sending 480,000 and leaving 720,000. The ratio improves, and the speed-cost term is floored closer to its overwhelming-push minimum. Your territory bonus and the ratio bonus now reinforce each other. The question is whether the extra 240,000 active Troops buys something specific. If the City is the only structure that closes the border and your other neighbor is allied, the answer may be yes. If the attack crosses the Highland edge into a Defense Post range, the answer may be no: the territory speed saving shortens the approach but does not remove the post’s loss and tile-cost multipliers.

The defender’s best counter is to let you take cheap edge land while launching a reverse attack at your thin side. Your best counter-counterplay is a reserve rule: keep enough Troops to cancel the strongest reachable attack and still hold the captured City. If that reserve falls below the rule before the route is complete, stop even if your territory advantage says the next tiles are fast. The win condition in this scenario is not “take as much as possible.” It is “use the large-territory clock to reach a named structure before the opponent can turn the new border against me.”

Scenario two: the large defender and the MIRV race

Assume you own 300,000 tiles on a compact island chain and have 700,000 Troops. A recently allied neighbor betrays you, accepts the alliance break, and launches a MIRV at a coastal City. The neighbor owns 360,000 tiles, has 500,000 Troops, and their missile route will take long enough for a land attack to matter only if you cross the shared strait quickly. You have one open Plains approach of 18 border tiles, a Mountain approach of 8 tiles, and a third player who can reach your home island if you empty it.

The size calculation tells you why the two large territories can move quickly relative to small players: both speed components are below the small-territory baseline, and the defender-side component also lowers the attack tick fraction. The route calculation still decides the race. Send against the 18-tile Plains edge only if it leads to the launcher’s City or a line that forces the MIRV owner to cancel their plan. Do not choose the eight-tile Mountain route merely because it is visually shorter; the terrain tile cost and any Defense Post can dominate the territory discount.

Suppose your normal attack sends one fifth, or 140,000. That may be too small to reach the objective before the missile, even with favorable territory size. A full send of 600,000 leaves 100,000 for the home island, which is unsafe if the third player has a direct route. A 60% send of 420,000 leaves 280,000 and improves the ratio without deleting your response. The correct choice depends on a visible deadline: the MIRV’s remaining flight, the route’s effective tick cost, and the third player’s reach. If those clocks show that 420,000 arrives before detonation and 280,000 can hold the home route, the partial send is stronger than the dramatic full send.

The MIRV race has a second trap. A fast attack can capture the launcher’s edge while the warhead is already committed. That is progress, not automatic safety. SAM range, launch timing, and the exact target may still determine the blast. If the attack cannot reach the relevant structure before the missile’s detonation, preserve the army and use the MIRV defense protocol instead. If it can, the large-territory bonus is the reason a counterattack may be worth attempting, but the reserve floor is still the reason not to send every last unit.

The defender can counter by launching from a different Silo, moving the target value, or letting you cross into a low-value edge while the MIRV hits the core. Your counter is to name the objective before the first tile moves and to stop when the objective becomes impossible. A territory bonus is strongest when it converts a known time window into a structure capture; it is weakest when it turns panic into an unbounded race.

Why the same troop total can look slow or fast

Visible current Troops are only the first line of the combat ledger. The attack engine uses the Troops in the active attack, not the number still sitting in your country. If you own 1,000,000 Troops and send 20%, the ratio sees 200,000. If another player owns 400,000 and sends 80%, the ratio sees 320,000. The second attack can be faster and cheaper even though the first country displays the larger total. This is the most common explanation for the community question “we both had 200k, why did their border disappear?”

The defender’s Troops per owned tile is separate again. A 300,000-Troop defender over 150 tiles presents 2,000 Troops per tile. The same army over 600 tiles presents 500 per tile. The density term makes the compact defender more expensive to take, while the defender’s owned-tile speed component can make the overall tick fraction smaller. Those facts are not contradictory: speed can improve while losses remain high. A player who watches only the animation sees fast movement and assumes the target is weak; a player who watches only losses sees a bad attack and assumes the speed did nothing. Both are reading one output instead of the whole ledger.

Terrain and structures can reverse the visual impression. Plains have the lowest base tile cost, Mountains the highest, and a defender-owned Defense Post multiplies the route’s loss and speed cost. Fallout changes those costs again. A large empire crossing a protected mountain can therefore look slower than a small empire crossing open plains, even when the size modifier favors the large empire. The correct comparison is the product of the inputs on the exact route, not a ranking of players by land count.

Maximum Troops and regeneration create another false explanation. A City can raise your cap; a bar near 42% of cap can refill faster than a bar near the ceiling; neither fact directly inserts a territory-size speed bonus. The v0.34.24 exploit fix is relevant here because invalid non-border attacks used to make a player think the bar, cap, and attack speed were linked through a hidden refund. They are not. Test the legitimate route with a bounded send, record the active stack, and compare the same route after the next tick window.

Finally, check border width. A wide front divides the conquest budget across more possible tiles and may show rapid movement across a broad edge. A narrow front may show fewer pixels changing while delivering the important structure. The right question is “how long to the stop line, and what reserve remains when I get there?” not “whose color is moving faster right now?”

Failure modes and opponent counterplay

The first failure is full-sending because the territory number is large. An attacker at the logistic floor can still lose to a dense defender, a Defense Post, a Mountain route, or a third-party counterattack. The fix is to treat the territory bonus as a time discount and pay the reserve cost separately. Write the reserve floor before you move. If no reserve floor exists, the attack is not a plan; it is an elimination attempt.

The second failure is chasing the midpoint. Owning 300,000 tiles makes the curve visible, but it does not make 300,000 an economic objective. A new region that adds two exposed borders can reduce your practical safety even while increasing the theoretical speed bonus. Choose land for its route, structure, income, or win threshold. The speed modifier is a supporting reason, never the only reason to annex.

The third failure is using a troop-cap upgrade as if it were a speed upgrade. Cities and completed levels can let you store more troops, and the attack slider may then send a larger active stack. That indirect effect can improve the ratio. The cap itself is not in the territory logistic. If the army remains below the cap, a City may solve storage but not the next border. Read the population growth guide before spending Gold for capacity.

The fourth failure is accepting a community percentage without checking its denominator. “142.5% faster” can mean an inverse tick-cost comparison, a single component, or a specific map-size assumption. The current source expresses the result as multipliers on a tick fraction. Use component values and compare the full product. That prevents a screenshot from turning into a promise that every full send beats every MIRV.

Opponents have clear counters. They can hold a Mountain or posted neck, spread their Troops to alter density, attack your reserve while your active stack is away, open a second route, or fire at a different high-value structure. In team games they can ask a teammate to pressure the side your speed bonus left empty. In a No Alliances lobby they can force you to price every new border yourself. In an Overtime lobby they can concede a cheap edge while racing the territory threshold elsewhere. The counter to all of these is not “send more”; it is to update the objective, route, and reserve after each board change.

Read the opponent’s response as a measurement. If they do not reinforce the route you chose, your speed advantage may be enough and the correct move is to stop at the structure rather than chase the retreat. If they shift a reserve toward your border, the original time estimate has expired even if the attack bar is still green. If they open a second front, count that front before adding troops to the first. A good counter is often a change in geometry: threaten a City from two sides, force a post to cover the wrong neck, or cancel before the defender can trade your active stack for your home reserve. The territory modifier gives you tempo; the opponent decides whether that tempo remains valuable.

Map and mode adjustments

On large World-style maps, owned-tile growth has time to reach the logistic bend, and a large empire can convert a wide, safe frontier into a real tempo advantage. The cost is that wide maps create more reachable borders. Use the threat assessment guide to identify which newly exposed edge can actually be attacked before you spend the speed dividend. A broad continent with one protected neck is a better platform for a full send than the same tile count spread across six coastlines.

Compact maps compress every clock. A 100-tile territory may not move the logistic curve much, but a short route can still make a small active attack decisive. Keep a larger immediate reserve because a neighbor’s counterattack arrives sooner. Do not import a large-map full-send threshold into Compact without recalculating the stop line.

Mountain-heavy maps reward the defender-side reading. If your large territory is behind a ridge, let the attacker pay the terrain premium and use your time to refill or build depth. If you are the attacker, compare the route around the ridge with the direct route. A faster large-territory attack on Plains can be strategically slower if it opens a coastline that a Warship can cut. The terrain systems guide gives the class table; this page tells you when the size multiplier is large enough to change the route decision.

Team games change the reserve contract. A teammate can hold a second border, but an ally’s owned-tile count does not become your attacker count, and their Defense Post does not automatically cover your tiles. Name the payer, the route owner, and the player responsible for the counterattack. If one teammate is the large attacker, their speed advantage can be the team’s breakthrough clock; the other teammates should protect the empty side rather than copy the full send.

In Overtime, territory is both a combat input and a win-condition input. A speed bonus can help you reach the crossing that puts the team over the threshold, but a long pursuit can lose the match while your army is away. In Doomsday, the deadline can justify accepting a smaller reserve, yet the mode’s drain and rot create their own clock. Read winning Overtime or the Doomsday guide before carrying a normal FFA stop rule into a special mode.

Map choice also changes how much information you can trust. On a dense map, a single visible border may hide a short boat route or an impassable cut that makes the apparent distance meaningless. On a water-heavy map, the territory bonus can make a land attack fast while the real objective still requires a transport and a naval screen. Before committing, draw the route on the actual map, count the first structure that matters, and identify the tile where a retreat remains possible. This keeps “large territory” from becoming a purely statistical claim detached from the map geometry that determines whether the fast attack can hold what it reaches.

The SCALE loop for every large attack

Use SCALE immediately before a serious send. S — Size both territories. Record your owned tiles and the defender’s owned tiles. Treat 300,000 as the point where the curve becomes visible, not as a magic threshold. If both sides are small, stop expecting size to explain the outcome. If both sides are large, expect speed to be only one part of a much faster late-game exchange.

C — Check the active stack and the route. Write current Troops, attack percentage, active attack Troops, defender Troops, defender Troops per tile, terrain for the next useful stretch, Defense Post coverage, fallout, and border size. The active stack determines the ratio; the route determines the tile cost; the territory count supplies a smooth multiplier. Missing one of these inputs is a reason to send a probe, not to increase the slider.

A — Assign a bounded objective. Name the exact City, port, river, Silo, trapped pocket, or win-threshold crossing that completes the attack. Estimate the route’s time in relation to the opponent’s next action. If the objective is only “take more land,” the attack has no evidence-based stop and should remain smaller. A large-territory bonus is most valuable when the objective is close enough for time to matter.

L — Leave a response reserve. Reserve enough Troops to cancel or absorb the strongest credible attack, protect the new border, and respond to a betrayal or nuke. A full send can be correct in a verified MIRV race or a match-ending threshold crossing. It is wrong by default. The reserve is not wasted capacity; it is the option that makes the speed advantage usable.

E — Exit when the premise changes. Stop when the route reaches the objective, terrain worsens, a post appears, a third player opens a front, the MIRV target changes, or the reserve floor is crossed. Recompute after a meaningful tick window. If the attack no longer buys the time you priced, recall it and keep the remaining army. Use near-parity combat when the ratio is close, land combat for the broader border checklist, and nuke defense protocol when the clock is nuclear.

The final rule is simple: territory size changes the price of time, not the value of judgment. A big empire should push when the discount reaches a named objective before the opponent’s answer, and should stop when the same discount merely makes an unsafe plan move faster. That is how the community’s “why are they so fast?” observation becomes a decision you can repeat rather than a mystery you explain after the replay.