Send News. Want a reply? Read this. More in the FAQ.   News Forum - All Forums - Mobile - PDA - RSS Headlines  RSS Headlines   Twitter  Twitter
Customize
User Settings
Styles:
LAN Parties
Upcoming one-time events:
Greenbelt, MD 08/22

Regularly scheduled events

Ships Ahoy - Diablo III

Battle.net announces the extended wait for Diablo III is now over, and the action/RPG sequel should now be available worldwide. For anyone getting error messages from the game, this article may help you work out what's wrong, and here's word on the release:

Twenty years have passed since the Prime Evils were defeated and banished from the world of Sanctuary. Now you must return to Tristram and investigate rumors of a fallen star, an omen that the End Times have begun.

Diablo III is now live and available at a store near you -- or you can click here to purchase a digital copy directly through Blizzard. The game is available at retailers in both a standard and Collector's Edition. Visit our Diablo III game information page or search the Game Guide to learn more about this highly anticipated third installment in the Diablo series.

View
286 Replies. 15 pages. Viewing page 3.
< Newer [ 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ] Older >

246. Re: Ships Ahoy - Diablo III May 16, 2012, 09:06 Overon
 
Speculation does not equal actual knowledge. Who here actually has knowledge of what the problem with Blizzard Diablo 3 downtime was?  
Reply Quote Edit Delete Report
 
245. Re: Ships Ahoy - Diablo III May 16, 2012, 09:02 nin
 
The Retail DVD will NOT install. The update agent always gets stuck and I've tried every solution posted. It's a major networking clusterfuck on the part of the idiots who coded it.

Unbelievable.

To anyone who hasn't bought it. DON'T. You won't be able to install the fucking thing, let alone try and play it.


The dvd worked just fine for me. Installed and off I went to play.


 
http://www.nin.com/pub/tension/
Reply Quote Edit Delete Report
 
244. Re: Ships Ahoy - Diablo III May 16, 2012, 08:58 RollinThundr
 
So let me guess, over 200 pages of bitching about Blizzard not being prepaired to launch the game and not having a backend in place, and Krowen defending them left and right as the bestest company ever? Does that about sum up this thread?  
Reply Quote Edit Delete Report
 
243. Re: Ships Ahoy - Diablo III May 16, 2012, 08:14 finga
 
Six months from now, no one will care that the first 24 hours of Diablo 3's launch were rough. If it turns out to be three weeks, or two months, which was something closer to WoW's early growing pains, then that's an issue people will care enough about for it to make an impact. Getting errors the very first day? Not really.  
Reply Quote Edit Delete Report
 
242. Re: Ships Ahoy - Diablo III May 16, 2012, 07:08 Dades
 
Not trolling, just a good ol' fashioned "told ya so" to all those fanboys who were blaming all the issues during the open stress test weekend on the fact that it was beta and a stress test, and claiming that everything would be fine at release. You know who you are.

The lesson here is to stop feeding Trollven.
 
Avatar 54452
 
Reply Quote Edit Delete Report
 
241. Re: Ships Ahoy - Diablo III May 16, 2012, 05:03 Dev
 
Krovven wrote on May 16, 2012, 04:50:
And do you know what caused the outages? Most likely hardware failure. You can test and test and test...something will always fail and have to be replaced.
Redundancy would solve that. Whatever the problem was, there was a way to help reduce or prevent it. A longer more massive stress test probably would have found it.
 
Reply Quote Edit Delete Report
 
240. Re: Ships Ahoy - Diablo III May 16, 2012, 04:50 Krovven
 
Wowbagger_TIP wrote on May 16, 2012, 03:05:
Not trolling, just a good ol' fashioned "told ya so" to all those fanboys who were blaming all the issues during the open stress test weekend on the fact that it was beta and a stress test, and claiming that everything would be fine at release. You know who you are.

Having to deal with losing progress in a single-player game because some server puked or your net connection got screwy for a minute is just really really stupid.

