OpenFront v0.35.0 Small-Economy Spawn Boost: How Many Ports to Rush in the First Three Minutes

Direct answer: build your second port while the boost is still near peak, and treat the Factory as a later, separate decision

The single most useful reframe of v0.35.0 is that your early-economy speed is no longer a property of the lobby — it is a property of your own port and factory level count. The release replaced the v34 fleet-size boost, which depended on how many trade ships existed on the map as a whole, with a per-player small-economy boost that multiplies your personal trade-ship and train spawn rate based on how many total port and factory levels you have built yourself. The multiplier is 1.5x at exactly one total level, then decays linearly and hits exactly 1.0x (no boost) the moment you reach six total levels. Because the per-level multiplier falls with every level you add, the boost is strongest while you are still a small economy — which in practice means the first two or three minutes of the match — and it doubles as a comeback tool the moment you are knocked back to a small level count after a loss, because the count is recalculated from whatever is standing at that moment, not from your peak.

That produces a specific, non-obvious tension you have to manage on the second and third decision of the game. Building more ports is additive and net-positive — the source doc comment is explicit that “total spawns still rise with every level built” — but each additional level also lowers the per-level multiplier, so the boost that made your first port worth 2.25x is what makes your second port worth only 1.44x in ship terms. The decision the boost forces on you is therefore not “when do I build ports” in general; it is “is my next 125,000-gold spend a port that the still-strong boost is amplifying, or is it a troop or land answer I cannot delay?” If you take one action from this page, make it this: the second port is the highest-leverage 125,000-gold purchase of the opening while you are at level 1 or 2, and the boost is the reason. The anti-pattern to avoid is building a second port purely because the first one is sitting idle — if you cannot feed a second port with a safe route and expanding land, the 125,000 gold is better held as a buffer or spent on troops, and the boost’s peak window is not a reason to build an unproductive port. Every number on this page is read from the v0.35.2 tag source, not from a patch-notes summary, and the version boundary section below states exactly what changed and what did not so you can apply the same logic to any v0.35.x sub-version.

Version boundary: what exactly changed in v0.35.0, and what did not

The v0.35.0 release notes (GitHub Release, non-prerelease, 2026-10-11, tag v0.35.0) state, in their “Meta Changes” section, that “trade ships and trains spawn faster in the early game” and that “the boost fades once you have several ports or factories, so the late game is unchanged.” The source at tag v0.35.2 confirms both clauses and adds the precision the release notes leave out: the boost is keyed on a per-player level count — playerPortLevels for the trade-ship path, numPlayerFactoryLevels for the train path — not on game time and not on the world fleet, so the same boost applies in a two-player lobby and a twenty-player lobby. The v34.25 release notes described the old boost as having “kept small lobbies boosted all game,” and the v0.35.0 notes explicitly frame the new mechanic as a replacement for that, which is the clearest statement of the design intent: the boost should be a window you collect early and lose as you grow, not a permanent small-lobby tax on your opponents.

What did not change in v0.35.0: the base spawn-rate formula shape (a rejection-modifier times a base divided by a boost-adjusted saturation for ships; a level-driven rate for trains), the Port and Factory purchase price (both remain 125,000 gold), and the trade-ship and train gold payout curves. The only change to the spawn math between the v34.25 baseline and v0.35.2 is the boost term itself. Concretely, the v34.25 boost was a function of the total number of trade ships on the map — it was shared across the lobby and diluted by other players’ economies, and the pity timer cancelled most of it, which is why the release notes describe it as having “kept small lobbies boosted all game.” In v0.35.0 the function became smallEconomySpawnBoost(levels) = 1 + (0.5 * within((6 - levels) / 5, 0, 1)) / levels, where within(v, 0, 1) clamps v into [0, 1] and levels is your own total port levels (for ships) or total factory levels (for trains). The release notes’ “the late game is unchanged” corresponds exactly to the formula hitting 1.0 at levels >= 6: from six levels onward the boost is a no-op and the spawn math is identical to a no-boost baseline. Hold that boundary in your head while reading the rest: every multiplier below is per-player, level-keyed, ship-or-train-specific, and exactly 1.0 the instant you cross six total levels. This boundary also means the mechanic has a clean, verifiable end state — if you build six levels, the code path is provably identical to a build with the boost function removed — which makes it easy to test your own play against the no-boost baseline and confirm you are not over-weighting the boost past level 6.

