Early Expansion Rhythm: How Fast to Grow Before Your First Push

The first twenty minutes of an OpenFront.io match are won or lost on one decision that almost nobody can state cleanly: how fast to expand, and exactly when to stop grabbing neutral land and start taking bots or players. This page answers it as a rhythm problem, not a list of troop counts. The core fact is that your army only grows fastest while it is somewhere between 40% and 45% of your current troop cap, and the only way to keep that number high is to keep raising the cap by claiming new tiles. So the early game is a loop: expand, watch your army settle near the growth peak, expand again. Break the loop by going idle at a fixed troop count, and you are strictly slower than a player who keeps moving. The page then walks the loop in the order you will play it: the direct answer, why the frontier move is what makes the army grow, how to read the curve, the wildlands-to-bot switch, the bot-to-player pivot, two worked scenarios, the failure modes and their counters, and finally how the tempo shifts by map and by mode. Every figure is verified against the OpenFront.io source at version v34 (commit 4e837520), so the numbers hold for the live game right now.

Three questions come back to this page from the community every single week, and they are all really the same question wearing different clothes. The first is “how fast should I be pushing in the first two minutes,” which is a tempo question and is answered by the annexation floor: once your army is large enough, a plains tile falls in five ticks, so there is no reason to stop. The second is “at what troop count do I stop expanding and go attack,” which is a misframed question, because the count is not the trigger and the cap ratio is. The third is “why does my army grow slower the bigger I get,” which is the curve doing its job and the thing this page explains before anything else. One more frame is worth setting before the sections start: the spawn you get is not a fixed starting condition but a constraint you have to read first. You start with 25,000 troops and a cap around 100,000, so you are at 25% of your cap with roughly three thousand troops per second of growth, and the spawn immunity window of about five seconds at the start is the only time in the whole opening where nobody can reach you. That window is what makes the first push free, and it is why the opening is won by whoever reads their spawn and runs the loop before a neighbor finishes reading theirs. The rest of this page assumes you can see three numbers on your screen at any moment: your current troops, your cap, and the terrain tier in front of you. If you can keep those three in view, every section below is just a rule about which of the next moves is cheapest in cap, and the whole opening stops being a sequence of guesses and becomes a single repeating check.

The direct answer: expand until your army sits at 40-45% of its cap

The single best rule for the opening is to keep your frontier moving while your own army hovers near 40% to 45% of your troop cap, and to treat that band, not a fixed number, as the trigger for your next push. You do not stop at 20,000 troops or 50,000 troops. You stop, take whatever is in front of you, and immediately look for the next stretch of neutral land or a weak bot, because every tile you add raises your cap and resets the whole curve in your favor. The reason the band matters is the growth formula. Your troops per tick are (10 plus troops to the power 0.73 divided by 4) multiplied by (1 minus troops over max). That curve peaks at 42% of your cap and then declines, so the moment your army drifts above about 50% of max, you are already growing more slowly than you were a few seconds earlier. That does not sound like much, but the early game is a race, and the player who keeps their army near the peak converts the same twenty minutes into a visibly larger force.

Two practical consequences follow. First, the number you should actually be watching in the top bar is the ratio of your troops to your cap, not the raw troop count. Two players with the same 40,000 troops can be in completely different positions if one has a 90,000 cap and the other a 120,000 cap. Second, because the cap is raised by tiles and the tiles you can raise it with are the neutral land right around you, the first target is almost always the closest unclaimed territory, not a distant bot that looks tempting on the map. The loop is: claim neutral land until your troops are near 40-45% of the new cap, take the next neutral patch, repeat. Bots enter the loop only once you have exhausted the cheap neutral land in your immediate area, and players only after you have a reason to contest them. If you can state your decision as “I am at X% of my cap and I have Y targets ahead of me,” you are playing the rhythm correctly. If your decision is “I have enough troops, I will wait,” you have already broken the loop.

The band is a range, not a point, for a reason that matters in a live match. The peak is at 42% but the curve is flat for a good distance around it, so you do not need to micro-time the exact moment you hit 42%; you need to keep your army somewhere between about 40% and 45% and let the next target come to you. That is why the rule is phrased as a band: at 40% you are still on the way up and there is no penalty to taking one more neutral patch, and at 45% you are just past the peak and the next patch will drop you back down toward the top of the curve. The failure is not overshooting the band by a few percent; the failure is letting the band sit idle while the ratio climbs past 60% because there was “nothing to do.” If the map gives you nothing to do at 45%, that is a map and mode question covered near the end of the page, not a reason to stop the loop.

