Quote:
Originally Posted by TouchOfEVil
Someone who never played an alpha before ? Wow. For an alpha this game almost looks like a ready to be released game from any developer but blizzard. Diablo 3 OPEN beta had more issues than this alpha. They deliverably put input lag and stress their own servers etc to see if it holds up. Sure your gameplay experience might suck but 3k ppl raging a bit is a spit in the ocean compared to the rage of a game shutting down in the release week. Chill the **** down, im even surprised all models are done/working
Don't be so daft. I've played many alpha releases before (seems like everything on Steam is early access lately), would wager many more than you, but from Blizzard I expect somewhat of a sound foundation to actually test their platform. Granted that post was over 3 months old and they've fixed that massive issue with the "stuttering", you can't honestly say D3 open beta was unplayable to the point where the game would just continue without you for 5 seconds at a time. You must have just got into the alpha since you don't seem to have experienced this issue, or just are just grossly misunderstanding the bug I've described as something that wouldn't literally prevent people from testing their alpha build.
What does deliverably putting input lag mean? Deliberately? Why would they actually try to put input lag in their build? Maybe you have some deeper insight into developing games than me, but that doesn't make any sense? Obviously they want to stress test their servers (Which by the way, they haven't done yet. 3000 concurrent users is NOTHING), and probably don't have one near my East Coast location, explaining the server lag, but could you explain why Blizzard would intentionally put input lag in the game?