And do you know what caused the outages? Most likely hardware failure. You can test and test and test...something will always fail and have to be replaced. Or, simply bugs. If the final boss isn't giving loot, you think that's worth them taking the servers down to do maintenance? Or should people that kill the final boss continue to get nothing?

There is no lost progress. You start from the last checkpoint, which they are frequent, just like most other games. As usual the idiots that didn't buy the game are talking out of their ass.

This comment was edited on May 16, 2012, 04:56.
 
Reply Quote Edit Delete Report
 
239. Re: Ships Ahoy - Diablo III May 16, 2012, 03:05 Wowbagger_TIP
 
Bhruic wrote on May 16, 2012, 00:20:
As long as they had "internet connection required", and "no guaruntee of server availability", they're almost certainly fine.
I'm pretty sure "no guarantee of server availability" wasn't a bullet-point on the box. If you don't know about it at the time of purchase, then you should certainly be offered a refund.

Zanthar wrote on May 15, 2012, 17:39:
I can live with the server downtime if it stops all the damn cheating and duping in the previous games. Only time will tell if that's the case though.
An offline mode where characters can never go online would have had no effect on the security of the online game. It would, however, have allowed people to play the game they paid 60 bucks for.

Krovven wrote on May 15, 2012, 17:12:
MadBoris wrote on May 15, 2012, 16:53:
What may be stranger still, is that there is still a horde of Blizz fanboys still actively dismissing issues on the D3 boards, aggressively at those that bring up the obvious. It's like a blind cult.

Then there is polar opposite folks that are bitching and trolling the boards when they didn't even buy the game. You balance each other out.
Not trolling, just a good ol' fashioned "told ya so" to all those fanboys who were blaming all the issues during the open stress test weekend on the fact that it was beta and a stress test, and claiming that everything would be fine at release. You know who you are.

Having to deal with losing progress in a single-player game because some server puked or your net connection got screwy for a minute is just really really stupid.
 
Avatar 9540
 
"The whole problem with the world is that fools and fanatics are always so certain of themselves, but wiser people so full of doubts." -- Bertrand Russell (I think...)
Reply Quote Edit Delete Report
 
238. Re: Ships Ahoy - Diablo III May 16, 2012, 02:33 Dev
 
Krovven wrote on May 16, 2012, 02:16:
You know you can just play on the Euro servers...

You mean since they announced that global region playing isn't enabled yet so you are stuck in your own region right now?

Edit: Nm, they announced that global play is now operable. But it wasn't last I checked.
 
Reply Quote Edit Delete Report
 
237. Re: Ships Ahoy - Diablo III May 16, 2012, 02:16 Krovven
 
You know you can just play on the Euro servers...

 
Reply Quote Edit Delete Report
 
236. Re: Ships Ahoy - Diablo III May 16, 2012, 00:20 Bhruic
 
This isn't a case of not liking a particular feature. This is a case of not being able to play the game you paid for due to developer/publisher incompetence. Granted, the game's only been out for a day but it's still unacceptable.

Sure, but that's not really lawsuit worthy. This is the sort of situation where, with an MMO, they'd tend to give you a free day to make up for it, but as Diablo 3 is already free, that's not really an option.

As long as they had "internet connection required", and "no guaruntee of server availability", they're almost certainly fine.
 
Reply Quote Edit Delete Report
 
235. Re: Ships Ahoy - Diablo III May 16, 2012, 00:16 UttiniDaKilrJawa
 
Sanctuary's screwed.
It is the End Times.
They officially ended at about 11:08 pm when the denizens of hell
punted me out of Sanctuary with error 37.

Hell wins.
Film at 11.
 
Reply Quote Edit Delete Report
 
234. Re: Ships Ahoy - Diablo III May 15, 2012, 23:56 Prez
 
This isn't a case of not liking a particular feature. This is a case of not being able to play the game you paid for due to developer/publisher incompetence. Granted, the game's only been out for a day but it's still unacceptable.

