radar
Another Live-Service Game Died This Month: The Case for Self-Hostable Servers
A new MMO this year peaked at 888 concurrent players on Steam before collapsing to dozens. Another live-service title got shut down just months after launch. Meanwhile, self-hostable games from a decade ago still have populated servers. The difference is not popularity - it is who owns the server.
The 2026 body count
Two data points from this year tell the whole story. First, a new MMO, Spellcasters Chronicles, peaked at just 888 concurrent players on Steam and quickly tailed off to a few dozen - a launch that never reached the population a live-service game needs to sustain itself. Second, the gaming press logged yet another live-service game shutting down only months after launch, the latest entry in a multi-year pattern of expensive online games closing fast.
This is not a fluke or a couple of bad games. It is the base rate. The live-service model concentrates everything - the world, the matchmaking, the save data, the population - on servers the publisher controls. When a launch undershoots, the math stops working, and the only lever the publisher has is the off switch. When they pull it, the game does not get smaller. It becomes unplayable, permanently, for everyone who bought it.
Why publisher-run games die and self-hostable ones don't
Contrast the 888-player flop with any self-hostable game. When a game ships a dedicated-server build that players can run themselves, its multiplayer outlives the publisher's interest in it. The studio can stop funding official servers, stop shipping content, even shut the company down - and the community servers keep running, because the people playing own the infrastructure.
That is the entire difference, and it is structural, not sentimental:
| Publisher-run (matchmaking / MMO) | Self-hostable (dedicated servers) | |
|---|---|---|
| Who runs the servers | The publisher, exclusively | Anyone - the publisher, communities, or you |
| What happens at shutdown | Game becomes unplayable | Community servers keep running |
| Lifespan | The publisher's decision | The community's decision |
| Examples that prove it | The growing list of shuttered live-service titles | Decade-old shooters and survival games still populated |
This is why the "Stop Killing Games" preservation argument keeps coming back to one technical ask: ship the server binary. A game with a self-hostable server is, by construction, preservable. A game without one is at the mercy of a balance sheet.
Popularity is not permanence
The obvious objection: plenty of live-service games are thriving. True. Final Fantasy XIV still peaks in the tens of thousands, Fallout 76 holds a healthy population years on, and Steam itself set an all-time record of over 42 million concurrent users in January 2026. The market is enormous.
But healthy publisher-run games are healthy conditionally. They are still entirely dependent on the publisher choosing to keep the lights on. FFXIV is wonderful and also one corporate decision away from the same fate as every shuttered MMO before it. Popularity buys time; it does not buy permanence. The only thing that makes a multiplayer game genuinely durable is the community's ability to host it without permission.
The question to ask of any multiplayer game you want to still be playing in five years is not "is it popular?" It is "if the publisher walked away tomorrow, could the community keep it running?" For self-hostable games the answer is yes. For everything else it is no.
What it means if you want a game to last
None of this is an argument against playing live-service games - plenty are great, and enjoying something with a finite lifespan is fine as long as you know that going in. It is an argument about where to invest if you want longevity: a clan that wants to play together for years, a community that wants a stable home, a group that does not want its world to vanish on a publisher's schedule.
For those groups, the durable choice is a game with a dedicated, self-hostable server - survival worlds, large-scale shooters, sandbox games - the same category that is actually rentable and self-hostable in the first place. You can run it on a managed host, move it between hosts, or bring it home, and no single company can switch it off. That control is the whole point of this site, and it is worth weighing before you commit a community to a game whose servers you will never be allowed to touch.
If you are deciding what to play next, our breakdown of which of this month's releases are self-hostable is the practical companion to this argument.
FAQ
- Why do live-service games shut down so fast?
- A publisher-run multiplayer game needs a critical mass of concurrent players to justify its costs. When a launch undershoots - some 2026 launches peaked in the hundreds, not the tens of thousands - the economics break and the publisher pulls the plug, often within months. The servers are theirs, so the game becomes unplayable the moment they switch them off.
- What makes a multiplayer game survive a shutdown?
- A self-hostable, dedicated-server build. When the game ships server software players can run themselves, the community keeps it alive long after official support ends - which is why decade-old self-hostable games still have populated servers.
- Aren't popular MMOs like FFXIV proof live-service works?
- They prove popular live-service works while it is popular. FFXIV and Fallout 76 still post healthy numbers, but they are publisher-run, so their lifespan is the publisher's decision. Popularity buys time; it does not buy permanence. Only self-hostable servers do that.