Skip to main content
⌖ OF Intel

GUIDES

How to Create a Private or Custom Game in OpenFront: Every Host Setting, Listed and Unlisted

Create a private OpenFront game. v36.3 changes publicly listed hosted lobbies to up to 500 players on any map; older settings below retain their v36.2 scope.

Tutorial Difficulty · Beginner Published Nov 15, 2026 Updated Nov 18, 2026 Reviewed by OpenFront Intel editors #host-lobby#private-game#custom-settings#win-threshold#lobby-preset#onboarding

Current listed-lobby limit: up to 500 players on any map. v0.36.3 replaces v0.36.2’s map-dependent limit for publicly listed hosted lobbies. The Box’s old 210-player hosted ceiling and the smaller-map listing ceilings below are historical. This does not set every scheduled public match to 500 players, and a higher limit does not make every map comfortable at that population.

For the full patch, see the v36 release notes. The walkthrough below describes the settings checked on November 15, 2026, at v0.36.2. Its map-based listing instructions and examples belong to that version; use the 500-player rule above for current listed hosted capacity. The other settings have not all been revalidated by this limited update.

In v0.36.2, every OpenFront match starts from the same place: a host creates a game, and that creation step is where the whole match gets its rules. The default public queue hands you a randomly configured game, but the Create Game flow hands you the actual settings dialog — the win threshold slider that now runs from 10% to 99.9%, a player limit you can set anywhere from 2 to 1000, a match timer from 1 to 120 minutes, spawn immunity, alliance duration, gold multipliers, a start delay in seconds, and presets that save your whole configuration for next time. This guide walks the full host flow in order, explains what each control changes about the match, and separates the two halves of the decision: building a private room for friends (free, no subscription, no lock-in) and listing that room publicly (subscription-gated, one-way, settings locked, auto-started after five minutes if you do not start it). If you have ever wanted a 12-player game on 4 Islands, an 80% threshold that actually ends in Overtime, or a friend game that never softlocks in a draw, the answers are in this dialog, and the numbers below are all from the v0.36.2 release and its source.

The create-game flow, step by step

The flow starts from the main menu. Where the default button joins the next scheduled game with whatever the playlist rolled, the create flow opens the host lobby dialog — the same dialog a listed host reopens to manage their room. The first thing the dialog shows is the map and the mode, because those two choices frame everything else: the map determines the maximum sensible player count, and the mode (FFA or teams) determines how the win threshold is applied. After that, the dialog lays out the settings controls as a stack of toggle-input cards, and the two important facts about that layout are that every setting has its own toggle plus a value field, and that a toggled-off setting means the default for that setting applies rather than zero or off. The win threshold card, for example, is off by default (meaning the standard 80% rule applies) and on with a value when you want a custom threshold; the player limit card is off by default (meaning the map’s natural capacity) and on when you cap the match.

The second important fact about the flow is the visibility toggle near the top of the dialog: Private or Public. A Private game stays invisible to the public browser; you share the game link or have your friends join from the room, and only players you want are in it. A Public game becomes a listed hosted lobby: it appears in the hosted queue of the public browser, anyone in that queue can see it, and the server starts running the hosted-lifecycle rules against it — the five-minute auto-start deadline, the map-driven player cap, and the settings lock. Choosing Public before you are ready to list is the most expensive mistake in this dialog, because once the lobby is listed you cannot take it back, and the moment it is listed your settings panel stops accepting changes. The third fact is the seating area at the bottom of the dialog: your own seat, the other open seats, the current player count, and the start control. The Start button is what actually launches the game at whatever time you want — for a private room that means you control the clock entirely, and for a listed room you also have a hard five-minute deadline from the server.

Putting the steps together gives a repeatable procedure. Pick the map and mode first, because those two choices constrain the player limit and the threshold behaviour. Then set the rules you actually want different from default — threshold, player limit, timer, immunity, alliances, gold — and leave the rest toggled off so the standard defaults apply instead of a half-set custom value. Then decide the visibility: Private for a room you will start yourself with known players, Public only when you want strangers to be able to find the room and you have the subscription that allows listing. Finally, save a preset if the combination is one you will reuse, seat your players, and press Start when the room is full or when you simply want it to begin. Every later failure mode in this guide traces back to one of those five steps being done out of order, and the section on failure modes maps each symptom to the step that caused it.

The settings dialog, control by control

