Perthro
Back to blog

Stop Killing Games and the problem of memory

A preservation bill passed a California Assembly vote this week. The fight is legal, practical, and quietly personal.

The California State Assembly passed the Protect Our Games Act this week, 43 to 16, according to Eurogamer. The bill now heads to the California State Senate. If it becomes law, companies behind server-dependent games would need to give players advance notice before shutdown and provide some workable way to keep a purchased game playable afterward, such as offline access or community servers.

That sounds dry until you remember what started this. The Crew was sold, played, delisted, shut down, and then effectively removed from owners' libraries because the game depended on servers even for parts people experienced alone. The Stop Killing Games campaign grew out of that very specific frustration. Players were not asking for every multiplayer service to live forever. They were asking a simpler question: if I bought this thing, why can it vanish so completely?

This is a legal argument, sure. It is also a memory argument.

A game can be over without being gone

There is a healthy version of an ending. PC Gamer reported this weekend that Wube Software sees Factorio's coming 2.1 patch as its last major update, with the studio moving to bug fixes, platform support, compatibility, and modding support after that. That feels almost old-fashioned now. A studio says: we made the game, expanded it, polished it, and now active gameplay development can conclude.

Nobody has to love that decision. Some players always want one more patch, one more planet, one more reason to come back. Still, there is a difference between a game reaching a final shape and a game being switched off from the outside. Factorio can stop growing and remain playable. That distinction matters.

Games are strange objects because they are both software and places. You can finish a book, put it on a shelf, and know what happened. You can finish a film and still have the disc, the file, or at least the memory of sitting through it. With games, especially online games, the thing itself can depend on a distant machine you never see. When that machine goes away, the place goes with it.

Sometimes that is unavoidable. A live competitive game with matchmaking, anti-cheat, licensed content, and constant server costs is not the same as a cartridge on a shelf. Pretending otherwise helps nobody. But the hard cases should not erase the obvious ones. If a game has a single-player campaign, or a local mode, or enough structure to work without central servers, players are right to ask why the end of support has to mean total disappearance.

The June pile makes the problem easier to ignore

The timing is a little funny. On the same weekend that preservation was back in the news, the release calendar was doing its usual trick: filling the room until nobody can hear themselves think. Nintendo Life's June Switch roundup pointed to Final Fantasy VII Rebirth for Switch 2, Tetris: The Grand Master 4, Solarpunk, to a T, Starseeker: Astroneer Expeditions, Wanderstop, and more. The last30days scan we ran also found fresh YouTube roundups focused on June cozy games and May indie releases.

That is the normal rhythm now. A game arrives, gets a launch trailer, gets streamed for a week, gets filed into a sale pile, and then another ten arrive. There is nothing wrong with abundance. I like abundance. I like the slightly ridiculous feeling of opening a storefront and seeing too many good things. But abundance can make loss feel less urgent. Why worry about the dead game when there are eleven new ones on Switch next month?

Because the dead game was once new too.

Every game that disappears had a launch window. It had screenshots, wishlist buttons, Discord excitement, people arguing about the price, someone taking the day off work, someone getting through a bad week because the driving felt good or the co-op night was funny. Then, years later, the conversation gets smaller. A shutdown notice appears. The publisher says thank you for your support. The servers go dark. If players are lucky, there is an offline patch. If they are unlucky, there is a hole where the game used to be.

That hole reaches past access. It changes how we remember our own play. I can remember games I finished badly better than games I loved but never wrote anything about. A boss I beat at 2 a.m. leaves less trace than a two-sentence note I made the next morning. The record is not the same as the game, but it helps. It gives the experience a second place to live.

Ownership has become a feeling you have to defend

One reason this debate gets heated is that everyone is using the same word for different things. Buy. Own. License. Access. Library. Those words get flattened inside a store button. A player sees a price, pays it, and watches the game appear in a library. The law may say one thing. The interface says another.

Publishers are not villains for needing to shut down services. Teams move on. Technology ages. Middleware breaks. Contracts expire. The ESA's objection, quoted by Eurogamer, is basically that strict shutdown rules could push developers to spend limited resources on old systems instead of new work. That is not a fake concern. Small studios especially do not have infinite time to maintain everything forever.

But players are not being unreasonable either. The industry spent years teaching people that digital libraries were libraries. It made ownership feel clean and permanent because that made digital buying easier. Now the bill is coming due. If a purchased game can become useless later, the store page should say so plainly. If there is a realistic end-of-life plan, it should exist before the shutdown notice. If the game can be patched into an offline state, it should not take a consumer campaign to make that happen.

The uncomfortable middle is probably where the real work sits. Not every game can be preserved in the same way. Not every server can be kept alive. Not every license can be unwound neatly. Fine. Then be specific. Tell players what they are buying. Tell them what depends on servers. Tell them what happens when support ends. Treat the end of a game as part of the product's life, not as a public-relations problem to manage after the fact.

The record around the game matters too

Perthro cannot keep a shut-down game alive. We should be honest about that. An iPhone journal is not an offline patch, a community server tool, or a legal remedy. What it can do is help you keep your side of the story intact: what you played, what you shelved, what you planned to play, what you rated, what you wrote down when the memory was still warm.

That is one reason the app cares about more than a single score. A five-star rating is useful, but it is thin by itself. A review, even a messy one, carries more weather. A backlog or wishlist says something about intention. A custom list can hold a year, a friendship, a genre phase, a run of games you meant to revisit. Library imports from Steam, PlayStation Network, and Xbox Live help pull scattered histories into one place, but the point is not just collection. The point is giving your play a shape you can come back to.

When people talk about game preservation, they usually mean code, servers, builds, source files, executable things. That is the foundation. Without the game, the rest is commentary. But the commentary matters too. Forums, reviews, screenshots, save files, lists, half-remembered co-op stories, all of it becomes part of the cultural afterimage of a game.

A game can disappear twice. First when it becomes unplayable. Again when everyone stops being able to explain why it mattered.

The better ending is boring, and that is fine

I hope the Stop Killing Games fight pushes the industry toward boring, practical habits. Clear store disclosures. Offline modes where possible. Community server options where reasonable. Refund rules when a product becomes unusable. End-of-life plans that are written before the last angry week.

None of that sounds glamorous. Good. The best version of preservation is probably not dramatic. It is paperwork, patches, export buttons, server binaries, plain language, and a little humility about what players thought they were buying.

Games deserve endings that make sense. Some will keep growing for years. Some will stop, like Factorio seems ready to, because the work has reached a good resting place. Some online worlds will close because they cannot be carried forever. But there is a big difference between turning off the lights after everyone has had a chance to leave, and locking the door while people's memories are still inside.

That difference is what this week's California vote is really about. Not nostalgia as a policy platform. Not the fantasy that every game can live forever. Just the modest idea that when people buy a game, invest time in it, and make it part of their lives, the ending should not feel like a trapdoor.