How to Read, Filter, and Choose the Right Public Lobby in OpenFront

The public browser in OpenFront is not a single lobby list — it is four separate queues (FFA, team, special, hosted) that the game feeds you at once. Every card shows the map, the mode, modifier pills, the current player count, and a countdown pill. Reading those four things and the auto-start window is what lets you pick the lobby that actually fits your goal. Listing a public lobby of your own is gated behind a paid subscription (Warlord or Sovereign), so a free player can join and pick freely but cannot host-and-list. In v0.34.20, listed lobbies can also distribute joiners across sibling lobbies; that may change the exact sibling you enter, but it does not change the card’s mode, host-selected one-to-five-minute start window, ten-to-one-hundred player cap, or locked configuration.

What the public browser actually shows you

When you open the public lobby browser from the main menu, the game does not hand you one mixed feed. It sends a single feed — the public games endpoint — that is split into four buckets keyed by public game type, and the interface lays those buckets out so you can scan each queue on its own. The four types the server can serve are FFA, team, special, and hosted, and those four names are the only values the public browser will ever show. That single design decision is the most important thing to internalise before you try to “find a lobby,” because the question “which lobby should I join?” is really two questions stacked: which queue am I in, and which card inside that queue fits what I want to play right now.

Each bucket is populated independently. The master scheduler fills the FFA, team, and special queues from the map playlist on a rolling basis, which means those three queues are always rotating and the specific lobbies you see are a moving target. The hosted queue is fundamentally different: it is not scheduler-driven at all. Every card in the hosted queue is a lobby that a player created privately and then chose to list publicly, and that host — not the game’s scheduler — controls when it starts, when it fills, and when it disappears. The schema that defines this even explicitly excludes hosted from the scheduled set, because the host owns its lifecycle. So when you read the browser you are looking at two kinds of thing at once: three queues the game runs for you, and one queue of player-hosted rooms where the terms are whatever the host set. Everything in the rest of this guide is about how to read both kinds confidently and not waste time on a lobby that will not do what you need it to do.

The quickest way to hold all four queues in your head at once is this summary table:

The practical upshot is that you should never treat the browser as a single sorted list and just click the top card. The top card in FFA is a free-for-all that may be near full and about to start; the top card in team is a structured match with a fixed team count; the top card in special carries modifiers that change the rules; and the top card in hosted is someone’s private room that may require you to be trusted or in their roster. Treating them as one list is the single most common onboarding mistake, and it is exactly what makes new players feel the lobby system is confusing or “trash.” Separate the queues first, then compare cards within one queue, and the whole browser becomes something you can scan in seconds instead of a wall of near-identical map art.

The four queues and how to decide which one is yours

The FFA queue is where you go when you want a classic free-for-all: no teams, no truce, the winner is whoever survives or holds the most at the end of the clock. The cards in this queue are the fastest-moving of the three scheduled queues, they cycle through the map playlist continuously, and they are the default place the browser points a brand-new player. If your goal is “just get a match going with normal rules and a reasonable number of people,” FFA is the queue to stand in. The thing to read on each FFA card is the mode subtitle at the bottom of the card and the player count, because those two together tell you whether the lobby is about to fill and start with you in it or whether it is still open and you will land at a disadvantage.

The team queue is for structured play: the card’s subtitle names the shape of the match, for example five teams of twenty, so before you join you already know it is not a free-for-all and you are about to pick up or be placed into a team. This is the queue to stand in when you want coordination, a role, and a game that plays more like a competitive team match than a scramble. The difference from FFA is real and it changes how you position yourself the moment you spawn, so choosing the right queue here is not a preference, it is a commitment to a different way of playing. The special queue is the modifier queue: every card there has rolled one to three weighted modifiers from the modifier pool, and those modifiers can change the rules dramatically. If you want variety, chaos, or a specific modifier you are looking for, the special queue is where you hunt — but you are also accepting that the rules are not standard, so you should read the modifier pills before you commit to a special lobby.

The hosted queue is the one that behaves differently from all three of the others. These are player-created rooms that a host has listed, and the host controls the start, the roster, and the lifecycle. Some hosted lobbies are open to anyone, some are trusted-only (they show a gate with an explanation instead of letting you join), and some are full and starting in seconds. You choose the hosted queue when you want a specific player’s room, a friend’s match, or a room that the host has set up for a particular purpose. The decision rule across all four is simple: pick the queue that matches the kind of game you want (normal FFA, structured team, modified special, or a specific player’s room), and only then pick the specific card. Mixing these two decisions — “which card” before “which queue” — is how you end up in the wrong match type and lose the match before it starts.

