*Membership spots not really limited!
*Membership spots not really limited!
habitual wrote:I was so looking forward to just wasting the day away playing this out on my back porch.
Fortunately it's just a server patch and should be finished in around an hour.
Benderbrau wrote:Do you have to have Battlenet working to play single player? Diablo 2 didn't require it. Hell I think I owned D2 for like a year before I even set up a Battlenet account.
Not got it yet but I've heard you have to be on the internet constantly to play, so I assume so. It's becoming the norm with games these days.
Benderbrau wrote:Perhaps you should lay off the Mountain Dew for a while.
Dragavon wrote:He's being diplomatic again.
Zechs wrote:I have to repress you more. You're way too goodie two shoes.
Fat Ollie Weeks wrote:I swear to God, you are so boring sometimes I think you're just a stealth-mod-bot that Jude has coded.
It's been 12 years since Blizzard last released an installment of its popular Diablo franchise, but judging by the enormous demand that today's release of Diablo III is seeing, it might as well have been yesterday.
The game unlocked at midnight Tuesday. Despite the late hour, however, players quickly overwhelmed the game's servers, extending the pain of people who have been waiting to wear out their index fingers on the clickfest.
Diablo III launched in multiple territories, which caused the Battle.net servers (required to authenticate the game before owners can play it) to buckle. That resulted in a dreaded "Error 37" message, forcing players to log in again, a stalling tactic to make the queue more orderly.
"Please note that due to a high volume of traffic, login and character creation may be slower than normal," said a message posted to the Battle.net forums. "If you're unable to login to the game or create characters, please wait and try again. We've temporarily taken our Battle.net websites offline and launched more servers to accommodate for the traffic. We hope to resolve these issues as soon as possible and appreciate your patience."
[Related: Five things to know about Diablo III]
Players, not too surprisingly, were pretty vocal in their frustration. "Error 37" quickly became a top trending topic on Twitter.
The server crunch is a familiar event for players of hotly anticipated massively multiplayer games. Blizzard's World of Warcraft had similar problems when it launched, as too many people tried to play at once. The problems usually resolve themselves within a day or two as the obsession over the new game fades a bit.
And given the demand for Diablo III, Blizzard actually warned people in advance this problem might occur. Pre-orders for the game set a new record for the company, coming in at 2 million.
Development on the game started in 2001, but the company was never happy with what it saw. Diablo III actually went through three quiet revisions, but it wasn't until June of 2008 that Blizzard officially confirmed the game was in development. Players had to wait another three years before the public beta opened up.
Dragavon wrote:It is irritating as hell that a game that I bought and paid for, I am unable to play.
Benderbrau wrote:And consider this: because it requires their servers to play it in any form you didn't pay for it, you just rented it from them. I'll bet that's the most you've ever paid for a rental.
some idiot on facebook wrote:I don't like your belittling tone, Jude. Just because I don't know how to spell the language of some tiny African nation doesn't mean that I'm wrong in thinking that your attitude towards women is 100% wrong. Obviously, you're some skinny, single nerd living on the East Coast who probably derives value in life from wrestling matches, hoping that Wolverine gets to sleep with teenagers and engaging in casual drug use. You're literally the worst thing to happen to comics since Stan Lee.
Users browsing this forum: Google [Bot], VaderTheTrader and 45 guests