As a player who has spent more nights than I care to admit dropping into battle royales, shooters, and live-service experiments, I thought I understood how hard it is to make a multiplayer game. Then I read what PUBG's IP franchise director, Taeseok Jang, said during an exclusive Krafton press tour, and I realized I had been looking at shutdowns like a spectator, not like someone standing in the developers' shoes. What happens when a game you have worked on for years goes live and disappears in two weeks? Is that just a failure, or is it a lesson written in server logs and community posts?
Jang says he feels sad when other multiplayer games don't succeed. That sentence stuck with me. He has friends who worked on Concord and Highguard. Concord launched in August 2024 and lasted just two weeks before Sony pulled the plug. Highguard, which launched in January 2026, managed to keep going for just over six weeks. Those numbers are brutal. But what moved me was not the numbers; it was Jang's reaction. He tries to see these failures as learning opportunities. 'When you think about making new games, it's really hard to succeed every time,' he says. He puts himself in their positions and asks, 'What could I have done better in that situation?' That is not armchair criticism. That is empathy with a notebook.

I have been the player who refreshes a store page, watches a trailer, and makes a snap judgment. I have also been the player who logs off after a rough launch and never comes back. So when Jang talks about community messaging, I nod. Highguard's case feels especially sharp: Wildlight Entertainment debuted the shooter at the 2026 Game Awards and then went almost silent right up until launch over a month later. That is an incredibly bold strategy for a debut game. Bold can work, but silence can also leave players to fill the gaps with doubt. If you do not tell your story, someone else will, and they will probably do it with fewer facts and more cynicism.
Here is how I see the recent multiplayer casualties:
| Game | Launch / Window | Outcome | What I take away |
|---|---|---|---|
| Concord | August 2024 | Shut down after two weeks | A polished shell is not enough without a clear reason to return |
| Highguard | January 2026 | Lasted just over six weeks | A big reveal needs sustained communication, not a long silence |
| PUBG: Blindspot | Early access, shut down end of March 2026 | Lasted just under two months | Small-team prototyping and player feedback matter more than pride |
Jang is no stranger to short-lived games, either. PUBG: Blindspot, a top-down tactical shooter, was shut down permanently at the end of March following an early access stint that lasted just under two months. That could make someone defensive. Instead, Jang says Blindspot's development 'reinforced how important it is to rapidly prototype in small teams and incorporate player feedback into the development process.' I love that. It is the opposite of pretending a bad launch is a mystery. It is treating early access as a laboratory, not a victory lap.
And he is not alone. InZoi's boss strongly recommends early access to other developers, too. The InZOI boss also says the success of Crimson Desert and other Korean games is 'really nice to see,' but Asian developers 'still have a lot to learn from Western developers.' That is a big statement, and as a player I appreciate the humility. The industry is not a single ladder. It is a messy web of regional strengths, tooling, community habits, and publishing muscle. Learning from others is not weakness; it is how you survive the next launch.
So what should a player like me do with all this? I can be kinder, but not blindly kind. I can give feedback that is specific instead of just loud. I can recognize that a two-week shutdown is not a moral failing; it is often a business decision made after a thousand smaller signals. But I can also vote with my time and say clearly what I want. Multiplayer games live and die on community, and community is a two-way street.
What I take from Jang's interview is not an excuse for every failed launch. It is a challenge to think like a builder even while I am sitting in the player's chair. The next time a multiplayer game stumbles, I will ask myself the same question Jang asks: what could have been done better? Sometimes the answer will be 'a lot.' Sometimes it will be 'nothing, the market just moved.' But asking the question keeps me connected to the people behind the servers. And in a medium built on connection, that feels like the whole point. 🎮