The win threshold is the headline v0.36.0 change and the one control that most changes the shape of a match. The card’s toggle turns the custom threshold on, and the value field accepts anything from 10.0 to 99.9 in steps of 0.1, with the placeholder showing the standard 80. The meaning is direct: the match ends early the moment a player (or team) holds at least that share of the territory, and the game schema caps the value at 99.9% because the win check is a strict greater-than comparison, so 100% would be mathematically unwinnable. A low threshold like 10% means the first big annexation ends the game within minutes; a high threshold like 95% means the game will almost always run to the timer or into Overtime unless one player truly dominates the map. The release notes added presets to this control so the common values are one tap away, and the same control works in team mode, where the threshold applies to team share. If you are unsure what a threshold does before you set one, the companion win conditions guide reads the live threshold and the five end states in detail, and the team victory threshold guide covers how the same number behaves when teams are on.

The player limit is the second big lever. The card’s toggle caps the match, the value field runs from 2 to 1000, and the default when the toggle is off is the map’s natural capacity. A cap of 2 makes a 1v1 that is essentially a ranked-style duel; a cap of 12 is the size the community’s own tips threads cite as the point where FFA games become winnable; a cap of 50 or 100 is the normal public-feel game; and a cap near 210 is a large-map brawl. The cap is not only a number to reach — it is a timer, because a listed lobby that fills to its cap starts immediately, ahead of the auto-start deadline. For private games the cap simply closes the room at that number, which is the difference between a friend game where everyone who joined fits and a friend game where the twelfth friend sits in the lobby watching the eleventh play. The map matters here more than the number: the same cap of 60 on a compact map is a very different crowd from the same 60 on The Box, and the v0.36.2 change to map-driven hosted caps (The Box 210, smaller maps less, consistent with what the public lobbies on that map allow) means the listed version of your room will never let you cap it above what the map supports. The map-driven lobby size guide has the per-map numbers.

The remaining controls are the tuning knobs. The match timer (max timer) runs from 1 to 120 minutes with a default of 30 when enabled; it is the hard clock after which the endgame state begins. Spawn immunity runs 0 to 120 minutes and shields fresh players from the first wave of aggression — five minutes is the default, and zero removes the shield, which is what you want in a friend game where everyone knows the rules. Custom alliance duration runs 0 to 15 minutes; zero disables alliances entirely (the label in the dialog says so explicitly), and a nonzero value caps how long a mutual alliance lasts before it expires on its own. Overtime runs 1 to 120 minutes with a default of 30, and since v0.36.0 it counts down from your chosen value, with the territory threshold shrinking during it — the winning in Overtime guide covers what to do inside it. The gold multiplier runs 0.1x to 1000x with a default of 2.0x, and the starting gold field sets the head start every player begins with. Start delay runs 0 to 600 seconds with a default of 3; it is the pause between the last seat filling and the game actually launching, and it is the setting that decides whether a slow-loading friend gets stranded. Each of these is a toggle-plus-value card, and the pattern to internalise is: toggle off means the standard default, toggle on plus a value means your override — there is no “half” state, and a half-set value is how you accidentally make a 1-minute match or a 0-allyles game you did not intend.

A quick reference of every control, its range, and its default when the toggle is off:

ControlRangeDefault (toggle off)What it changes
Win threshold10.0–99.9%, step 0.180% (standard rule)Early-win trigger when a side holds that share
Player limit2–1000Map’s natural capacityCloses the room at that count; the listed cap is map-driven
Match timer1–120 min30 minHard clock after which the endgame state begins
Spawn immunity0–120 min5 minShields fresh players from the first wave of aggression
Alliance duration0–15 minAlliances onZero disables alliances; nonzero caps how long one lasts
Overtime1–120 min30 minCounts down from the chosen value; the threshold shrinks during it
Gold multiplier0.1x–1000x2.0xStarting gold head start for every player
Start delay0–600 s3 sPause between the last seat filling and the game launching

Choosing a win threshold that ends the game the way you want

The threshold is the single setting most likely to make or break a custom game, because it decides whether the game ends in a clean early win, a long grind, or an Overtime scramble. The default 80% is tuned for the standard public game: with 50 or 100 players on a large map, no one holds 80% of the territory, so the game usually runs to the timer and the endgame is decided in the final minutes or in Overtime. That is the correct behaviour for a large public game — an 80% threshold at 100 players is effectively a “nobody can win early” rule, which keeps the map busy until the clock. But the same 80% in a 4-player friend game on 4 Islands is a different animal: with four people, 80% is reachable, and the game will end the moment one player takes the fourth island, which is often exactly what you want in a small match and sometimes a softlock in the wrong one.