I agree that it's unacceptable (To me, the very notion that my ability to play a singleplayer game is reliant upon a company's server being online and working is unacceptable, so D3 is an absolute no-go for me). But generally it's better to temper one's response in accordance with the severity of the infraction. As parents we don't cut our kids feet off if they stay out past curfew one night. By the same token, a more reasonable response to Blizzard's lack of judgement and the technical ineptitude with which they handled the launch would be to, say, email Blizzard and demand a refund. Or write a letter explaining why Blizzard has lost you as a customer forever. Or find a witchdoctor or warlock and cast a curse on the the Diablo 3 team that will cause them to have uncontrollable, incessant, oily diarrhea forever more.

This comment was edited on May 16, 2012, 00:14.
 
Avatar 17185
 
“The greatness of a nation and its moral progress can be judged by the way its animals are treated.”
- Mahatma Gandhi
Reply Quote Edit Delete Report
 
233. Re: Ships Ahoy - Diablo III May 15, 2012, 23:54 PropheT
 
Cutter wrote on May 15, 2012, 23:01:
None of it works becase the installer won't patch on certain 64 bit Vista/Win7 systems. It just hangs and won't update anything. So even if you could DL the full client the moment the updater starts you're fucked. And they've know this for a while now. That's just not dropping the ball, that's just shitting on customers.

The release version doesn't have the issue, or didn't for me, even though the open beta did.

If you're still having trouble I can dig through my post history for the fix if you want it, I know I posted it here back when open beta was live. It sounds a lot more complicated than it is, really, it's fairly simple to correct once you know what obscure component you're looking for.
 
Reply Quote Edit Delete Report
 
232. Re: Ships Ahoy - Diablo III May 15, 2012, 23:52 Zanthar
 
Yet another outage... this time all of battlenet is down.
 
Reply Quote Edit Delete Report
 
231. Re: Ships Ahoy - Diablo III May 15, 2012, 23:01 Cutter
 
Dev wrote on May 15, 2012, 22:41:
Wraith wrote on May 15, 2012, 19:41:
Jesus Christ, what a piece of shit.

Here's a clue, Blizzard. Have some software engineers worth a damn who can code an update agent which isn't an exercise in engineering incompetence.

The Retail DVD will NOT install. The update agent always gets stuck and I've tried every solution posted. It's a major networking clusterfuck on the part of the idiots who coded it.

Unbelievable.

To anyone who hasn't bought it. DON'T. You won't be able to install the fucking thing, let alone try and play it.
Thats why you don't use the retail DVD. You put the code into your battle.net account and download it. Retail boxes are a waste anyway IMHO.

I'm not excusing blizzard here, the online only SP is crazy, and having servers offline for 4 hours for a promised 1 hour maintenance, they shoulda done more OPEN stress testing, and they shoulda invested in enough servers for the known pre-order demand trends. I'm just saying there's ways around using the dvd.

None of it works becase the installer won't patch on certain 64 bit Vista/Win7 systems. It just hangs and won't update anything. So even if you could DL the full client the moment the updater starts you're fucked. And they've know this for a while now. That's just not dropping the ball, that's just shitting on customers.
 
Avatar 25394
 
"The South will boogie again!" - Disco Stu
Reply Quote Edit Delete Report
 
230. Re: Ships Ahoy - Diablo III May 15, 2012, 22:41 Orogogus
 
Jerykk wrote on May 15, 2012, 22:26:
Orogogus wrote on May 15, 2012, 22:08:
ASeven wrote on May 15, 2012, 21:59:
Prez wrote on May 15, 2012, 21:44:
I can understand being pissed about not being able to play your game in Singleplayer because of some shit with the servers you have no interest in being connected to (which is mainly why I am not buying D3), but let's have some perspective here. Lawsuits? Really? Do we really need to clog up our already completely borked legal system with lawsuits over a game? How about we save our litigation for things like medical malpractice and negligence resulting in injury or destruction of property?

Truth be told, sometimes the way to force change of the good kind is to go litigious on their asses.

