Here’s a few, as someone who has worked in games for 12 years.

Most games have code and design decisions that hark back 25+ years. Every single unreal engine game for example is based code written in the mid 2000s and some parts of the engine really feel like it. Online components are developed the same way. If you made a multiplayer game 10 years ago and it was successful, your next game is going to be built on top of that. I’ve seen places that use stored procedures in Oracle DB for gameplay logic, others that rely on any number of SQL server specific tricks. Closed source dotnet frameworks, proprietary AWS services, if you can think of it there’s probably a game shipped on it. You’re also making the assumption that the server is a neatly coupled thing.

Am I responsible for providing a fallback to EOS, or Steam, or playfab in case their services are decommissioned?

What about the licenses for the code that affects other areas - we have a GPL’ed library here that we can use but now all of a sudden the vitality of the license means we have to replace it?

Who defines “ordinary use of the game”?. If the game has a multiplayer component, to some large number of users that can construe “ordinary use”. call of Duty is the best example of this (although COD is probably one of the games with the best track record here).

This is going to result in games moving more towards the Hollywood studio model - start up a company, launch a game and wind down the company for the next project. People who rely on that already unstable industry will be given even less stability due to this.

> I have a hard time imagining the server architecture would change much

That’s great - I’m sure if it’s that little work you’re willing to do it for all of those games companies.

> A dedicated company-owned server is just a beefier home computer with load balancers and matchmaking. Drop those two, slap a server list on the client, and you're golden

Game backends are just like Other backends. Some use event queues, microservices, third party APIs, licensed components. This adds a burden that no other software is expected to carry - it’s perfectly fine for Google to drop support for their devices but a 25 person company needs to go back and fix all their old games if they want to keep selling them?

What is irrational in pointing out that this particular law, as it is written, gives the game developers a perverse incentive to further embrace more exploitive revenue models such as free to play and subscription based services? The technical implementation is irrelevant. It is the business side of things that you should actually worry about.

If anything, some people seem to have this weird faith in regulation that makes them think if some politician is promising to fix something via legislation, then it will get fixed, regardless of how the law is actually written or how it will work out in practice. California in particular is full of regulations that feel good but are either ineffective or has unintended consequences. See prop 65 which litters the state with vaguely worded warning messages that provide next to zero useful information, or prop 13 which massively disincentivizes home building and effectively makes new homeowners subsidize the property taxes of those who bought before them.

You can be supportive of regulations. I am supportive of many regulations. But I don't just support a regulation because it is great news that makes me feel warm and fluffy. I want well thought out regulations that don't neuter themselves with exemptions and don't easily lead to undesirable consequences. If this makes me an irrational anti regulation crusader, then off to Antioch, CA I shall go.

> I'm always shocked by how irrationally anti-regulation this site is.

If you wanted to trigger a HN rant, topics should always include regulation, particularly in regard to nuclear power, guns, freedom of speech or taxation.

There's so many renditions of these style bills that it's hard to keep track what's in this specific one.

From what I can tell this one doesn't include provisions to protect indie shops/solo devs. The entire time spent developing a game is a net loss until release (and probability wise, probably still a loss then). So this is adding more upfront cost to devs.

The bill text I found is also one of the more generic versions I've seen. Specifically this line

>the ordinary use of the game

This is quite broad. I've seen some supporters of this style bill push for 'offline play' being a requirement. For instance, an mmo raid may require 20 players. If after the death of the game getting 20 players is impossible, I have seen people push for ai (just the game version) so it would be possible, or a patch to make the content possible for 1. Each of which are development time that serves no benefit to making money.

There's also the likelihood of the server architecture requiring many moving pieces. Think if fortnite died tomorrow how many different servers it would take to host. Could an argument be made that an end user couldn't be expected to launch a dozen aws services? More dev time, more costs.

Now the day 1 proponents would probably focus on the obvious provide the server exe cases, but these are concerns down the line.

Also at least this one doesn't do the 'development bond' idea I've seen to protect against the entity going bankrupt, essentially requiring every dev to pay for some sort of insurance before releasing the game (more costs for indie devs).

I would describe them as pessimistic rather than irrational. They just believe that instead of going with an option like you proposed, companies will push toward unregulated options.

Since I don't know their backgrounds and don't have any background working with video game company executives it's hard to tell which options are more likely.

Its because people are brainwashed by techno capitalists propganada and think they're going be in the "startup" founder position one day and thus defend the people currently in those positions no matter what, thinking their protecting their own interests (and its almost always the opposite).

There's nothing wrong with having an ambitious attitude, but why not be ambitious seek to build a better tech-biz ecosystem that is actually pro consumer and pro human..

People seem to think there's only one way, and that way is letting capital owners behave however they want incase they're also in that position one day.

It’s not irrational, the comments literally explain in great detail the downsides of the regulation.

For example one commenter in this thread said:

>See also car fuel economy standards that push car makers into killing the wagon market segment in favor of SUVs.

This is an objectively true and prove-able statement. What is irrational about that?

WRT regulation the only thing that matters is the incentives that it creates.

>If this is how the bill ends up being enacted, it will only push more big game developers into making their titles subscription only.

This is a valid concern and a real incentive if that’s how the law works. What is irrational about this argument?