The decision framework is to match the threshold to the player count and the map, not to the mood of the room. For 2v2 or small FFA (under about 12 players), a lower threshold — 50 to 70% — ends the game when a real lead exists, which is what the community’s tips threads converge on: games under 12 players are winnable, and the win should be bankable before the endgame turns into a stalemate. For mid-size games (12 to 50 players), 80% is the honest default: it is high enough that the game plays out, low enough that a genuinely dominant player does not have to wait out a full 30-minute timer. For large games (50 to 200 players), keep 80% or go higher (85 to 95%), because at that size no one is going to hold an 80% bloc for long and a lower threshold just produces a lot of fast, shallow games where one early annexation ends everything. The one value to avoid in every size is anything near 100: the schema stops you at 99.9, and a 99.9% threshold is a game that can only end by timer or Overtime, which is usually not what a custom game is for.

Two concrete scenarios make the numbers real. Scenario one: a friend group of 8 on 4 Islands who have played the default 80% threshold and are tired of games that end when the last island flips, with the winner decided by a 12-point lead they could not extend. The fix is a 60% threshold: the game now ends when one player holds 60% of the territory, which at 8 players on that map is a clear, bankable lead rather than a photo finish, and the game ends on the win condition instead of dragging into a final-minute scramble. Scenario two: a 100-player game on The Box where the host wants a real endgame rather than a 30-minute timer that everyone loses track of. The fix is the opposite direction — keep 80% or raise to 90%, because at 100 players the early wins are already rare, and lowering the threshold would produce a game that ends in five minutes on a random annexation, which nobody at that table wanted. The rule of thumb: fewer players, lower threshold; more players, threshold at or above default; never above about 95, and the Overtime card is where you decide what happens after the timer, not the threshold card.

Player limits, map size, and the v0.36.2 hosted cap change

The player limit is where the v0.36.2 release changed the rules that most affect large custom games. Before v0.35, a listed hosted lobby could be capped at a uniform 100 players on every map; v0.35 moved the public lobbies to map-driven sizing, and v0.36.2 extended the same logic to hosted lobbies: the cap a host can set on a listed lobby is now the largest public lobby the map gets, with a quarter of that on compact maps, floored at 10 so every map can still be listed. The concrete numbers from the release: The Box allows 210 players on a listed lobby, and smaller maps allow less, consistent with what the public lobbies on that map already run at. The server-side code that enforces this is the hosted-lobby player-count function, which computes the cap from the map’s land tiles and the compact flag, and the host dialog shows the resulting maximum in the listing step. For private games the number you type is still yours — the 2-to-1000 field — and the map does not police your private cap; the map-driven cap applies to the listed version of your room, which is the part other players can join.

The practical consequence is that the player limit and the map are one decision, not two. A cap of 150 on a compact map is a room that is always full and always starting, because the map does not have the territory to keep 150 players busy; the same 150 on The Box is a sprawling map with space to spare. A cap of 12 on 4 Islands is a tight, decisive FFA; the same 12 on The Box is a small room on a huge map, which plays like an exploration game where everyone has more territory than players. The listing step makes the interaction visible: the dialog shows the suggested maximum and the hard maximum for the map you picked, so if your cap is above the map’s hosted maximum the listing step will not accept it, and the fix is to lower the cap, pick a bigger map, or keep the game private where your cap is not policed by the map. For the historical v0.36.2 transition, compare a group of 150 on The Box: that exceeds the previous flat 100-player ceiling but fits the 210-player map cap introduced in that patch. A group of 30 already fitted under 100 and is not an example of capacity newly unlocked by v0.36.2.

The early-start behaviour ties the cap back to timing. A listed lobby starts immediately the moment it fills to its cap, ahead of the auto-start deadline, so a cap is also a start trigger: a 210-cap lobby on The Box that is half full will not start early, but a 25-cap lobby that reaches 25 will start the second the last seat is taken. For a private game the cap has no start trigger — you press Start whenever you want — which is another reason friend games with a tight cap and a known roster are the natural home for the small, winnable formats the community keeps describing. The one number to remember from v0.36.2 is that the listed cap is no longer a constant 100; it is a per-map value, The Box at 210, smaller maps less, and the public lobbies on the same map run at the same sizing, so the number you can list at is the number the map’s public games already support. If you are choosing a map and a cap together, pick the map first and let the map’s hosted maximum set the ceiling for the listed room, then set the private cap to whatever the actual table size is.