Why keeping the frontier moving makes your army grow faster

The counterintuitive part of the early game is that the way to build a bigger army is to keep spending it on neutral land. The growth formula rewards a large gap between your current troops and your cap, and it punishes a small gap. At a 100,000 cap, the curve produces roughly 349 troops per tick at 40% of cap, about the same 348 at 45%, but only 342 at 50%, 192 at 80%, and 104 at 90%. A player who idles at 90,000 troops against a 100,000 cap is adding about 1,000 troops per second, while the same army at 40,000 against the same cap is adding about 3,500 per second. The difference is not a small efficiency gain; it is three to five times the growth rate.

The cap itself is raised by tiles in a sub-linear way: the base is 2 times (tiles to the power 0.6 times 1000 plus 50,000). That has two effects on the early game. First, the very first tiles are extraordinarily cheap in cap terms, because the base already carries a 50,000 floor before any territory, so your first hundred tiles push you from a 100,000-scale cap to a 130,000-scale cap quickly and that is where your growth is fastest. Second, the sub-linear exponent means each additional ring of land gives you a smaller cap jump than the previous ring, so there is a point where a long thin push into distant territory stops being worth it compared with a compact push that fills the space beside your core. The frontier-moving rule is really two rules in one: keep the gap between troops and cap near the 42% peak, and prefer the compact, cheap tiles that keep the gap there over the expensive distant tiles that do not. When a player tells you “I just keep pushing and my army keeps getting bigger,” that is the formula doing its job, not luck. The moment the push stops, the gap collapses toward zero, the formula output collapses, and the same army that was growing at 3,500 per second is now growing at a few hundred. The rhythm is the engine.

There is a second, less obvious reason the frontier move wins, and it is about what you are spending. Every neutral tile you annex costs you a few ticks of your army, not a chunk of it, and on plains that cost is so small that the cap you gain is almost free compared with the troops you would be idling anyway. So the expansion is not a trade between “grow” and “take land” the way a fixed-count player imagines it; it is a trade that is almost free. The troops you “spend” annexing a ring of neutral land are the troops that would have been sitting at 60% of your cap growing at three thousand per second, and by the time the ring is done you have more total troops than you would have by idling, because the cap you added is now doing the work. The one exception is terrain: a mountain ring costs you more ticks per tile than a plains ring, so the same “almost free” logic weakens as the terrain gets steeper, and that is exactly why the compact rule says take the cheap tiles beside your core first and leave the distant steep tiles for later when your army is big enough to make the cost matter less. Read the frontier, spend the almost-free tiles, and the army grows for you.

Reading the growth curve: the 42% peak and the saturation cliff

The growth curve is the single most important number to internalize because it tells you when your current army is doing the most work it can do. The formula is (10 plus troops to the power 0.73 divided by 4) multiplied by (1 minus troops over max). The first term, the 10 plus the 0.73 power, grows slowly as your army gets bigger; it is your base reproduction. The second term, the 1 minus troops over max, is the brake, and it is the one that drives the early game. As your troops approach your cap, that second term approaches zero and the whole product slides down.

The peak of that product is at 42% of the cap. Worked at a 100,000 cap: at 20% you are adding about 2,840 troops per second, at 40% about 3,490, at 45% about 3,480, at 50% about 3,420, at 60% about 3,120, at 80% about 1,920, and at 90% about 1,040. The numbers tell a story. From 20% to 40% you are gaining the most per tile of land you could spend, so that is the band to live in. From 45% to 60% you are still near the top, so it is fine to let your army settle there while a push finishes. Above 70% you are in the saturation zone and every second of idling costs you more troops than a player who just pushed through. The table below is that same 100,000 cap read as a position, and the column on the right is the decision it maps to.

Troops (of 100k cap)	Ratio	Troops per second	What the curve tells you
20,000	20%	~2,840	Unused capacity; spend on neutral land now
40,000	40%	~3,490	Near the peak; take what is in front of you
45,000	45%	~3,480	Still at the top; let a push finish
50,000	50%	~3,420	Just past the peak; keep the frontier moving
60,000	60%	~3,120	Decelerating; a slow idle now is a real cost
80,000	80%	~1,920	Saturation zone; you are losing the race
90,000	90%	~1,040	Nearly flat; the next push is mandatory

