Ars Live recap: How can we stop publishers from killing their own games?
Ars Technica details a live discussion with Ross Scott about the Stop Killing Games movement, which is trying to make sure games remain playable after publishers turn off the servers that support them. Scott framed the problem as long-standing and said the industry has normalized access disappearing with little warning.
The core issue is straightforward: when a game depends on publisher-run online services, a shutdown can effectively erase the product for everyone who bought it. That has obvious implications for live-service planning, backend architecture, and how much of a game’s value is tied to infrastructure the studio may not control forever.
Scott’s argument is also a preservation one. He compared the practice to other consumer products where access would not be revoked on a whim, and said the lack of action is part of why he felt compelled to help organize the movement. For developers, the debate touches on end-of-life support, offline fallback modes, and whether games should be designed with a survivable sunset path from day one.
The broader pressure here is likely to keep building as more games rely on always-online systems. Even teams that never expect to run a title indefinitely may need to think harder about decommissioning plans, server handoff options, and what players can still do once official support ends.
“intolerable a decade and a half ago”
- what
- Ross Scott discussed the Stop Killing Games movement and its goal of preserving access to games after server shutdowns.
- who
- Ross Scott, Ars Technica Senior Gaming Editor Kyle Orland, and the Stop Killing Games movement.
- when
- The live discussion took place this week.
- impact
- Live-service and online-dependent games may need better end-of-life plans, offline modes, or preservation strategies.
Raises preservation concerns, but pushes better planning.
Follow game preservation updates
See relevant stories in your personalized news feed.
Discussion