The post takes the consumer anger behind Stop Killing Games and reframes it as a free-software issue. Instead of focusing on narrow preservation rules for abandoned or shut-down games, it argues that players should have the classic software freedoms to run, study, modify, and redistribute games, including the server side of multiplayer titles. That is a much bigger claim than the campaign usually makes. It turns a complaint about dead purchases into an argument against proprietary software itself.
Most readers thought that leap was the core mistake. The useful consensus was narrower and more concrete: there is a real problem when publishers sell a one-time purchase that later becomes unusable because of avoidable server dependencies,
DRM, or shutdown decisions. Many people were fine with forcing clearer disclosures, offline fallbacks, refunds, or some way for communities to keep a discontinued game running. They were not fine with treating that as proof that all games should become
free software. Several comments pointed out that the article blurs code, assets, trademarks, server operations, and copyright into one bucket when they are not the same thing legally or economically.
The longest, highest-signal discussion came from game developers pushing back on the idea that end-of-life preservation is just a matter of tossing players a server binary. Modern online games often depend on licensed
middleware, internal systems, cloud services,
anti-cheat assumptions, and tightly coupled backend logic that was never designed to be disentangled. Releasing something runnable at shutdown can require architectural work from the start, not a cleanup pass at the end. The practical takeaway was not that preservation is impossible. It was that the cost shows up early, in product and architecture decisions, and will push some teams toward simpler multiplayer designs, community-hostable servers, or away from online-only mechanics entirely.
That led to the strongest pro-SKG framing in the comments: this is exactly the point. Older games routinely survived because they exposed dedicated servers,
LAN play, or direct connections. A lot of modern games die because publishers chose designs that maximize control, monetization, and anti-piracy leverage, not because multiplayer preservation is inherently unsolved. On that view, regulation would not kill multiplayer. It would penalize a specific style of tightly controlled live-service game and reward designs that remain functional after official support ends.
The mood was skeptical of the article, not of the underlying preservation problem. People were annoyed by its free-software absolutism and by what many called obvious AI-written prose. But beneath that, there was broad agreement that selling a game as a product and later turning it into a dead icon is a bad model, and that future rules will likely hinge on whether games are marketed as durable purchases or time-bounded services.
jxself.org