Ensuring that the multiplayer server component of your game is a standalone end-user distributable is a huge task to impose on every game that wants to have a multiplayer component. Especially once you consider the vast majority of games that never even get traction much less turn a profit.
So, the second someone buys your prerelease indie slither.io game, what exactly does this checklist look like? It needs to also day 1 launch with a self-hostable standalone server distro instead of the crappy spaghetti mess you live coded on an EC2 machine?
If you mean the servers to actually host the self-hosted solution, then "me" is a perfectly reasonable option. Server hosting is far from an insurmountable hobby expense.
> Especially once you consider the vast majority of games that never even get traction much less turn a profit.
Which is the whole point. Believe it or not - people who slave away on the game for years want people to maybe get to play it and enjoy it? Cause it's also art and not just business and there's a preservation angle to all of it?
> It needs to also day 1 launch with a self-hostable standalone server distro instead of the crappy spaghetti mess you live coded on an EC2 machine?
Not by day 1 launch, by day "we shut everything down". Not on an EC2 machine - as I mentioned in the thread above, even dumping your cloudformation templates and saying "enjoy all these queues" will satisfy the requirements.
They also need to have had invested in the extra work so that hypothetical players can have the opportunity to self-host the server on day 1 for a game that never caught on in the first place?
If you really don't want to bother with that - don't sell the game, sell timed access and shut it down once the last subscription runs out.
It seems short sighted.
In my opinion it's the other way around. It's short sighted to throw away so much of the medium's history with no way to preserve it.
Is it? Your hosting it somehow? No one is asking for a 1-click installer. What do you do? Let us do that.
If you can't meet these very achievable goals, perhaps the game isn't at a point where it should be sold for money. What are you going to do when that ec2 instance gets randomware and becomes inaccessible, just tell all the people who paid you money to go home and forget about it?
I love indie developers, but if one can't have a modicum of professionalism, then they shouldn't ask people to pay for a product.
It's like thinking that just because the code exists, then it's in a state that could be pushed publicly to github, and that's not the case for almost any codebase.
To think that I would need to do all that the second I charge $1 seems unreasonable. And I think you underestimate how true this is for most games you see on Steam.
I mean, this covers it. Put that code out, and some one else can rysnc it to a VPS. The ask here in not that it's nicely bundled up into a single click deploy. It's that a path exists at all. If I need a fleet of servers and some technical know how, that's fine. Even expected for many games.
If a developer decides to not take that requirement in the design stage then that is their prerogative, but not even doing it would be like not following any other EU consumer protection law.
(Usually I don't like regulations that blatantly favor small businesses like this, because they're coming from a misguided place. But in this case, the benefit of the regulation scales with the number of customers of a given firm, while the costs are fixed per firm, so applying it to large firms but not large ones won't much encourage fragmentation and could capture most of the benefits of applying it to everyone without most of the costs.)
You are buying a license for 2 weeks sounds a lot less appealing than just "buying", but that would have been the reality for Concord had they not issued refunds. Is a year that much better? Maybe, but have it in writing.
These "we sell you a license we may terminate at any point for any reason" terms are absolute bullshit.
If not, then buying is not owning and piracy is not stealing.
If the game can be taken away from you st any time then "buying" is definitely inaccurate too then. "Licensing for a limited time" might be the most accurate, but something like "Lease for X years" might be more concise and accurate enough.
If you buy something, that will be yours, you can use it as long as you want, you can sold it or it can be inherited from you. (In copyright terms that's a perpetual, irrevocable license.)
If there is only a limited duration you can use something, that's called renting and the duration must be known before you enter into a contract.
The terms of the purchase of an online game that might shut down are quite clear and known ahead of time. It's just not a fixed amount of time.
There is a different valid business model, where you subscribe for eg. a monthly / yearly fee and can watch movies form a catalog or play games from a catalog as long as you keep paying and the service is working.
> The terms of the purchase of an online game that might shut down are quite clear and known ahead of time.
On a ticket or a pass there is a clear date or deadline printed on them. Do the same for games (buy thins game 10 EUR for 1 year) and that would be fine, too, (it is the same subscription model just with yearly duration).
I think bankruptcy is clearly its own category here. This is targeted at companies who release something then shutter it because they didn't sell enough copies.
The idea is to force the companies to provide an end-of-life plan that leaves the game in a "reasonably playable state". Depending on the game the approach can differ. Releasing the binaries along with instructions for hosting dedicated servers is one approach (that some games already take). I was playing on a (pirated, but it was a long way ago and I was a child) Lineage 2 server way back in 2007 on my local ISP network, so even something like MMORPGs can be covered if it's included in the discussion at the design stage of the game.
But even if the backend is very complex and vendor-locked, releasing something like a set of Cloudformation templates and saying "you can only host this on AWS and it's going to be restrictively expensive but there you go" is also an option that would satisfy the requirements. It's still better then having nothing at all to dig at (although some fans still do reverse-engineer and spin up community servers even without having access to any of this).