What each field on a lobby card actually means

A lobby card is not just map art. The card component renders a specific set of fields, and each one answers a concrete question you need to answer before joining. The map image fills the card and, behind it, a set of modifier pills sits over the art: those pills are the modifiers the lobby will run, and on a special lobby they are the entire reason the lobby is different from a plain FFA. Reading the pills before you join is the one habit that prevents the “I joined and the rules are not what I expected” failure, because the pills are the lobby’s rule set made visible at a glance. If you are in the special queue and a card has no pills that appeal to you, that is the lobby to skip, not the one to gamble on.

The bottom bar of the card names the map and the game mode together. This is the line you check to confirm the mode — for example “FFA” or “5 teams of 20” — and it is the fast way to verify you are looking at the match type you think you are. A featured lobby overrides this line: instead of the map name it names itself, so a featured lobby carries its own label plus an accent colour, and that is how you recognise a featured (front-and-centre) lobby versus a rotating playlist lobby at a glance. The player count is shown on the card as well, and it is your signal for how full the room is: a count near the cap means the lobby is close to starting, a low count means it is still open and you will be entering early. Finally, the countdown pill on the right of the card is the single most decision-relevant field on the whole card.

That countdown pill tells you, right now, how long until the lobby starts — or that it is already “Starting…”. It is the window that decides your opening position, because a lobby you join with ninety seconds left starts with you still loading in and not ready, while a lobby you join early gives you time to pick your starting position, set up, and be ready for the drop. The countdown is what turns “which lobby” from a guess into a timed decision: you are not just choosing a room, you are choosing a room at a specific point in its start cycle. Together the four fields — modifier pills, the map-and-mode bottom bar, the player count, and the countdown pill — are everything the card gives you, and a player who can read all four in under a second per card can scan a whole queue and make the right pick without overthinking. If you find yourself ignoring the countdown and just clicking, that is the field to train on first, because it is the one that changes the match you actually get.

Why the list looks short and how timing changes your options

A very common complaint from the community is that the public list feels too short — “why are there only a handful of lobbies?” The honest answer is structural, not a bug. The three scheduled queues rotate on the scheduler’s schedule, so at any given moment there is a limited set of live FFA, team, and special lobbies, and they are constantly being replaced as the playlist rolls. The hosted queue is even more tightly bounded: the server holds at most ten hosted lobbies in the public list at once, and in v0.34.18 each of those lobbies runs on an auto-start window the host picks between one and five minutes. That means the hosted queue is not an open marketplace of hundreds of rooms; it is a small, capped, time-boxed set that empties and refills as hosts list new rooms and old ones auto-start and close. Featured lobbies run on a ten-minute window, so they change even more slowly.

Understanding that bound changes how you behave. Because the hosted list is capped at ten and runs on a one-to-five-minute window the host sets, a hosted lobby you see now may be gone in a couple of minutes if the host set a short window and the lobby fills, so hesitation has a real cost: the lobby you are reading may no longer exist by the time you finish reading it. The counter-move is to read the countdown pill and the player count together and decide within seconds, because the window is short by design. For the scheduled queues the same logic applies in a softer form: the lobbies rotate, so a specific FFA lobby you are staring at may be replaced by the next playlist entry, and the right move is to commit to a queue (FFA, team, or special) and pick the first card in that queue that reads well, rather than waiting for a perfect card that the rotation may never produce.

This is also why the timing of your entry into the browser matters. If you open the browser right as the hosted lobbies are auto-starting, you will see a short, churning list; if you open it mid-window, the list is more stable and you can read it properly. There is no free lunch — the hosted window is now host-selectable from one to five minutes and the featured window is ten minutes, and the cap is ten hosted rooms — but knowing the shape of the churn lets you stop treating a short list as a failure of the system and start treating it as the system working as designed. The concrete habit is: pick your queue, read the countdown and count on the first one or two good cards, and join before the window closes. That habit turns “the list is too small” from a complaint into a non-issue, because you stop waiting for a list that is structurally going to be small and fast-moving.

What you can and cannot do: the subscription gate

