> Of course it's to do with [DRM]. If it [was a single player game], there would be no issues at all.
The two are unrelated. If it was a single player game we wouldn't be having these issues... because it wouldn't need server capacity to play, which is nothing to do with DRM. It could still have always-on DRM.
Well, if the players still had to be connected to the servers (always-on) to play, maybe the same problems would arise even though the players wouldn't be interacting.
The strange aspect of this is that their infrastructure seems to be static. In this modern age of cloud computing, why not make the number of game servers elastic? That would bring safety to them and savings by reducing the number of idling servers when demand is low.
Perhaps. I had be interested in your sources for this fact though. Otherwise it feels like opinion being stated as fact.
More saliently, it happened with the launch of Cities XL... which did more or less exactly the same things in the cloud that this new SimCity is trying to do.
It's DRM.
The game is intended to be played online. You share resources with neighbouring cities. Crime spills over into your city from others. You can work together on collaborative projects (international airports etc.). It's not MMO but it's not single player either.
I believe in some early interviews Maxis also referred to some computational work being offloaded to EA servers but I can't find these now. They might not have gone through with it, but it was certainly in the original plan.
There really is nothing to say in their defense, even if they DID design the game to be multiplayer, they could of done it in a decentralized way and let peers inter-connect. They did it this way for control. Do not defend them.
A proportional response would be to allow users to refund the game, since this is a quality issue and is clearly out of the players' control; and to rapidly expand their server capacity until they have enough for everyone.
(I'm not an advocate for DRM, just proportionality.)