The exact multiplier at every level, and why ships get the boost squared

The full decay curve, computed directly from smallEconomySpawnBoost at tag v0.35.2:

Total levels	Raw boost	Trade-ship effective (boost squared)	Train effective (boost, not squared)
0 (no ports/factories)	1.0000	1.0000	1.0000
1	1.5000	2.2500	1.5000
2	1.2000	1.4400	1.2000
3	1.1000	1.2100	1.1000
4	1.0500	1.1025	1.0500
5	1.0200	1.0404	1.0200
6+	1.0000	1.0000	1.0000

Two rows of this table carry the whole decision. First, the jump from level 1 to level 2 costs you 0.81 in ship terms (from 2.25 down to 1.44) — the single largest drop in the curve — which is why the second port is the one the boost is amplifying hardest relative to what you give up. Second, by level 5 the ship multiplier is already down to 1.0404 and the train to 1.02, so the “boost” you are actually collecting by level 4 or 5 is a rounding error; the mechanic has effectively ended even though you have not formally reached six, and the practical end of the window is level 4 or 5, not level 6.

The asymmetry between the ship column and the train column is the part easiest to misread, and it is stated in the source’s own doc comment rather than left implicit: “The pity timer square-roots odds changes, so squaring the boost makes it the realized ship multiplier (1 port level: one every ~8s, not ~12s).” In plain terms, the trade-ship spawn path applies the boost twice — once as the multiplier and once because the pity-timer’s internal rejection modifier is applied to a base that has already been divided by the boost — so a 1.5x raw boost becomes a 2.25x realized ship spawn rate, while a train’s 1.5x raw boost stays a 1.5x realized train spawn rate. The base ship spawn rate in the code is expressed as 100 / boost^2 in the rejection-modifier’s denominator, which is why the table above shows the boost squared in the ship column: at level 1 the base is 100 / 2.25 ≈ 44.4 rejection ticks between spawns, versus 100 at no-boost, a 2.25x acceleration. This is why the practical advice on this page leans on ports, not factories, for the opening: at level 1 the second port you build is worth 2.25x your current trade-ship pace, but the second factory you build in the same turn is worth only 1.5x your current train pace, and trains are a slower, later-game gold source to begin with (see the Port versus Factory page for the full payback math on that difference). The squared-ship / linear-train split is also why the boost’s value is front-loaded even more than the raw multiplier table suggests: the ship benefit of the second port is 0.81x your current pace, while the train benefit of the second factory is only 0.30x, and that gap is the single largest single-number reason to sequence ports before factories in the opening.

Decision framework: what your current level count should do on this turn

Turn the table above into a turn-by-turn rule:

Your current total port levels (factory levels for the train path)	What the math says about this turn	The action the math supports
0 (no ports yet)	You are about to enter the highest-multiplier window of the game	Build your first port now; the moment it finishes, your trade ships spawn at up to 2.25x the no-boost pace
1	You are running at 2.25x ship / 1.5x train; the next level drops you to 1.44x / 1.20x	The highest-leverage second purchase of the opening; if you have 125,000 gold, build the second port before anything that is not a direct combat answer
2	You are at 1.44x / 1.20x; the next level drops you to 1.21x / 1.10x	Still net-positive, but the marginal ship gain (0.23) is now less than a third of what the second level gave you; if you are behind on troops or land, the third port can wait one turn
3 to 5	The realized ship multiplier is 1.21x or lower and the train is 1.10x or lower	The boost is active but no longer the dominant driver; use normal trade-vs-land-vs-troop prioritization and let the Port versus Factory framework set the order
6+	The boost is exactly 1.0; spawn math is identical to a no-boost baseline	Stop treating the boost as a factor; your port count is now a pure income question, not a spawn-rate question