Private versus listed: what the visibility toggle actually changes

The Private/Public toggle near the top of the host dialog is the one setting that changes everything downstream, and it is worth understanding precisely what each side does before you flip it. A Private game is invisible to the public browser: it does not appear in the hosted queue, no one can find it by browsing, and the only way in is the game link or the host’s room. There is no auto-start deadline on a private room — you press Start whenever the table is ready, and if you sit in the lobby for an hour the server does not intervene. The settings panel stays fully editable for as long as the room is open, so you can change the threshold, the cap, the timer, anything, right up until you press Start. Private games are also where the host’s full control over the roster lives: you seat the players you want, the player limit closes the room at your number, and the start delay is the only timing between “room full” and “game running.” This is the mode for friend games, for testing a settings combination before you trust it, and for any game where the table is known in advance.

A listed Public game is a different regime. The moment the lobby is listed it appears in the hosted queue of the public browser, where any player can see the card — map, mode, modifier pills, current count, and the countdown — and join it, subject to the map’s hosted cap. The server starts a five-minute auto-start deadline at the moment of listing: if the lobby has not started by then, the server starts it for you, and the host dialog’s countdown reflects that deadline. Unlisting cancels the deadline, and relisting starts a fresh one, but the listing itself is one-way — once listed, the host cannot take the lobby back down, which is the v0.34.18 behaviour that is still in force in v0.36.2. The settings lock is the other hard change: the instant the lobby is listed, the settings panel becomes inert, the preset and copy controls are disabled, and an amber “settings locked” banner takes their place, so the threshold, cap, timer, and every other control are frozen at whatever they were at the moment of listing. A listed lobby also runs the map-driven cap described above, and within 30 seconds of its auto-start it can no longer sell queue spots, so the last moments of a listed lobby’s life are a short, fixed window.

The decision the toggle forces is therefore about the audience, not about the rules. If the table is friends or a known roster, go Private: no deadline, no lock, no subscription, full control until Start, and the cap is exactly the number of chairs you set. If you want strangers to find the room — a bigger game, a community event, a room for a content stream — go Public, and accept the three consequences together: the subscription that allows listing, the one-way listing with the settings frozen at the moment it goes up, and the five-minute auto-start that means a listed lobby will run whether you are ready or not. There is no “public but I can change settings” mode, and no “private but discoverable” mode; the toggle is the whole boundary, and everything in the next two sections — the subscription gate and the failure modes — hangs off which side of it you are on. The list lobbies guide covers the reading side of that boundary, what a player sees when they browse the hosted queue, and how to judge a listed card before joining it.

The subscription gate and the one-way listing

The one feature in this flow that costs money is listing, and the gate is explicit rather than silent. The host dialog checks the account’s entitlement for creating public lobbies, and if the account does not have it, the Public side of the visibility toggle is replaced by a subscription-required dialog that points at the store instead of showing the toggle at all. The in-game gate names the tiers that can list, and the store is the source of truth for the current tier and price, because those can shift between releases; the stable structural fact is the one the gate enforces — creating and running a private game is free at any tier, and listing that game publicly is the paid action. The host cheats guide is relevant on the private side, because a private room is the only place the host’s cheat controls are fully available, and some of those controls are mutually exclusive with listing at all.

The one-way listing is the other paid-and-permanent consequence, and it is the one new players most often miss. Listing is a state change, not a toggle you can flip back: once the lobby is up in the hosted queue, the server rejects any unlist attempt, and the host’s only lever is the settings lock, which freezes the configuration rather than undoing the listing. The practical effect is that a host commits fully at the moment of listing — the map, the mode, the threshold, the cap, the timer, the start window — because nothing in the listed lobby can be changed from that point on. The release notes for the change are explicit that this is intentional: the listed lobby’s configuration is the lobby’s public contract, and a host who can change the rules mid-listing is a host who can bait players into a game that is not the game they joined. For a private room none of this applies, which is the real reason to prototype a settings combination in a private room first: a private room can be reconfigured, re-capped, re-thresholded, and re-timed at will, and it is the only safe place to test a combination you are not sure of before you freeze it into a listing that cannot be walked back.

