The post says the Stop Killing Games movement does not go far enough. Instead of merely asking publishers to keep discontinued games playable, it argues that games should satisfy the classic free software freedoms, including the right to inspect code, modify it, and redistribute copies, with special emphasis on server software for multiplayer titles. The core claim is that games die because users never really control the software in the first place, especially when publishers can shut off servers, lock down clients with DRM, or prohibit fan-run replacements.
For tech leaders, this is a familiar platform-control fight in game form: if products depend on opaque hosted backends and restrictive licensing, preservation, ownership, and customer trust become liabilities that regulation will eventually try to unwind.
Sympathetic to game preservation and hostile to remotely killable products, but skeptical of the post itself because it overreaches into free-software absolutism, reads like AI-generated writing to many, and glosses over how hard modern multiplayer backends are to preserve or release.
01 Modern live-service backends are not cleanly separable products you can zip up at end of life.
They are entangled with licensed middleware like Wwise, Havok, Photon, Bink, platform SDKs, anti-cheat assumptions, and backend designs built for giant shared worlds, persistent economies, and matchmaking. Requiring post-shutdown playability would push studios to architect games around detachable server models from day one, which means fewer features and less ambitious online designs rather than a simple legal compliance step.
For many multiplayer games, preservation is an upfront architecture choice, not an end-of-life patch. If regulation lands here, it will shape what kinds of games get funded and built.
02 Community-hostable multiplayer is not some lost ancient art.
Descent 3, Minecraft, and Counter-Strike 2 show that games can remain playable for decades when hosting is decentralized and failure of the official service is not fatal. That reframes the issue from "impossible technical burden" to "designs changed because publishers preferred control, monetization, and anti-cheat tradeoffs."
A lot of preservation risk was designed in, not discovered later. The old dedicated-server model still works when companies choose it.
03 The cleanest technical compromise is splitting engine code from proprietary assets.
Projects like OpenMW, OpenGothic, fheroes2, and the Doom engine model show how a free reimplementation can keep games alive without giving away the art, music, or original data files. That does not solve every legal or economic issue, but it weakens the claim that preservation must mean full public-domain release of the whole game package.
There is already a workable preservation pattern where code becomes portable and maintainable while commercial assets stay controlled. That is a much narrower and more realistic target than mandatory free redistribution of everything.
04 The strongest consumer argument was about packaging and disclosure, not ideology.
If a game depends on continuing hosted service, selling it as a one-time purchase is misleading unless the shutdown terms are explicit or there is an end-of-life fallback. Several people said the honest model is subscription pricing for genuine services and product pricing for software that remains usable after support ends.
The product versus service distinction is doing most of the moral work here. If companies want service economics, they should stop marketing the thing as durable ownership.
01 Mandating free redistribution or source release would blow up the economics of commercial game production.
Commenters arguing this point were not objecting to preservation itself. They were objecting to the article's leap from "keep sold games usable" to a model where one buyer can legally copy the game for everyone else, which they see as incompatible with funding large studios and high-budget titles.
Preservation rules and free-software rules are not the same thing. Conflating them makes the policy much easier to attack.
02 Open-source success stories in games are weaker than free-software advocates suggest.
One commenter with AAA experience argued that prominent examples often rely on proprietary control during the commercial window, donations that do not cover wages, or business models that fail to support full teams. That turns "games can be free" from a proof into a niche exception.
There are examples of open games, but not many that clearly fund mainstream production at scale. That matters if the policy goal is industry-wide behavior change.
03 Some commenters think new legislation is the wrong tool because the actual problem is disclosure and contract clarity.
In this view, companies should be allowed to sell server-dependent software if they clearly state the dependency and lifetime, and ordinary fraud or consumer law should handle misrepresentation. The burden should be on buyers to value these products correctly, not on governments to prescribe software architecture.
A disclosure-first regime would preserve business flexibility while attacking the worst deception. It would do less for preservation, but it is politically and legally simpler.