Two things about this table are easy to miss. First, the level count is your own total across all your ports (and, for the train path, all your factories) — not a per-port count, and not reset by the map. If you build a second port, lose both ports to an attack, and rebuild them, your boost level count is recalculated from whatever is standing at that moment, which means a rebuild after a loss can hand back a chunk of the boost you had already faded out of. This is the comeback property the release notes allude to when they say the boost is a “small-economy” mechanic: the moment you are knocked back to a small level count, the multiplier jumps back toward 1.5x, and your economy recovers faster than a no-boost player in the same position. Second, the count is the sum of levels, not the count of buildings: a level-2 port counts as 2 toward the boost, so upgrading an existing port from level 1 to level 2 moves you from the level-1 row to the level-2 row without spending gold on a brand-new structure. That means the cheapest way to leave the peak-multiplier window is often to upgrade an existing port rather than build a new one, and the cheapest way to stay in a high-multiplier window after a loss is to rebuild the structure you already had. The decision framework is therefore not “how many ports do I have” but “what is my total port level count right now, and is the next 125,000-gold spend a level increment that the boost is still amplifying, or is it a land or troop answer I cannot defer?” If you can answer that in under ten seconds, you are applying the framework correctly.

Scenario 1 (numeric): second port at 90 seconds versus at 4 minutes

Assume a standard opening: you take your first land by 30 seconds, build your first port by 60 seconds (125,000 gold), and face a second-port decision at 90 seconds against the same 125,000-gold decision at 4 minutes. You are at level 1 from 60 seconds, and you are collecting trade ships at the level-1 pace (2.25x the no-boost ship rate) for as long as you stay at level 1. The key insight is that both orderings end at the same level count — two total levels — so the total spawn-rate math is identical at the end; the only difference is when you get the second port’s own income, and the boost’s job is to make that head start worth more than it would be without the boost.

Ordering A (second port at 90 seconds): you collect at 2.25x from 60s to 90s, then at the level-2 pace (1.44x) from 90s onward. Ordering B (second port at 4 minutes): you collect at 2.25x from 60s to 4 minutes, then at 1.44x. Over the 90s-to-4-minute window, Ordering B collects at 2.25x and Ordering A collects at 1.44x, so the raw collection delta over that window is a 0.81x shortfall in A’s favor — A gives up collection rate by dropping to 1.44x early. But that is exactly the cost of moving to the next level, and it is the same cost either ordering eventually pays; the only real difference between the two orderings is when you get the second port’s own income. Ordering A’s second port is standing and contributing gold 3 minutes and 10 seconds earlier than Ordering B’s. Because total spawns rise with every level built (the additive property), that 190-second head start on a full second income source is worth more than the 0.81x rate differential over the same window, which is why the early second port wins in the standard, uncontested opening. The gold math: a trade ship at level 1 pays its base route value, and the second port opens a second, independent route that contributes its own full route value for 190 seconds more than Ordering B — so the head start is not just a rate differential but a full second income stream running 190 seconds longer. The one case where it does not: if your 125,000 at 90s is actually a combat or land answer (an incoming attack, a land you must hold), the deferred port wins, because a lost port or land is worth far more than 190 seconds of second-port income. The boost’s job is to make the defensible early second port strictly better, not to tell you to build into an attack.

Scenario 2 (numeric): a contested 3-port race, and why the third port is a different decision from the second

Now a faster, contested opening: you and one opponent are both at two total port levels and racing toward three by the 5-minute mark. Is the third port worth 125,000 gold versus holding that gold as a buffer against the opponent’s next attack?

Going from level 2 to level 3 drops the realized ship multiplier from 1.44x to 1.21x — a 0.23x loss in spawn rate — while the third port itself starts contributing income immediately. Unlike Scenario 1 there is no clean structural argument, because the 0.23x loss is a permanent rate change (it does not recover if you wait) while the 125,000-gold buffer is a conditional asset that pays off only if the opponent actually attacks before you would have built the port anyway. The decision the boost forces at this level count is: do you believe the opponent’s next attack is likely to arrive before you would have spent the 125,000? If yes, and that attack would cost you more than 125,000 in lost gold or land, the buffer wins and you skip the third port for now. If no — the opponent is focused elsewhere and your next 125,000 is not a combat decision — the third port wins, because a permanent 0.23x spawn-rate gain for the rest of the match is a larger gold delta than a buffer that never gets deployed. The 0.23x loss is small in absolute terms — it is less than the level-2-to-level-3 drop in the raw multiplier table — but it is permanent, so over a 20-minute match it compounds into a meaningful gold deficit against a player who built the third port at the same level count.