The practical read is: if your ratio is under 30%, you should be spending on neutral land right now, you have unused growth capacity. If it is between 40% and 50%, you are at the peak and should be taking whatever is in front of you. If it is above 70%, you are idle and a neighbor is about to outgrow you. The curve also tells you why “wait to 50,000 troops” is the wrong way to phrase the decision, because 50,000 is a number, not a position on the curve, and the same 50,000 against a 120,000 cap and a 90,000 cap is two completely different growth rates. The population growth guide covers the cap formula and the city bonus in detail, and the attack ratio guide covers how much of that army a single push should spend; this page is the loop that ties the two together. Train yourself to read the ratio and the curve, and the tempo decisions stop being guesses.

From wildlands to bots: the first switch and the land-grab threshold

The first switch is from neutral land to bots, and the threshold is not a troop count but a scarcity signal. While there is unclaimed land in your immediate ring, you want to take it, because neutral tiles are the cheapest cap you will ever get and the annexation cost against empty land is tiny. The cost to annex a neutral tile is clamped between 5 and 100 ticks, computed as 2000 times the tile cost divided by your attack, and on plains the tile cost is 16.5. With a human attack of troops divided by 5, that means a 10,000-troop army annexes a plains tile in about 16.5 ticks, a 20,000 army in about 8 ticks, and by the time you are near 40,000 you are at the 5-tick floor, which is as fast as the game allows. So the land-grab threshold is: keep taking neutral land until the frontier around you is empty, which on most maps means a few compact rings of your core.

Bots enter next because they are the cheapest defended target you can fight. A bot starts with 10,000 troops and grows at half the rate of a human, so a bot you first meet in the opening is almost always weaker than you if you have been running the rhythm. The switch to bots is when the neutral land is gone and the weakest bot is closer than the next patch of unclaimed territory somewhere else. Take the weakest bot, not the one with the most gold, because you are buying cap and a position, not gold, at this stage. A bot you clear gives you its tiles, which raise your cap, and it removes a future threat that would have been growing in your periphery. The land-grab threshold, stated as a decision: take neutral land while it is free, take the weakest adjacent bot when the neutral land runs out, and only turn on a player when you have a concrete reason to contest them. If a player is actively pushing into the neutral land you want, the reason exists and you switch early; if a player is far from your border, the reason does not exist and you keep running the wildlands-to-bot loop. The threshold is a scarcity and threat signal, and it is the thing that separates a tempo player from one who is stuck choosing a number.

When to turn on players: the pivot that ends the opening

The pivot to players is the moment the opening becomes a midgame, and it has three triggers you should check in order. The first is a neighbor who is pushing into territory you want: the moment an unclaimed patch you are about to take is inside their reach, you take it first or you contest them, because the neutral land is the cheapest cap and letting a neighbor take it gives them the cap you were going to have. The second is a player whose army is visibly smaller than yours on the cap ratio, which is the moment you can take a border and keep it, because a player defense scales with their army and a small player simply cannot hold a contested edge against you. The third is a player who has stopped expanding and is sitting idle, which is the tell that their growth rate has collapsed to the saturation zone and you are now out-growing them by a wide margin.

What you should not use as a trigger is a fixed troop count or a fixed time. “I will go aggressive at 50,000” and “I will push at the five minute mark” both ignore the fact that the cap ratio, not the count, is what decides whether a border can be taken and kept. A 50,000 army against a 120,000 cap is at 42% and still growing fast; the same 50,000 against a 70,000 cap is at 71% and already in saturation. The correct pivot is to read each border as a ratio and take the ones where your cap is comfortably larger than the defender’s, keep the ones where it is close, and leave alone the ones where the defender is still out-growing you. The pivot also has a cost side: a player border you take is a long-term commitment, not a one-tile annexation, because a player will reinforce it and contest it back. So the pivot is not “take the weakest player” but “take the border where my cap advantage is large enough that the cost of holding it is worth the cap and the position I gain.” When you can name the border you are taking and the cap ratio that makes it winnable, the pivot is a decision. When you cannot, you are guessing, and the guess usually loses the opening.

There is a sequencing detail that makes the pivot stick: take the border, then immediately re-run the loop on the other side of it. The moment a player border flips to you, you have new neutral land on the far side and a new weakest bot or weakest player in range, so the opening does not end at the pivot, it continues through it. A player who takes a border and then idles to “hold” it has turned a tempo win into a static one, and the defender starts re-closing the gap at their own growth rate. The correct read of a successful pivot is that you have just bought a new ring of the same loop, so you keep the ratio near the peak by spending on the new neutral land, which is also the cheapest way to make the border you just took unbreakable, because a thick buffer of your own tiles in front of a contested edge is the one thing a player cannot contest back cheaply. The pivot, then, is not a switch from “expansion mode” to “war mode”; it is the loop with the target list changed from neutral land and bots to the weakest player border, and the same ratio rule that told you when to take the bot is the rule that tells you when to take the player and when to stop and re-expand. That is the whole opening in one sentence: keep the ratio near the peak, take the cheapest cap in front of you, and when the cheapest cap is a player, you have pivoted.

