HN Debrief

Stop Killing Games fails to secure EU law despite 1.3M signatures

  • Gaming
  • Regulation
  • Consumer Protection
  • Software Architecture
  • Europe

The article reports that Stop Killing Games, a campaign aimed at preventing publishers from selling games and later rendering them unusable by shutting down required servers, cleared the EU petition threshold with 1.3 million signatures but still failed to get the European Commission to propose legislation. The Commission called a blanket legal duty to keep games playable disproportionate and pointed to intellectual property, business confidentiality, cost, and security concerns. That sounds like a hard rejection if you only know the headline, but the important context is that this EU citizen initiative process does not create law. It forces a formal answer. Several commenters said the campaign expected exactly this outcome and had already moved its effort toward Parliament, where 45 Members of the European Parliament have reportedly backed a legislative call tied to the upcoming Digital Fairness Act.

Do not read this as the end of the issue. If you build or sell software that depends on remote services, watch the Digital Fairness Act and start thinking now about end-of-life promises, offline modes, self-hosting, and clearer product labeling.

Discussion mood

Mostly frustrated and cynical about the Commission, with many people treating the response as industry-friendly and heavily shaped by lobbying. At the same time, the better comments were not triumphalist about SKG and focused on the hard part ahead: writing a narrow law that protects buyers without turning vague preservation goals into costly compliance traps for developers.

Key insights

  1. 01

    The petition was never the main battlefield

    The EU citizen initiative was a forcing function, not a direct path to legislation. Clearing the signature threshold guaranteed a formal Commission response, and Stop Killing Games appears to have planned for a rejection while building support in Parliament and tying the issue to the wider Digital Fairness Act. That changes the story from "1.3 million people lost" to "the venue shifted to the place where actual lawmaking can happen."

    Track the Digital Fairness Act, not just the petition headlines. If this issue affects your business, Parliament and its amendments are where the concrete obligations are likely to emerge.

      Attribution:
    • madanparas #1
    • hodgehog11 #1
    • rookderby #1
  2. 02

    The proposal still lacks the legal shape to survive Brussels

    The core consumer complaint is easy to grasp, but several comments pointed out that SKG came in with a movement frame, not a compromise-ready legislative package. In the EU process, vague goals like keeping games "playable" leave too much room for industry to attack edge cases, costs, and definitions. Without a narrower scope, clearer terms, and likely carveouts for smaller studios, lawmakers get an easy excuse to say the idea is directionally appealing but not fit for drafting.

    If you want a regulation to pass, define terms before your opponents do. For any advocacy or policy work around software, write the operational definitions and exemptions early or expect the process to stall on ambiguity.

      Attribution:
    • reedf1 #1
    • Timon3 #1
    • hobofan #1
  3. 03

    Modern game backends are not just one server binary

    Developers with backend experience added a useful reality check. Some games really could be preserved by releasing a server executable, but others depend on matchmaking, player data, voice, cloud databases, event pipelines, and managed services such as PlayFab, AWS, Kafka, or third-party networking layers. For those games, "just let players host it" can mean redesigning the product from the start, not flipping a switch at shutdown. That does not kill the consumer case, but it does mean the eventual law will end up shaping architecture choices for future games.

    If your product depends on hosted services, treat end-of-life as an architecture requirement, not a legal afterthought. Map which dependencies block redistribution or self-hosting now, before regulation or customer pressure forces the issue.

      Attribution:
    • maccard #1 #2 #3
    • 59nadir #1
  4. 04

    Supporters are really arguing for future design constraints

    The more technically coherent defense of SKG was not "preserve every game exactly as it exists today." It was "for future games, require an end-of-life plan from day one." That could mean avoiding cloud-only dependencies where they are unnecessary, keeping single-player logic local, or making multiplayer degrade to LAN, direct connect, or community hosting. The important shift is that the burden moves from heroic preservation at shutdown to ordinary design discipline at the start.

    This is the same pattern seen in privacy and accessibility rules. Teams that build for the requirement up front absorb far less pain than teams that assume they can retrofit it later.

      Attribution:
    • roblabla #1 #2 #3
    • sensanaty #1
  5. 05

    Clear labeling may be the politically viable middle ground

    A recurring practical idea was to classify games more honestly at purchase time. Instead of pretending all game purchases are equivalent, publishers could be required to disclose whether a title works offline, how long online functionality is guaranteed, whether saves are exportable, and whether the buyer is getting a durable copy or time-limited access to a service. That framing sidesteps the hardest preservation arguments and turns the issue into consumer disclosure and refund policy, which is a much more familiar regulatory lane.

    Expect software sales rules to move toward labeling and service-life disclosure before they move toward broad preservation mandates. Product pages, terms, and save-data portability are low-hanging places to get ahead of that shift.

      Attribution:
    • rafterydj #1
    • butz #1
    • necovek #1
    • magicalhippo #1
  6. 06

    Reverse engineers already keep many dead games alive

    People who have actually reverse engineered shipped games argued that the industry's impossibility claims are overstated. A lot of games can be revived to some extent without source code, and common engines like Unreal often leave enough intact for preservation unless developers deliberately strip or harden server-side pieces. Anti-tamper systems such as Denuvo make revival slower and messier, but not necessarily impossible. That weakens the claim that shutdown always reflects unavoidable technical reality.

    If preserving a product matters to your users, you do not want the unofficial recovery path to depend on reverse engineering and anti-tamper workarounds. Building an official fallback is cheaper reputationally and often technically simpler than fighting your own community after shutdown.

      Attribution:
    • systemdev #1 #2

