more like slop killing games amirite
Now, every time I post that somewhere public like a YouTube comments section, someone tells me that I'm an idiot for thinking that that's what SKG is about.
They always quote the same talking points to me:
- The law would only affect future games, not games that already exist.
- There are multiple ways to make a centralized multiplayer game work forever after its servers need to shut down for whatever reason.
- Every game must be preserved forever, even though we're specifically asking for games to be changed in non-trivial ways when they shut down, at any cost, as long as it's only to the game developer.
Now, anyone who has ever developed a piece of software or organized any kind of anything is probably thinking about how vague and contradictory "keep it running forever after it must stop running" is.
The game that this campaign was started about is The Crew, a Ubisoft racing MMO that ran for ten years and was discontinued because renewing the licensing for the cars would have been more expensive than the amount of money the game would likely make over the next decade.
That leaves two possibilities if shutting down the game is not an option:
- force Ubisoft to pay for the car design licensing and run the servers forever at a loss
- modify the game in some very significant ways and release the modified version to owners for free
The first option has a pretty simple workaround that pretty much any company that makes multiplayer games would always choose to do because the alternative is losing money forever:
Spin up a new company every time you're releasing a new game that requires servers of any kind, then file for bankruptcy and dissolve the company when you need to shut down the servers.
The end result is that the only change is that a lawyer somewhere gets a little bit of money from the company at some point long after the game's release.
The second option is not game preservation. The entire point of The Crew is that the cars you're racing against other real people are real cars that exist in real life.
Ubisoft would, at minimum, need to remove those two things about the game if they didn't want to keep paying the licensing fees and server costs.
Which then leads to the question of what "killing" a game actually means.
Counter-Strike 2 was a massive update to Counter-Strike: Global Offensive that replaced the entire game with one made on a new engine. This was far from the first time something like this had happened. World of Warcraft: Cataclysm and RuneScape 3 were both massive changes to live service games that replaced what was there before.
Would a game developer be forced to duplicate their game and keep running both forever, splitting their playerbase, any time they wanted to make a significant change? What even counts as "significant"?
And if those three examples don't count, then at what point does it start counting? Would replacing the play button on the main menu of a game with an apology for the servers being discontinued count as a significant enough change?
A lot of the time, I see "well, they can just make it open source or let me download the server executables and call it a day" as a response to this.
Except that that's not how software development works, especially for something as complex as a multiplayer game that can be played by a million players simultaneously.
A software project of sufficient complexity will not have code that's all owned by one party, and the code isn't the whole picture.
Let's talk about this in terms of games I have personally worked on.
Alien Swarm: Reactive Drop is open source and does have downloadable game server executables. But there are definitely parts of the game and the services it uses that are closed source.
First, a lot of our players play the game on ranked servers. Ranked servers talk to a computer that's in my basement (the same one that this thread is hosted on) in order to collect the stats and hand out medals once a month.
This month, nearly 400 players have participated. That's a lot for such a small game: https://stats.reactivedrop.com/heroes/season-53
Let's, for the sake of argument, pretend that HoIAF doesn't exist. And that the anticheat and abuse reporting features don't need to exist either. That means all the remaining source code can be released, right?
Well, no.
A Source Engine game like AS:RD is built on Source Engine. Source Engine uses the Havok physics engine. Not only can we not legally include that in our public source code, Valve can't even give that source code to us.
Valve's agreement with Nvidia means that anyone who has access to that source code needs to be a contractor for Valve, including an NDA. AS:RD is public and open source, so we can't do that.
You could imagine a version of the game with physics removed and some kind of kludge to make sure the game is still completable, but at what point does removing stuff from the game turn it into a different game?
We also don't have access to the source code for most of the DLLs in the bin folder. engine.dll is a complete black box to us.
But let's ignore all of that. Let's say that just handing over the DLLs and EXEs is enough.
Which leads me to...
Spy Cards Online.
This one is completely open source. You can see everything needed to build and run the game here: https://git.lubar.me/ben/spy-cards
There's some incomplete protocol documentation, but the full source code is there, so someone else could read the source code and write their own documentation.
But people don't play Spy Cards Online for the vanilla game mode. They play it for the over a hundred community-made game modes.
There are several gigabytes of custom game mode rules and match recordings and card portraits and video game music people downloaded from YouTube hosted on that server as well.
Even just the source code is a third of a gigabyte.
And while all of this data is public and can be downloaded by whoever knows the URL to access it, most live service games also store player-specific data.
And it's not free to store and send gigabytes of data to whoever requests it.
If Spy Cards Online ever did need to shut down, any reason I can think of for that happening would also apply to hosting downloads of the source code and data.
And a live service game that actually does have persistent characters and inventories would essentially be suffering the biggest data breach ever, on purpose, because they are required to by law.
This is a very complicated process, and the more we say "well, just ignore or change that" to any road block we approach, the further we stray from the original goal of preserving a game exactly as it was.
And most importantly, all these changes are not free to make.
We're talking about a live service game that has reached end of life. The people who made it originally probably don't remember what they were doing a decade or more ago, and probably don't work at the company anymore.
The poster child for SKG, The Crew, was being discontinued because it was more expensive to keep selling it than the money selling it would have brought in.
Once we ignore all of the NDAs and legal agreements and private data, this all boils down to money.
A company could hire a team of software engineers to learn their codebase and convert their live service game into a singleplayer one with no licensed content, but that costs a lot of money and a lot of time, and also isn't game preservation.
They could also simply go out of business. Apart from some lawyer somewhere getting paid to do some paperwork, this is functionally identical to how it currently works.
I'm not saying you can't make laws that help to preserve media.
But if your entire plan is "the people in charge of making laws will figure it out", you don't have a plan.
Right now, SKG could more accurately be called "ban all multiplayer games from being developed by making it prohibitively expensive and introducing contradictory legal requirements".
Ok, let's talk about SKG a bit.
First, let's lead this off by stating something I agree with:
There are a lot of very big companies out there making live service games they plan to immediately abandon and shut down the moment it looks like the game isn't going to make them infinite money. At one point, Sony announced the cancellation of 19 different live service games they were developing simultaneously. They simply shouldn't do that.
Make games that don't cost infinity dollars for the company making them to run instead. There are a finite number of game developers in the world. Have them work on stuff that isn't going to get thrown away the moment after it's finished.