One detail changes the third-port math on contested maps specifically: the boost is keyed on your own level count and is completely blind to what your opponent is doing, so a contest does not reduce your boost the way it reduces your land-capture odds. Two players can both be at level 2 in the same lobby and both get exactly the 1.44x ship rate; the contest decides who holds the land, not who gets the spawn multiplier. This is a direct departure from the v34.25 mechanic, where the boost was keyed on the global trade-ship count and was shared and diluted by other players’ economies. If you are losing land to a strong opponent, your v0.35.0 boost is still doing its full per-player work even while your land position deteriorates — only the land-capture side is being penalized by the contest, not the spawn-rate side — which means the third port is more worth building in a contested game than a relaxed one, because the contest is not eating the exact mechanic that makes the third port’s 125,000 worth spending. The one exception: if the contest is so one-sided that you are losing land faster than you can recapture it, the buffer wins regardless of the boost, because a player who is losing land is not going to collect the trade-ship spawn rate the boost gives them anyway — the base rate is being interrupted by the contest, and the multiplier on an interrupted base rate is worth less than it appears in the table.

Failure modes: when the boost pays you nothing, and the counter for each

The boost is a multiplier on a base rate, not a flat gold addition, so every failure mode below is a case where the base rate you are multiplying is too small for the multiplier to matter. The table below summarizes the four failure modes and their counters; the paragraphs that follow each work through the reasoning.

Failure mode	Why the boost pays nothing	Counter
Port with no safe route	The boost multiplies spawn rate, not route safety; extra ships are intercepted	Check the route’s both-ends-enemy status before building the second port
Ports built but land not expanded	The boost multiplies spawn rate, not gold-per-ship; short routes pay little	Pair the second port with at least one land expansion in the same window
Boost window spent on a port instead of troops	The boost is doing its job; the mistake is spending the gold on the wrong thing	If the next 125,000 is a combat decision, the port loses to troops
Still “using the boost” at level 5+	The multiplier is 1.04x or lower; the mechanic has faded	Switch to plain income/land/troops prioritization at level 5

Failure mode 1: you have a port but no open, safe trade route. The boost multiplies your trade-ship spawn rate, but a spawned ship is only worth gold if it can complete a route. If your only port sits on a coast you cannot defend, or your route crosses open water an opponent’s warship can intercept, the extra ships the boost gives you are simply more ships you lose or more ships that never finish a payout. The community’s working model for when a route is safe is the capture rule: a trade ship is pillageable only if both its origin and its destination belong to an enemy (see the Capturing trade ships discussion for the exact condition). If at least one end of your route is your own or allied land, it is not pillageable and the boost is safe to collect in full; if both ends are enemy-controlled, the boost is multiplying a base rate an opponent is actively intercepting. The counter is trivial and often skipped: before you build your second port, confirm the route you will feed it is not both-ends-enemy, and if it is, either hold the 125,000 until the land is yours or take a warship to the route first.

Failure mode 2: you are building ports but not upgrading land, so your per-ship value is not growing. The boost multiplies spawn rate, not gold-per-ship; the per-ship value of a route is set by the route’s endpoints and their city counts. If you are at level 2 on ports but your home land is still at its opening size, your routes are short and low-value, and 2.25x of a small number is still a small number. The counter is the standard one: pair the second port with at least one land expansion in the same 90-second window, because the port’s value scales with the routes it feeds, not just with the boost.

Failure mode 3: you are behind on troops and you spend the boost window’s gold on a port instead of a defense. This is the only failure mode where the boost is not the problem — the boost is doing exactly what it should, and the mistake is that you spent the gold the boost made available on the wrong thing. If an opponent is at 80% of your land count and you spend 125,000 on a third port while your troop line is underfunded, the 1.21x ship rate you get from that third port is irrelevant to whether you are about to lose the game. The counter is the Scenario 2 rule applied to troops: if the next 125,000 is a combat decision, the port loses and the troops win, boost or no boost.

Failure mode 4: you are at level 5 or higher and you are still trying to “use the boost.” By level 5 the ship multiplier is 1.0404 and the train is 1.02 — a rounding error — and at level 6 and beyond the boost is exactly 1.0. If you are planning your economy as if a spawn-rate multiplier is still active, you are optimizing against a mechanic that has already faded. The counter is to treat level 5 as the practical end of the window (and level 6 as the hard line in the math): below it, the table is the decision driver; at and above it, switch to plain income-versus-land-versus-troops prioritization and stop consulting the boost table.

Mode and map adjustments: where the second-port rush is strongest and where it is weakest

The boost is lobby-size-blind by design — the same 1.5x at level 1 applies in a 2-player lobby and a 20-player lobby — but the value of the second port’s head start varies with the map and mode, because the head start is worth more when the routes it feeds are worth more.

