Stop Killing Games Is Really About Dedicated Servers

Where the campaign actually stands in 2026

"Stop Killing Games" started as a one-man crusade. Ross Scott, who runs the YouTube channel Accursed Farms, kicked it off after Ubisoft's shutdown of The Crew demonstrated that a game you paid full price for could be deleted from existence by a server switch. Three years later it is one of the most-signed consumer-rights movements in EU history, and the autocomplete searches tell you people are genuinely confused about where it landed: "what happened to stop killing games," "ubisoft responds to stop killing games," "the end of stop killing games." So here is the factual status, because the rumor that it "failed" is wrong.

The European Citizens' Initiative, formally titled "Stop Destroying Videogames," cleared verification with 1,294,188 valid signatures out of roughly 1.45 million collected, announced in January 2026. It was formally submitted to the European Commission on February 23, 2026. The European Parliament held a public hearing on April 16, 2026, run jointly by its internal-market, legal-affairs, and petitions committees, and a plenary discussion followed on May 21 in which, notably, not a single MEP spoke against it (the politics of that fight are covered in Stop Killing Games is winning in Brussels). The Commission is now obligated to issue a formal response within its mandated six-month window (mid-2026), which is the gate that decides whether actual legislation gets drafted.

None of that is "dead." A successful initiative does not automatically become law, the Commission can decline to legislate, but a million-plus-signature initiative with a Parliament hearing behind it is exactly the kind of pressure that moves consumer-protection rules in the EU. And it is not happening in isolation.

Why The Crew is the test case

The Crew is the perfect martyr for this cause precisely because of how it was built. It was an always-online racing game: even the single-player campaign authenticated against Ubisoft's servers on every launch. There was no offline mode, no LAN mode, and crucially no dedicated server software anyone outside Ubisoft could run. When the servers were switched off on March 31, 2024, every copy on every hard drive on earth became a coaster. Not degraded. Not multiplayer-only. Completely non-functional, including the parts that never needed other players.

On March 31, 2026, exactly two years after the shutdown, the French consumer-rights group UFC-Que Choisir, with backing from Stop Killing Games, sued Ubisoft. The core allegation is that Ubisoft misled buyers about the permanence of something sold as a purchase rather than a rental. The suit asks the court to strike down contract clauses that let a publisher disable a purchased game without warning or recourse. We covered the legal mechanics of that case separately in the Ubisoft preservation test case; what matters here is the engineering lesson underneath it. The Crew could not be preserved by anyone, at any price, because the architecture left no seam for the community to grab. There was nothing to hand over.

Contrast that with a game that ships a dedicated server. When a survival game's publisher loses interest, the game does not die, because the thing that runs the world is a binary already sitting on thousands of community machines. That is the entire distinction the movement is circling, even when the conversation gets framed in the language of law and ownership.

The four asks, and the one that is technical

A persistent myth, repeated by critics including some prominent developers, is that the campaign demands publishers keep servers running forever. It does not. The actual position is narrower and more reasonable: when you end official support, leave the game in a reasonably playable state, or provide the means for others to. In practice that maps to a handful of concrete policy ideas:

• An end-of-life plan disclosed up front, so buyers know whether a game becomes unplayable when support ends.
• An offline patch or standalone build for games that can function without a live service.
• Release or escrow of server software so the community can host the game after the publisher stops.
• Honest labeling at the point of sale, distinguishing a permanent purchase from a time-limited license.

Three of those four are legal and disclosure questions. The third one, server software, is the only one that is purely technical, and it is the one that actually determines whether a multiplayer game can outlive its publisher. You cannot offline-patch a game whose entire logic lives on a server you do not control. The only durable preservation mechanism for an online game is the dedicated server binary in community hands. Escrow is just the legal wrapper that guarantees it gets released.

The games that already comply

Here is the part the headlines miss. An entire genre already does the thing Stop Killing Games is asking for, voluntarily, because it is how the genre works. Survival and sandbox games ship dedicated server software as a standard feature. The world runs on hardware the player controls, and the save sits on the player's disk, a point we made in who owns your game server save. A publisher decision cannot reach into your hard drive and delete the world.

The pattern is stark. Every game in that table that ships a server binary is, by the movement's own definition, already preserved. None of them needed a law. They are not more ethical companies, they simply chose an architecture, dedicated servers, that happens to make their games shutdown-proof as a side effect. The games that fail the test are the ones built as live services with the server logic locked away.

This is why the framing matters. "Stop Killing Games" sounds like a fight against publishers. Operationally, it is an argument for a specific technical pattern: ship the server. The survival-game scene has been quietly demonstrating the solution for fifteen years.

What a good end-of-life plan looks like

If you are a studio that built an online game and you want to be on the right side of this, the playbook is not complicated, and it is cheap relative to the goodwill it buys. When you sunset official servers:

• Release the dedicated server build. Even an unsupported, "use at your own risk" binary lets communities keep the lights on. You do not have to maintain it. You have to not delete it.
• Document the save and config format. A world is only portable if people can read it. The games that survive longest are the ones whose save files and server configs are legible, which is exactly the leverage players hold over their own data.
• Publish the network protocol or unlock LAN. A game that can bind to a local address is a game that cannot be remotely killed.
• Escrow the server code where release is not possible. If licensing or middleware blocks an open release, escrow is the compromise: the code is held by a third party and released on a defined trigger, such as official-server shutdown.

This is the same reason hosting quality varies so much between live-service games and self-hostable ones. When the server is a community artifact, an ecosystem of hosts, tools, and documentation grows around it. When it is a guarded internal service, there is nothing for that ecosystem to form around, and the game is one corporate decision away from oblivion. We track that quality gap across the market in the game server hosting radar.

The California parallel

The EU initiative is the loudest front, but it is not the only one. A California bill backed by the Stop Killing Games campaign advanced through committee in 2026 and is heading toward a full assembly vote, and the Reddit thread announcing it cleared the hurdle drew thousands of upvotes and hundreds of comments, a sign the appetite is not confined to Europe. The California approach is more prescriptive than the EU initiative: it leans toward requirements like advance notice before a discontinuation, clear disclosure of what stops working, and either an offline option, a standalone version, or a refund, with the rules applying to games published after a cutoff date rather than retroactively.

Whether either effort becomes binding law is genuinely uncertain, and honest coverage should say so. The EU Commission can decline to legislate after its July response. The California bill still has to survive a full vote and a signature. But the direction of travel is unmistakable: regulators on two continents are now treating "the publisher can delete your purchase" as a consumer-protection problem rather than a fact of life. Studios that ship dedicated servers are simply ahead of whatever rule lands.

What it means for players right now

You do not have to wait for a court or a parliament to protect your own library. The single most reliable signal that a game will still be playable in ten years is whether it ships a dedicated server you can run yourself. That is not a guess about a company's intentions, it is a property of the software you can verify before you buy.

Practically: prefer games with dedicated server support for anything you want to keep. When you run one, keep your own backups of the save and config, because the value of a self-hostable game is only realized if you actually hold the data. And treat "always-online, no offline mode" as the warning label it is, because that is the exact architecture that turned The Crew into a two-year-old cautionary tale and a live lawsuit. The preservation fight is being argued in Brussels and Sacramento, but it is won or lost in the build settings, on the day a studio decides whether or not to ship the server.

Related reading

• Stop Killing Games Is Winning in Brussels: The Political Fight
• The Ubisoft The Crew Lawsuit: Server Preservation's Test Case
• Who Owns Your Game Server Save?
• The Game Server Hosting Radar
• ARK: Survival Ascended Dedicated Server in 2026
• The Game Host Trust Gap