There is a hard gate on what you can do with public lobbies, and it is the one thing new players are most surprised by. Joining and choosing from the public browser is open to everyone — a free player can read all four queues, compare every card, and join any lobby that is open to them with no restriction. The gate applies to creating and listing a public lobby of your own: the public-list toggle in the host dialog is only available to a player with the right to create public lobbies, and when it is not available the game shows an information dialog pointing you to the subscription page instead of the toggle. The in-game gate names the tiers that can list: a Warlord or Sovereign subscription — the host dialog’s subscription-required dialog and the store page are where the current pricing and exact tier are stated, and that is where you should confirm it before assuming, because tier boundaries can shift between releases.

So the decision the gate forces is this: you can be a consumer of the public lobby system at any tier, picking from the four queues and joining freely, but you cannot be a producer of listed public lobbies without the paid entitlement. That split matters for how you plan your play. If your goal is simply to find and play matches, you do not need to buy anything — the entire browser and all of the joining is available, and the only thing you cannot do is host a listed room. If your goal is to run your own room with friends, host a custom setup, or list a lobby that others can find, then the subscription is the prerequisite and you should confirm the exact tier and price at the store before you commit. The most common confusion is assuming that because you can see the list you should also be able to add to it, and the gate is the reason that assumption is wrong.

The practical read is to separate “I want to play” from “I want to host and list.” For playing, the system is fully open and the only thing that affects your options is which queue you are standing in and how full the cards are. For hosting and listing, the entitlement is the first thing to check, and if you are not on the required tier the toggle will not appear — you will see the subscription dialog instead, and that is the game telling you the feature is paywalled rather than silently failing. Knowing this before you try to host saves the awkward moment of reaching for a toggle that is not there. And because the exact tier boundary is a subscription detail that the store is the source of truth for, the guide points you there rather than restating a price, which can change; the structural fact — free to join, paid to list — is the stable part you can rely on now.

Failure modes and what to do about each one

The lobby system has a short list of real failure modes, and each one has a concrete counter that reading the card gives you. The first and most common is joining a lobby that starts before you are ready: you click a card, the countdown hits zero while you are still loading, and you land in the match without your setup. The counter is the countdown pill itself — do not join a lobby whose pill is already low unless you are ready to start immediately, and prefer a lobby with a comfortable window so you can pick your position and be ready for the drop. If you are reading a lobby with seconds left and want to be ready, join now; if you want setup time, pick a lobby with a longer countdown.

The second failure mode is the lobby that disappears before you commit. Because hosted lobbies are capped at ten and run on a one-to-five-minute window the host sets, the lobby you are reading can auto-start and close while you are deciding. The counter is to make the decision fast: read the queue, the count, and the countdown on the first one or two cards that fit, and join without over-deliberating. Do not stand on a single card reading it for a full minute in the hosted queue — the window will move. The third failure mode is the trusted-only lobby: a hosted (or roster-controlled) room that you are not allowed to join shows a gate with an explanation popup instead of letting you join, and the join does not fail silently — the game tells you that you need to be trusted to enter. The counter is to recognise the gate before you click, understand that this room is for the host’s trusted circle, and move to an open lobby rather than waiting for the host to add you.

The fourth failure mode is the mode mismatch: you join what you assumed was an FFA and it is a team match, or you join a special lobby without reading the modifiers and the rules are not what you expected. The counter is to read the bottom-bar mode and the modifier pills before joining, not after. The fifth failure mode is the “too few lobbies” trap, where you keep waiting for a better list that is structurally going to be small and fast. The counter is the queue-first habit: commit to the queue that matches your goal and take the first card that reads well, because a small rotating list rewards decisiveness, not patience. Every one of these failures is preventable with the same two skills — reading the card’s fields and acting within the countdown window — and the rest of this guide is about making those two skills automatic so the lobby browser stops being a source of frustration and becomes a fast way to get into the match you actually want.

Filtering by mode and map: a concrete decision procedure

Putting the fields together gives you a repeatable procedure for going from “I want to play” to “I am in the right lobby” without guessing. Step one is to name the kind of game you want, because that selects the queue before you look at a single card. If you want a normal free-for-all with standard rules, go to FFA. If you want a structured team match with a fixed team count, go to team. If you want modifiers and variety, go to special. If you want a specific player’s room or a friend’s match, go to hosted. This step is the one most people skip, and it is the one that causes the most wrong matches, so make it explicit: write down the kind of game before you touch a card.