On island maps with a single shared open-water choke point, the second port’s route safety is the binding constraint, not its gold value: the boost is doing its full 2.25x work for you, but if the only viable route crosses a choke point an opponent can hold with one warship, the extra ships are interceptable and the boost is multiplying a base rate you are not actually collecting. On these maps the Failure mode 1 counter (check the route’s both-ends-enemy status before building) is the single most important step in the entire opening, and the second port should be delayed one turn specifically if the route is both-ends-enemy and you do not yet have a warship to screen it. The one adjustment specific to island maps: because the choke point is shared, your opponent’s second port is worth the same head start to them as yours is to you, so the race to the choke point is symmetric and the player who takes the warship first has the route for the rest of the match — the boost does not change this symmetry, it only makes the gold you collect while you hold the route more valuable.

On maps with multiple independent coastlines and no single choke point, the second port’s route safety is less of a constraint and its gold head start is the binding value: you can open a second, independent route that does not share the first port’s choke point, and the 190-second head start from Scenario 1 applies in full. On these maps the second port at 90 seconds is the strongest version of the play, and the third port’s contested-race calculation from Scenario 2 is the next decision, run with the same “is the next 125,000 a combat decision?” test. The one adjustment specific to multi-coastline maps: because the routes are independent, the second port’s head start is not limited by the first port’s route value, and the 0.81x rate differential from Scenario 1 is the only cost — so the early second port is strictly better on these maps than on single-choke-point maps, and the boost’s value is maximized here.

In team modes the boost is still strictly per-player — your team’s other members’ ports do not contribute to your level count and your ports do not contribute to theirs — so the second-port rush is the same per-player decision it is in solo, and the team’s shared land position does not change your boost table. The one team-specific adjustment: if your team already has a member at level 3 or higher, the team’s combined economy is already past the peak of the boost curve, and the marginal value of your own second port is lower in team terms than in solo terms, because the team’s total gold is less dependent on your individual early window than it is in a solo game. The boost itself is unchanged, but the decision weight of your second port in the team’s plan is lower, which means the 90-second rush is still correct for your own gold but less likely to move the team’s outcome than it is in a solo match. The counter: in team modes, coordinate with your team’s other members on who takes the second port, because two team members both building a second port at 90 seconds is a gold double-spend that the team as a whole does not need.

What to do with this page: the three-turn checklist

Run this in the first three minutes of any v0.35.0 or later match. The checklist is designed to be run in under ten seconds per turn, and the decision at each turn is a single yes/no question: “is the next 125,000 a port the boost is amplifying, or is it a combat/land answer I cannot defer?”

1. Turn 1 (first 90 seconds after your first port is up): check the trade route’s both-ends-enemy status. If the route is safe (at least one end is your own or allied land), build the second port now if you have 125,000 gold. If the route is both-ends-enemy and you have no warship to screen it, hold the 125,000 and take the warship first; the boost is still active when you return, because the level count only moves when you build, not when the map changes around you. The one detail that changes Turn 1 on contested maps: if your opponent is visibly rushing a warship, the warship-first option is the safer default, because the 190-second head start from Scenario 1 is not worth a lost port.
2. Turn 2 (next 90 seconds): if you built the second port you are now at level 2 (1.44x realized ship rate). The next decision is the third port versus a land expansion or a troop answer. Apply the Scenario 2 test: if the next 125,000 is a combat decision it loses to the troops or the land; if it is not, build the third port and move to the level-3 row. The one detail that changes Turn 2 in team modes: if a team member is already at level 3 or higher, the third port’s marginal value in team terms is lower, and the land expansion or troop answer is the better default.
3. Turn 3 (next 90 seconds, or the next decision slot): if you are at level 3 or higher, the boost is now 1.21x or lower and falling. Stop treating it as the primary driver and switch to the Port versus Factory framework for the rest of the opening, and to the front-loaded Port and Factory investment framework once you reach the mid-game, where the saturation midpoint changes (still in effect in v0.35.2) start to matter more than the small-economy boost, which has by then faded to near 1.0. The one detail that changes Turn 3 on the v0.35.x sub-versions: the boost formula is identical across v0.35.0, v0.35.1, and v0.35.2 (verified byte-for-byte), so the checklist is the same on all three sub-versions and does not need to be updated for any of them.