Linked by Thom Holwerda on Mon 11th Mar 2013 14:46 UTC
Games "To see anyone defending EA and Maxis for the state of SimCity, even were it in perfect working order on launch, depresses me to my core. This self-flagellation-as-skincare notion, where gamers loudly and proudly defend the destruction of their own rights as consumers, is an Orwellian perversity. That it might be considered in any way controversial to call them out on their crap, to point out that no, always-on DRM is not an advantage to anyone, is bewildering. It's a sign of just how far the gaming world has fallen into the rabbit hole of the publisher's burrowing." As usual, RPS hits the nail on the head so hard it shoots through the board.
Thread beginning with comment 555197
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Technical Stuff!
by static666 on Tue 12th Mar 2013 09:42 UTC in reply to "Technical Stuff!"
Member since:

Imagine you're writing a multi-player online game. You're going to get "shared state" (this can't be avoided). The end result is that a lot of things that effect the shared state (things like AI, weather, etc) are going to be done at the server. The client is just there for user input and output.

Really can't think of that much "shared state" in a city-building simulation game that would require centralized processing and justify always-online requirement. This is no MMORPG with tons of actors, buffs/debuffs/area effects, 3D terrain, complex boss encounters; nor it is a competitive online game where server-side processing is required to prevent cheating.

a) duplicate all of the game's logic in the client (creating a lot more work and bloat)
b) give the end user a copy of the server, where "single-player" means running a local server (increasing work and documentation/support/updates and code portability hassles)
c) make "single-player mode" re-use the existing servers

Heh, "duplicate". Sure, why include any game's logic into the purchase at all (after all it's more work and bloat) or letting the user run a local server (again more work, who ever reads documentation, plus users's stupid anyway). Let's sell just a bunch of textures packed in proprietary format with a dumb client app and PROFIT! :-)

Reply Parent Score: 1