Step two is to scan the cards in that queue and filter by the fields that matter for your goal. If you have a preferred map, scan for the map name in the bottom bar and prefer the cards that show it. If you care about modifiers, read the pills and keep only the lobbies whose modifiers you actually want to play under — in the special queue this is the whole point of the queue, so a card with no modifiers you like is a card to skip. If you want to enter at a fair point in the match, read the countdown pill and prefer lobbies with a window that gives you setup time, and check the player count to see whether the room is about to fill. Step three is to commit within the window: pick the first card that passes your filters and join it, because the list is rotating and the hosted lobbies are time-boxed, so the best card you can get is the first good one, not the perfect one you keep waiting for.

Step four is to handle the edge cases as they appear. If the card shows a trusted-only gate, skip it for an open one — do not wait to be added. If the countdown is already low and you are not ready, either join immediately if you can commit or pick a lobby with a longer window. If the mode on the bottom bar is not the one you wanted, that is the lobby to leave the queue on — you are in the wrong queue and you should re-run step one. The whole procedure is fast by design: queue first, filter by the fields that matter, commit within the countdown, and handle gates and mismatches by skipping rather than stalling. A player who runs this procedure turns the lobby browser from a wall of near-identical map art into a filterable list, and the “which lobby should I join” question stops being a vague feeling and becomes a four-step check you can run on any card in a few seconds. The lobby pick is the decision everything else then depends on: once you are in, your opening position is the lever that decides the first minutes, which is covered in First Match, and your map and modifier choices feed straight into the wider map strategy the lobby’s bottom bar and pills are telling you.

Version boundary: what is live today versus what is coming

The one number and one timer that are easy to get wrong across guides and streams are the hosted-lobby auto-start and the hosted-lobby cap, so it is worth stating the version boundary precisely. In the build you are playing today — release v0.34.18, shipped 2026-09-24 — the hosted queue works like this: the public hosted list is still capped at ten lobbies at once, featured lobbies still run on a ten-minute window, but the hosted auto-start is now host-selectable anywhere from one minute to five minutes, and a hosted lobby can now hold between ten and one hundred players. That is the current, verifiable behaviour, and it is what this guide’s timing advice is built on: read the countdown and the player count, act within the window the host set, and watch for the early start that fires when a listed lobby fills to its cap.

A change that landed in the same release is just as easy to get wrong, and it is the one that used to trip up every other write-up: making public lobby listing one-way. In v0.34.18 a host can still list a lobby, but once a hosted lobby is listed the server rejects unlisting — the host cannot take it back down. That is a real change to the hosted queue, and it is in the live build now, so describing it as something you can use today is correct. Combined with the lock that applies to a lobby’s settings once it is listed, the practical effect is that a host commits more fully before the lobby goes public: the start window, the player cap, and the settings are effectively set the moment the lobby is listed. The guide’s rule is to keep the live numbers (host-selectable one-to-five-minute hosted window, ten-minute featured, ten-hosted cap, ten-to-one-hundred player cap, one-way listing, Warlord-or-Sovereign gate) as the facts you can act on today, and to treat any tip that still describes a fixed five-minute window or a host who can unlist a lobby as describing an older build. If you see a stream or a guide that says a host must wait a fixed five minutes or can take a lobby back down, that is describing the previous behaviour, not the one in your client, and you should hold the one-to-five-minute, one-way behaviour as the truth for v0.34.18.

The reason the boundary matters for your decisions is that the timing advice is different from release to release, and v0.34.18 is the first build where the hosted window is a choice rather than a constant. On the live build the countdown pill is still the only timing signal and you act on it directly, but the number it shows is now whatever the host picked between one and five minutes, not a fixed five. A hosted lobby that shows a short window is one the host set tight, so you should read the player count alongside it: if the lobby is filling, it may start early the moment it hits the cap, which shortens whatever window the host chose. That is the difference from the older fixed-window build, where every hosted lobby counted down the same five minutes no matter what. Keeping the build you are playing cleanly separated from the older behaviour is what lets you trust the rest of the guide: the fields, the queues, the cap, the gate, and the timing are all stated for the build you are actually playing, and the previous release is labelled as previous. That discipline is the difference between a guide that is useful on day one and a guide that quietly teaches you to expect a window that your client no longer enforces.