Scenario: a compact plains core with three neighbors

Scenario A is a compact spawn on plains with three neighbors and a ring of neutral land between you and all three of them. You start with 25,000 troops and a cap of roughly 100,000, so your starting ratio is 25% and your growth is fast, about 3,300 troops per second at the 25% point of a 100,000 cap. The rhythm here is to take the full neutral ring first, because it is the cheapest cap and it is the buffer that keeps your three neighbors from reaching you early. At a 25,000 army your annexation is slow, about 16 ticks per plains tile, so you let your army build while you take the ring, and by the time the ring is done your army is near 40,000 and your annexation is at the 5-tick floor. Now the neutral land is gone and the three neighbors are the targets. One of them is a bot that started with 10,000 and has been growing at half your rate, so at this point the bot is around 30,000 and you are around 45,000, which is a clean ratio in your favor. You take the bot first because it is the cheapest defended target and it raises your cap. The two human neighbors are still far behind your ratio, so you hold the border against them, keep expanding into the next neutral patch on your other side, and only turn on the human neighbor who has started pushing into your buffer. The assumptions that make this work are that the spawn was compact, the neutral ring was reachable before the neighbors, and the bot was weaker than you because of the half-rate growth. If any of those are false, the order changes, and the section on failure modes covers the cases where the buffer was too thin or the bot was too strong.

The number that decides whether this scenario is a win is the size of the neutral ring. If the ring is wide enough that you can take it and still be near 40-45% of a freshly raised cap when you turn on the bot, the bot is a free win and the whole sequence is automatic. If the ring is thin, the bot you meet at 45,000 may be closer to 40,000 than 30,000, and the clean ratio in your favor has narrowed to a coin-flip, which is the failure mode the next section names. The compact spawn is the other half of the win: because your core is compact, the cap you gain from the ring is cheap per tile, so your cap is higher than a sprawling spawn of the same tile count, and that higher cap is what keeps your growth at the peak for longer. Read the ring before you commit to the bot, and the scenario is a decision rather than a gamble.

Scenario: an island spawn with no neutral ring

Scenario B is the same player on an island spawn with almost no neutral land around you, a bot to the north and a human to the south, and a coastline on the west. The opening rhythm here is fundamentally different because you cannot run the wildlands loop at all, there is no neutral ring to take. Your starting ratio is still 25% and your growth is still fast, but you have nothing to spend it on except the bot and the human, so the pivot to defended targets comes almost immediately. The decision is which one to take first, and the answer is the bot, because the bot is at half growth rate and the human is at full rate, so the gap between you and the bot closes the fastest while the gap between you and the human widens against you. You take the bot as soon as your army is near 40,000, which on this spawn is only a few seconds of growth, and you use the bot’s tiles to raise your cap before the human arrives at your southern border. The coastline changes the cost: the sea tiles are not annexable, so your effective cap is lower than a plains spawn of the same size, which means your absolute growth is slower and the window to take the bot is shorter. The assumption that makes this work is that the bot is weak enough to clear before the human gets there. If the human spawned close to your southern border and is pushing hard, the window is too short and you have to take a defensive posture against the human and let the bot sit, which is a losing position in the opening. The island case is the clearest demonstration that the rhythm is driven by the neutral land around you, not by a fixed timer or count, and it is the case where a player who waits for a number will lose to a player who reads the frontier.

Two reads separate the island win from the island loss. The first is the timing of the bot push, which has to land before the human’s army crosses the southern border, and because the human is at full growth rate the human’s arrival is earlier than a naive “the human is far away” estimate. The second is the coastline, which lowers your cap and therefore lowers your absolute growth, so the same “wait to 40,000” that is a quick win on a plains island is a slow loss here because your cap is smaller and your 40,000 is a higher percentage of it. On an island you do not get the wildlands loop, so the bot is your neutral land, and the bot push is the first and most important move of the whole opening. The player who treats the island as “no neutral land, so I just wait” has no loop at all and is the exact case the rhythm rule exists to catch.

Failure modes and the counters to them

