Stop Killing Games

“Stop Killing Games” is pushing for EU-wide rules to prevent publishers from intentionally making purchased games unplayable when online support ends—especially when the game depends on publisher-controlled servers. The core claim behind the activism is straightforward: cutting off “life support” after a sale amounts to an assault on customer rights and media preservation, because players effectively lose access to something they already paid for.

Supporters frame the practice as increasingly common in modern live-service and online-reliant titles. A key example cited is Ubisoft’s The Crew, described as having a player base of at least 12 million, which was later “destroyed for all players.” The argument is that if publishers can do this without consequences, the behavior will spread across the industry. The initiative also emphasizes that the legality is currently murky in many places, with governments lacking clear laws and license terms often failing to override national consumer-protection rules.

The debate then shifts from principle to implementation—where the biggest friction appears. Activists say they are not asking companies to run servers forever. Instead, they want an “end-of-life plan” that keeps games playable on consumer systems after support ends, typically by requiring publishers to provide a pathway such as protocols, patches, or server-related components so the community (or others) can operate the game without ongoing publisher hosting.

Critics—especially game developers—argue that this is far harder than it sounds. Online games often rely on complex server logic, real-time networking, proprietary systems, and security-sensitive infrastructure. Even if a law requires only a “thin support layer,” opponents warn that publishers will still face major engineering work, and that the line between what must be released versus what can remain proprietary will be contentious. There’s also concern about “malicious compliance,” where companies follow vague requirements in ways that technically satisfy the law but don’t solve the underlying problem—analogized to salary-range disclosure rules that can be gamed.

Another major worry is that broad rules could spill into other software categories. Because SaaS and web services follow similar patterns—remote dependencies, hosted backends, and subscription access—developers fear the same obligations could migrate from games into web development, raising costs and slowing innovation.

The transcript also highlights a political critique: the language is viewed as too vague, potentially giving politicians “easy wins” without fully understanding the technical realities. That vagueness, critics say, could harm indie developers and lead to fewer games overall. Even some who dislike live-service shutdowns argue the most workable version would be narrowly targeted—such as applying to games explicitly sold and marketed as single-player—while still allowing publishers to end support.

Overall, the central tension is whether consumer-rights and preservation goals can be achieved with precise, enforceable technical requirements—or whether the current proposal risks unintended consequences, loopholes, and industry-wide ripple effects.