The decision rule that falls out of the gate and the lock is: do the free, editable thing first. Build the room privately, set the settings, seat the table, and play a test round if the combination is new. Only when the combination is one you trust — and only if the table is actually the kind of thing you want strangers to find — do you pay the listing cost and accept the lock. If the goal is a friend game, never pay the listing cost at all, because a private room has every advantage a listed room has for a known table and none of the disadvantages: no deadline, no lock, no cap policing, no subscription. If the goal is a public game, pay once, set everything before you list, and treat the five-minute auto-start as a feature of the public contract rather than a surprise — the lobby will run on schedule, the settings will be the ones you set, and the only thing left to decide is when to press Start yourself, if you want to start it before the deadline does.

Presets, start delay, and the settings that outlive the room

The preset controls sit at the top of the host dialog and are the mechanism that turns a one-off settings combination into a reusable one. A preset is a named snapshot of the lobby configuration — the map, the mode, the threshold, the cap, the timer, the immunity, the alliances, the gold, the start delay — and the dialog’s preset strip lets you save the current configuration under a name, load a saved preset back into the dialog, and delete one you no longer need. Presets live in the user settings, not in the lobby, which means a preset you save in one room is available in every room you create afterwards, and a preset you saved before the v0.36.0 threshold change loads with the threshold it captured, not with whatever the new default is. The one limitation is that the preset controls are disabled the moment a lobby is listed, which is the settings lock in action: you can save and load presets in a private room and in the pre-listing window of a public room, but not in a listed one, so the habit to build is to save the preset before you list, not after.

The start delay is the setting that most players never touch and most often need. The field runs from 0 to 600 seconds, with a default of 3, and it is the pause between the last seat filling and the game actually launching. At the default 3 seconds, a player who joins the last seat and is still loading when the room fills gets dropped into the game mid-load, which in a large map is a spawn without the map context they need; a 30-second delay gives a slow-loading latecomer time to finish loading before the first wave starts, and a 600-second delay is effectively a “start when I say so” hold that keeps the room full but frozen until the host starts it. The delay is also the only timing knob a private room has between “full” and “running,” which makes it the setting to reach for when a friend group keeps having someone join late and lose their first minutes; the fix is a longer delay, not a lower cap. For a listed room the start delay interacts with the auto-start deadline: the delay is the pause after the room fills, and the deadline is the hard stop after which the server starts the game regardless, so a listed room with a long delay and a slow-fill table will hit the deadline before the delay does, and the game starts on the server’s clock rather than the host’s.

The settings that outlive the room are worth naming explicitly, because they are the ones that make a custom game repeatable. The presets are the big one: a named combination that loads in one tap in any future room, which is how a friend group keeps playing the same 12-player 4-Islands 60%-threshold format without re-entering the numbers every time. The lobby link is the second: a private room’s link is the artifact you share with the table, and it is what makes a private game reproducible for a known roster without any listing at all. The start delay, the threshold, and the cap are the third cluster: the three numbers that most define the feel of the game, and the three worth pinning in a preset rather than re-deciding per room. If you are building a recurring format — a weekly friend game, a stream format, a community event template — the workflow is to set the numbers once in a private room, save the preset, share the link, and let the preset carry the format forward; the only things that change per session are the table and the start time, and everything else is one tap away. The first match guide covers what happens after the room starts, and the map strategy guide is where the map choice feeds into the opening position the start delay is protecting.

Failure modes and the setting behind each one

The host flow has a short list of real failure modes, and each one traces to a specific control rather than to the system at large. The first and most common is the game that ends too early or too late, which is always a threshold problem, not a luck problem. A threshold that is too low for the player count ends the game on the first big annexation, which is the “the game ended in five minutes” complaint; a threshold that is too high runs the game to the timer and into Overtime, which is the “we never reached a decision” complaint. The counter is the threshold decision framework from above: match the threshold to the player count and the map, lower it for small games, keep it at or above default for large games, and use Overtime to decide the endgame rather than the threshold. The second is the room that is full but not starting, which is a start-delay problem in a private room or an auto-start problem in a listed one: a private room with a long delay and a host who is not watching will sit full and frozen until the host starts it, and a listed room with a slow-fill table will hit the five-minute deadline and start half empty. The counter for a private room is a shorter delay or the Start button; the counter for a listed room is a cap that matches the realistic table size, so the room fills before the deadline does.