The most common failure is going idle at a fixed troop count, which is the “I will wait until 50,000 and then act” pattern. The counter is to watch the ratio, not the count, and to keep spending on neutral land as long as the ratio is under 60%. At a 100,000 cap, 50,000 is 50% and you are already below the 42% peak, so idling there is strictly worse than taking the next patch of neutral land, which would have raised your cap to 110,000 and put your same 50,000 army at 45% with a higher absolute growth. The second failure is over-expanding into distant territory and thinning your border, which is the “push a long finger across the map” pattern. The counter is the compact rule: take the tiles beside your core first, because the sub-linear cap formula means the first rings are the cheapest cap and the distant finger is the most expensive, and a thin border is a border a neighbor can break through cheaply. The third failure is taking a bot that is too strong, which happens when a bot has been sitting near your spawn growing at half rate and you are late to meet it. The counter is to read the bot’s army against yours before the push, and if the bot is near your ratio you skip it and take neutral land elsewhere until the gap reopens. The fourth failure is pivoting to a player too early, before you have a cap advantage, which is the “attack the player who is already big” pattern. The counter is the ratio rule from the pivot section: only take the border where your cap is comfortably larger. The fifth failure is ignoring the terrain, which is pushing a mountain border at a time when a plains border would have been free. The counter is to check the terrain tier before every push, because the tile cost is higher on highlands and mountains and the same army annexes slower. Every one of these failures is a failure of reading the frontier, not of a bad troop count, and the counter to all of them is the same: keep the ratio near the peak and take the cheapest cap in front of you.

Two more failures that are easy to miss in a fast opening. The first is mistaking your own speed for the enemy’s, which is reading your army at 45,000 and assuming the neighbor is at 30,000 because the neighbor’s border looks quiet. A quiet border is not a small army, and the neighbor may have been spending on cap all along and be at 45,000 itself, in which case your 45,000 is a tie and the push is a coin-flip, not the win you planned. The counter is to estimate the neighbor’s cap, not its border, by looking at the tiles it has claimed and running the cap formula in your head, which is fast once you have done it a few times. The second is the reverse failure, which is over-reading the frontier and freezing, because the map has three neighbors and you do not know which one to take first, so you wait. The counter to that one is the cheapest-target rule, which is to take the weakest defended target and raise your cap, because any target you take raises your cap and the next decision is then made from a stronger position, so freezing to avoid a wrong first target is always worse than any wrong first target. The two failures are the same shape, a failure to act on the frontier, and the two counters are the same shape, an act that raises your cap.

How the rhythm changes by map and mode

The rhythm is the same on every map, but the tempo at which you run it changes with the terrain density and the mode. On a map with lots of plains, like the green-heavy side of the world map, your annexation is fast and your cap rises quickly, so the whole opening compresses and you are taking your first bot earlier than you would on a mountainous map. On a mountainous map, the tile cost is higher and your annexation is slower, so the neutral ring takes longer and the pivot to bots is delayed, which gives the bots more time to grow and narrows your window. The practical read is that on a fast map you should be at the bot by the two-minute mark and on a slow map you might still be in the neutral ring at four minutes, and if you are not at the bot on a fast map by three minutes you have likely gone idle. The map also decides your starting ratio’s value, because a fast map raises your cap quickly so the same 40% is reached sooner, and a slow map keeps your cap low so the same 40% holds for more seconds, which is why the timing read has to be per-map rather than a single fixed minute.

In team modes the rhythm is the same for your individual expansion, but the pivot to players is replaced by a pivot to the allied border, which means you take the neutral land and the weak bots and hold the shared edge against the enemy team rather than contesting a solo player. The compact rule is even more important in team modes, because a thin border that you push far across the map is a border your ally cannot cover and the enemy team can cut through, so the compact core and the cheap first rings are what keep the shared edge defensible. In human-versus-nation modes the rhythm is the same but the bot is replaced by the nation, and the nation starts at 18,750 on medium difficulty and grows at the full human rate, so the nation is a harder target than a bot and the pivot to it should come later, only after you have a clear cap advantage, because the nation’s full-rate growth means the gap between you and it does not close the way the gap to a half-rate bot does. In FFA the rhythm is exactly the solo case, and the pivot to players is the most common decision of the game, so the ratio rule from the pivot section is the most important number you will use. The mode changes the target, the terrain changes the tempo, and the ratio stays the same, which is why the rhythm is a rule you can apply anywhere in the game, not a list of numbers you have to memorize per map, and the only thing you have to re-learn per situation is which target is cheapest and where the shared or contested edge actually sits.