Launchers replaced server browsers, then became them

The in-game server browser was replaced by matchmaking, and matchmaking was supplemented by launchers, and launchers grew curated server lists. The industry spent fifteen years removing the server browser and then rebuilt it, badly, somewhere else.

What the original actually did

A server browser was a table. Name, map, players, ping, and a filter box. It was ugly and it worked, and its important property was that every server was in it on equal terms — a server appeared because it existed, not because anybody approved it.

That property is the whole argument. A list that contains everything is a list where a new server has a chance, and where a server with twelve players and a specific personality can be found by the people who want exactly that.

Why it was removed

The usual explanation is that matchmaking is better for new players, and it is. A browser presents a beginner with forty choices and no basis for choosing, and most of them will pick badly and have a bad time.

The less-discussed reason is that a browser is a discovery surface the publisher does not control. Every minute a player spends choosing a server is a minute they are not in a monetised queue, and every server they choose is one whose behaviour the publisher cannot shape.

Both reasons are real. Only one of them is in the announcements.

What replaced it, and what it lost

Matchmaking answers "find me a game" well and "find me a place" not at all. Those are different questions, and the second one is what a community is.

The loss is not the interface. It is persistence: the same server, the same people, the same names. A lobby that dissolves at the end of the match cannot accumulate anything, and a community is an accumulation.

That is why the modes and communities that survived the transition are disproportionately on games that kept the browser, which is visible in what is still populated on Counter-Strike 1.6 and Team Fortress 2 decades after their release.

Then launchers grew lists

FiveM has a server list. So do most modding platforms and most games with third-party clients. They had to, because the moment a game has servers people choose between, something has to present the choice.

These lists are browsers with different politics. They are curated, ranked, frequently monetised through paid placement, and their ordering is a product decision rather than a query result. A new server does not appear on equal terms; it appears wherever the ranking puts it.

So the function returned and the property that made it valuable did not.

Why ranking is the whole difference

An unranked list is a database query. A ranked list is an editorial position, and once there is an ordering there is an incentive to sell it.

That is not automatically bad — a list with no ordering at all is unusable past a few hundred entries. What matters is whether the ordering is legible: whether a server owner can find out why they are where they are, and what would move them.

Where it is not legible, the list becomes a market in visibility, and the servers that win are the ones that spent rather than the ones that were good. Every list that has existed for long enough has had this argument.

What a good list owes a small server

Three things, and they are cheap:

Presence. Being in the list at all, reachable by filter, without payment.

A reason. Some visible basis for the position, even a crude one.

A path. Something a twelve-player server can do to be found by the people who would like it, that does not require being a two-hundred-player server first.

The original browser gave all three by accident, because it was not trying to be helpful: it was just showing you the table. Everything since has had to provide them deliberately, and most lists are still working out how.