Against the grain

  1. 01

    Consumers can solve this by refusing the product

    A minority view held that this is not a fit subject for state intervention at all. If buyers dislike live service games, online-only single-player titles, or revocable access, they can stop purchasing them and let the market punish publishers. That argument matters because it rejects the whole premise that software sales need a new legal category here, and it frames SKG as paternalism rather than consumer protection.

    Do not assume broad public support for preservation rules just because the consumer complaint sounds intuitive. Any proposal will need to justify why ordinary disclosure and buyer choice are not enough.

      Attribution:
    • canthonytucci #1
    • mvdtnz #1
    • akramachamarei #1
    • skotobaza #1
  2. 02

    The burden may land hardest on small studios

    Several developers pushed back on the idea that only Ubisoft-scale publishers would feel this. Small and mid-sized teams often lean hardest on managed networking, matchmaking, voice, analytics, and platform services because they cannot afford to build them in-house. If regulation is written broadly, the teams with the least legal and engineering slack may bear the highest proportional cost, while big publishers adapt or route liability around it.

    If regulation advances, watch for revenue thresholds, scope limits, or exemptions tied to game type and studio size. Without them, the rule could entrench incumbents rather than discipline them.

      Attribution:
    • maccard #1
    • hobofan #1 #2 #3
  3. 03

    Disclosure rules could become another dark-pattern checkbox

    Not everyone bought the labeling compromise. One objection was that publishers would happily add a token subscription, a broad rental label, or a tiny print support promise that preserves the business model while making the buying experience even worse. That criticism is useful because it highlights the gap between informing consumers and actually constraining seller behavior.

    If you rely on disclosure as the fix, pair it with enforceable minimum standards or refund rights. Otherwise the market may just absorb the label and keep moving.

      Attribution:
    • brokensegue #1
    • skotobaza #1

In plain english

AWS
Amazon Web Services, a large cloud computing platform that provides hosted infrastructure and managed services.
Denuvo
A commercial anti-tamper and digital rights management system used in games to make modification and cracking harder.
Digital Fairness Act
A planned EU consumer protection initiative focused on fairness in digital markets and online products.
EU
European Union, the political and economic bloc whose institutions can create rules that apply across member countries.
LAN
Local Area Network, a way for devices on the same local network to connect directly without relying on an internet service.
SKG
Stop Killing Games, a campaign that argues publishers should not be able to make purchased video games unusable by shutting down required services.

Reference links

Policy and legislative context

  • Digital Fairness Act
    Background on the broader EU initiative many commenters said is now the real path for game preservation rules.

Talks and videos

Technical references and tools

  • Photon Engine
    Referenced repeatedly as an example of a managed multiplayer stack that may complicate self-hosting or end-of-life preservation.
  • Photon product selection documentation
    Linked to argue over whether Photon Fusion supports a preservation-friendly networking model.
  • AmongUsP2P
    Example of a community project showing that a popular social game can be adapted toward peer-to-peer play.

Related background examples