The third failure mode is the settings that changed after they should not have, which is the one-way listing in action: a host who lists a lobby and then tries to adjust the threshold finds the panel inert and the amber banner in place, and the only way to get the adjustment is to wait for the current game to end and create a new room with the corrected settings. The counter is the prototype-in-private habit: test the combination in a private room, confirm it behaves, and only then list it, because a listed lobby is a frozen contract and the fix for a frozen contract is a new room, not an edit. The fourth is the listed room that starts with a slow-loading player still in the last seat, which is the start-delay-and-auto-start interaction: the room fills, the delay runs, and a player who is still loading lands mid-wave. The counter is a longer start delay for slow-loading tables, or a cap that is one below the realistic table so the room does not fill until the last seat is actually ready. The fifth is the room that a friend cannot join, which is almost always the link, not the permission: a private room’s access is the game link, and a stale or mistyped link is the failure, not a gate on the friend’s side; the counter is to re-share the current link from the room and confirm the room is still open, because a private room that has started is gone from the lobby and a new session needs a new link. Every one of these is a setting, not a bug, and the section on version boundaries below lists which numbers are the ones that are easy to get wrong across releases.

Version boundary: what is live in v0.36.2 versus what is coming

The version boundary for this flow is the one that separates the numbers you can act on today from the numbers that were true last release, and it is worth stating precisely because the host settings changed across v0.36.0 and v0.36.2. In v0.36.2, the build this guide is written against, the facts are: the win threshold runs 10.0% to 99.9% in steps of 0.1 with the standard 80% as the default when the toggle is off, and the v0.36.0 presets are live on that control; Overtime runs 1 to 120 minutes with a default of 30 and counts down from the chosen value, the v0.36.0 behaviour; the player limit is 2 to 1000 for a private room, and a listed hosted lobby’s cap is map-driven — the largest public lobby the map gets, a quarter of that on compact maps, floored at 10, with The Box at 210 and smaller maps less, the v0.36.2 change; the listing is one-way with the settings locked at the moment of listing, the v0.34.18 behaviour still in force; a listed lobby auto-starts after five minutes, the host picks the start window between one and five minutes, and within 30 seconds of the auto-start the lobby can no longer sell queue spots; the match timer is 1 to 120 minutes, spawn immunity is 0 to 120 minutes, custom alliances are 0 to 15 minutes with zero disabling them, the gold multiplier is 0.1x to 1000x, and the start delay is 0 to 600 seconds. That is the full set of numbers that are live, and they are what the decision framework and the failure-mode counters are built on.

The one number that is easy to get wrong across the releases is the hosted cap, because it moved three times in a short window. Before v0.35, a listed hosted lobby was capped at a uniform 100 players on every map; v0.35 moved the public lobbies to map-driven sizing, so the public games on each map started running at the map’s natural size; and v0.36.2 extended the same map-driven sizing to the hosted lobbies, so the cap a host can list at is now the map’s largest public lobby, The Box at 210, smaller maps less. If a stream, a guide, or a community thread describes a listed lobby capped at a flat 100 on every map, it is describing the pre-v0.35 behaviour; if it describes the public lobbies as map-sized but the hosted ones as still flat-100, it is describing the v0.35 window. The live behaviour in v0.36.2 is the map-driven one for both, and the release body states it explicitly: the publicly listed hosted lobby cap moved from a uniform 100 to map-driven sizing, consistent with public lobbies, The Box at 210 and smaller maps less. The second easy-to-get-wrong number is the threshold range, because the v0.36.0 change made it 10 to 99.9 with presets, and any write-up that describes a fixed 80% with no custom option is describing the pre-v0.36.0 build. Keeping the v0.36.2 numbers as the truth and labelling the earlier behaviour as earlier is what makes the rest of the guide safe to act on: the threshold, the cap, the timer, the lock, the deadline, and the start delay are all stated for the build you are actually playing, and the previous releases are named as previous rather than blended in. If you are setting up a room today, the numbers above are the ones to use, and the one to double-check against the store is the subscription tier that allows listing, because that is the one number the in-game dialog does not state and the store is the source of truth for.

Related content

Continue reading
Adaptive Build Order: Spend the Next Gold on the Constraint

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.