Which is why we need legislative change to force them not to sell a designed-for-obsolescence product in the first place.
Software isn’t a bunch of prepackaged recordings cut together and copied over and over again. You need the binary, the assets, and the environment it can be hosted in. Server software needs maintenance because it lives on a network and networks attract people who will screw around with it if vulnerabilities are known to exist (and there will always be vulnerabilities); and if the entity maintaining it decides that it is no longer worth the expense, they stop maintaining it. That’s their goddamn right so the onus is on you to know what you’re buying and who you’re buying it from and what kind of commitment you can expect from them because more often than not it is not if they will shut it down, but when and what you can expect afterwards. A $60 game you bought once probably doesn’t entitle you to full service for the rest of your natural life. Even a subscription has a time limited term of service.
I understand how the cost-benifit analysis today favours shutting down servers and retroactively taking away recently sold products. This is probably why the previous comment suggested the need for legislation.
What you don’t own are the servers running the server side features or the software not on the disc you bought.
It is true that the players do not own the servers, but it should also be illegal for game companies to abuse their customers using that asymmetry.
This is true even though Dark Spore was apparently a pretty dull game (I never played it myself).
If you’re buying a game with a substantial single player game, LAN-based multiplayer, and online multiplayer, the part you don’t get to keep is the latter portion when the game ends. You’ve effectively bought a game and a ticket, and you should know you bought a ticket because business entities don’t have the obligation to keep existing or to continue owning their assets beyond whatever their contracts require (and there’s even ways to sell those out depending on the contract). But you still own the rest.
In the case of a MMORPG or live service game, all you own is a ticket. And even then it’s not as if you can’t be banned from accessing the servers effectively at-will but usually for cheating or harassment. You have to know the difference, because an online game is an experience in entertainment terms where as an offline game is a re-runnable piece of media. That’s not to discount the scummy things software shops can do, but check the original article; they’re shutting down the servers mostly for games 9+ years old, one that’s only a few years old but is online-only (never heard of it, must not have been too successful), and I have no idea what Ubisoft is doing with the access to DLC part in some of those titles. The article didn’t explain that part very well which is basically what I expect from game journalism, but is this DLC that is intrinsically part of the online experience? Is it offline DLC you can still keep, but not redownload? Is this a little bit of column A or a little bit of column B?
Point is, for some things that you “buy”: when the music stops, the band goes home and the stage gets taken down.
I will note the DRM server shenanigans are something I think should be illegal (on the basis that’s it’s a kind of fraud, but different than what you wrote about) though, and I’m surprised you didn’t bring that up.
Darkspore just didn’t have the cachet that SimCity did, so it didn’t attract as much attention.
that opinion is pretty convenient for the game publisher considering I've yet to see a single one who made it possible for a consumer to know the date they would pull the plug before purchasing the game.
How generous that it's our responsibility to do what we cannot do, but misguided to expect game publishers to do what they can do because it would be more expensive for them. Ubisoft makes billions in revenue. They can afford to not be deceptive and to make sure that players have an opportunity to access and continue to use their purchases for as long as the company has purchases on offer.
How you spend your money is up to you, but unconsidered legislating has much broader implications for society. If you think companies are not upfront enough now, or that it is not completely bleeding obvious that services with a cost component to them can be shut down at will after some length of time, then maybe that’s something to be arbitrated in court before we start flippantly talking about Acts of Congress for every paper cut we experience in life and it’s a meme at this point that like clockwork, somebody can go into some level of detail in what is involved for what people are asking for and you’ll almost immediately find someone saying “we need legislation” in nearly those exact words to the point that I don’t even think it is said in good faith; it just a reflex some people seem to have.
I mentioned this elsewhere, but the multiplayer and live services components of games are more like an experience that you buy a ticket to than an ongoing game you can always return to. When the music stops, the band goes home and the stage gets torn down.
Those are the requirements for making it easy to host it in an alternative location. Laws for incompatibility don't need nor usually require it to be easy, only possible.
Microsoft was able to release the network protocol for smb without releasing the binary, the assets, or the environment for their Microsoft server. They were able to release the network protocol without needing to be responsible for the development and maintenance of samba. Microsoft is not in any form responsible for security vulnerabilities in samba.
If Ubisoft released the protocol for Assassin's Creed 2 multiplayer then the only person responsible software updates would be the group implementing that protocol. A law requiring that minimum disclosure would not be expensive nor take a lot of work (unless the protocol documentation is conveniently deleted).
The biggest issue would be certificates, but if companies know before hand that protocol and authorized keys need to be published by the end of the product life, then companies will plan ahead to make those things easy for them. People who run companies can plan ahead when they are required to do so.
Counterpoint: No it's fucking not.
(It's not much of an argument in either case is it?)