← Back to context

Comment by phyzix5761

10 hours ago

So now it becomes way more expensive for small studios to come out with games that have online features. This is a huge win for big studios who will suck up all that market share.

Handing over a standalone server to the public is a massive engineering, financial, and legal headache. Modern multiplayer games rarely run on a single isolated program. They rely on a huge network of interconnected cloud microservices.

A single match might require separate proprietary systems for matchmaking, player inventories, anti cheat, metrics tracking, and database management. Many of those come with licenses that don't allow you to just give away the code for free.

Disentangling the actual game logic from these third party platforms like AWS or Epic Online Services requires months of rewriting code. At that point you're basically re-inventing the wheel on so many technologies that your costs go up exponentially.

Games are rarely built entirely from scratch by a single company and are usually packed with licensed third party software like proprietary network code, commercial physics engines, or specific anti cheat software. Because the studio doesn't own the rights to distribute these proprietary tools to the public for free then releasing a standalone server forces them to spend extensive legal and development hours stripping out the restricted code and replacing it with open source alternatives.

Releasing server code also exposes the inner workings of the company's technology. If a studio uses the same proprietary engine or backend framework for their active money making games then releasing the server code for a dead game essentially hands hackers and competitors a roadmap to exploit their current profitable titles.

Does it though? Just release the a standalone server once the game is done making money.

  • Updated my original post to explain why this wouldn't work.

    • Somehow I highly doubt that a small game company is going to run a "huge network of interconnected cloud services". I've also yet to find a small game company running their own big online multiplayer game.

      1 reply →

    • Your argument still doesn't hold, sorry. The law won't apply retroactively so the existing games can be killed. However, if the law passes, the EOL plan just becomes another product requirement you have to plan for. So you won't "rewrite" the server code, you write it to comply in the first place.

      This was also the excuse people gave for GDPR and California's privacy law and everybody got forced into complying after the date of validity. Simply having an "excuse" of money loss due to engineering your game user-hostile in the first place (especially after the law became valid) isn't a good argument. It will have some preparation time and if you didn't plan for it, it is your fault.

Counter-Strike: Global Offensive was a game running all of these things (matchmaking, skins, anticheat ...). After Counter-Strike 2 was released, the servers for CS:GO were shut down. Yet, the game remains mostly playable. Sure, the skins no longer work and there's no official matchmaking, but third parties have stepped up. That's because Valve released (and have always released) server software.

I find this argument quite bad. It was done in the past and it's still being done today. There's nothing preventing any company from doing it except for a combination of laziness and greed.

  • CS:GO's server architecture makes perfect sense for a game that would be easy to release server software.

    What do you do for, say, a failing MMO built on a proprietary game engine you're trying to make a sequel for?

> Releasing server code also exposes the inner workings of the company's technology.

And yet releasing standalone servers back in the 00s was the norm, rather than the exception. I don't buy the argument.

  • What you're noticing - that companies suddenly started closed-sourcing their server code, isn't just something that happened for no reason. Internet connections got fast, and it enabled more complex games like MMORPGs and MOBAs which are an order of magnitude more complex than the shooter games you're probably thinking of (Quake III?)

    A LOT of architectural thinking goes into scaling MMORPGs, and it starts at the data model. I've watched quite a few interviews with WoW devs, and the data model for their system is counter-intuitive. That constitutes a trade secret in my mind.

    And that's something that companies that produce MMORPGs/MOBAs/etc. can conclusively demonstrate in court.

    That said, it's possible that companies could release a "nerfed" version of their server code with trade secrets removed for the community to run once the official game servers are taken down. It isn't clear if that'll be in scope of the law, or if that's even what proponents of Stop Killing Games would be okay with. We'll have to see.

    • This whole thing doesn't apply to MMORPGs to begin with because they're all already subscription based. If I understand the main grievance correctly, the problem is giving the consumers the wrong impression they're making a normal one-time-payment PURCHASE and then rendering the item they purchased unusable later.