When there's real harm being done, or the company is abusing a monopoly position. This seems more like initiating a lawsuit against a developer because you don't like quick time events, or the default field of view, or menus that aren't mouse-friendly enough. The way to force change here is to get people not to buy the game. It's not like Blizzard has the kind of stranglehold that Microsoft or Apple has. What case is there to be made here?

This isn't a case of not liking a particular feature. This is a case of not being able to play the game you paid for due to developer/publisher incompetence. Granted, the game's only been out for a day but it's still unacceptable.

There's "unacceptable" as thrown around on a message board and "unacceptable" in a court of law. Well, whatever. Good luck with the lawsuit.
 
Reply Quote Edit Delete Report
 
229. Re: Ships Ahoy - Diablo III May 15, 2012, 22:41 Dev
 
Wraith wrote on May 15, 2012, 19:41:
Jesus Christ, what a piece of shit.

Here's a clue, Blizzard. Have some software engineers worth a damn who can code an update agent which isn't an exercise in engineering incompetence.

The Retail DVD will NOT install. The update agent always gets stuck and I've tried every solution posted. It's a major networking clusterfuck on the part of the idiots who coded it.

Unbelievable.

To anyone who hasn't bought it. DON'T. You won't be able to install the fucking thing, let alone try and play it.
Thats why you don't use the retail DVD. You put the code into your battle.net account and download it. Retail boxes are a waste anyway IMHO.

I'm not excusing blizzard here, the online only SP is crazy, and having servers offline for 4 hours for a promised 1 hour maintenance, they shoulda done more OPEN stress testing, and they shoulda invested in enough servers for the known pre-order demand trends. I'm just saying there's ways around using the dvd.
 
Reply Quote Edit Delete Report
 
228. Re: Ships Ahoy - Diablo III May 15, 2012, 22:26 Jerykk
 
Orogogus wrote on May 15, 2012, 22:08:
ASeven wrote on May 15, 2012, 21:59:
Prez wrote on May 15, 2012, 21:44:
I can understand being pissed about not being able to play your game in Singleplayer because of some shit with the servers you have no interest in being connected to (which is mainly why I am not buying D3), but let's have some perspective here. Lawsuits? Really? Do we really need to clog up our already completely borked legal system with lawsuits over a game? How about we save our litigation for things like medical malpractice and negligence resulting in injury or destruction of property?

Truth be told, sometimes the way to force change of the good kind is to go litigious on their asses.

When there's real harm being done, or the company is abusing a monopoly position. This seems more like initiating a lawsuit against a developer because you don't like quick time events, or the default field of view, or menus that aren't mouse-friendly enough. The way to force change here is to get people not to buy the game. It's not like Blizzard has the kind of stranglehold that Microsoft or Apple has. What case is there to be made here?

This isn't a case of not liking a particular feature. This is a case of not being able to play the game you paid for due to developer/publisher incompetence. Granted, the game's only been out for a day but it's still unacceptable.
 
Avatar 20715
 
Reply Quote Edit Delete Report
 
227. Re: Ships Ahoy - Diablo III May 15, 2012, 22:08 Orogogus
 
ASeven wrote on May 15, 2012, 21:59:
Prez wrote on May 15, 2012, 21:44:
I can understand being pissed about not being able to play your game in Singleplayer because of some shit with the servers you have no interest in being connected to (which is mainly why I am not buying D3), but let's have some perspective here. Lawsuits? Really? Do we really need to clog up our already completely borked legal system with lawsuits over a game? How about we save our litigation for things like medical malpractice and negligence resulting in injury or destruction of property?

Truth be told, sometimes the way to force change of the good kind is to go litigious on their asses.

When there's real harm being done, or the company is abusing a monopoly position. This seems more like initiating a lawsuit against a developer because you don't like quick time events, or the default field of view, or menus that aren't mouse-friendly enough. The way to force change here is to get people not to buy the game. It's not like Blizzard has the kind of stranglehold that Microsoft or Apple has. What case is there to be made here?
 
Reply Quote Edit Delete Report
 
286 Replies. 15 pages. Viewing page 3.
< Newer [ 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ] Older >


footer

.. .. ..

Blue's News logo