i saw blizzworker periodicly answering questions and giving updates on the input they recieve.
but we created how many new threads ? and how many of them were duplicates from duplicates from duplicates from duplicates from duplicates ?
They said on Twitter that they had a fix, but it was bad, and they are going to give it another crack tomorrow. Basically, theyâre incompetent.
1 Like
Well I guess we will be waiting another 10hrs+
We have to be strong all ! , we all have to hope that we can play today
the most unbelieveable part for me is that on a release night they dont have a nightshift for bugs like this. Instead they reply âwe will look at this tomorrowâ. GeezâŚ
My main issue with this is:
It worked in the BETA.
There was no mentioning that this was to change for release.
They have either made a conscious decision to change it right before release without considering the consequences (or have considered and didnât care but it would help lower load on the game servers).
They have âaccidentlyâ changed it as they have âmentionedâ - how does something like this get âaccidentlyâ changed? If it was a simple âtrueâ or âfalseâ, it would be a simple and easy fix.
This would have been perfectly fine if they had changed this prior to the Beta - we all would have known about it back then and could have done what we needed to do (ie. update if we wanted to) or we could have decided not to buy back then.
Whatever the truth is, pure incompetence from them. Exasperated by the fact it is is now roughly 17hrs and they still havenât fixed it and likely wont for another, who knows, 10hrs+ or so?
3 Likes
I really hope to play this weekend⌠Blizzard doesn`t like my Xeon either⌠
Of course, the one team of devs they have on alert for a launch like this, needs to sleep nowâŚ
IntelÂŽ Software Development Emulator ( AVX emulator )
but still canât start diablo 
new error 0xc0000005
I have the same Problem⌠clicking " Play " button and its not working.
Clicking Play - Launching - and back to play.
My PC:
Prozessor: Intel(R) Core⢠i7 CPU 930 @ 2.80GHz, 2801 MHz, 4 Kern(e), 8 logische(r) Prozessor(en)
BaseBoard: SABERTOOTH X58
Graphic card: Geforce GTX 1060
RAM: 12GB
yes and have Application Error bla bla ntdll.dll 0xc0000005
This is just dumb. If this isnât fixed in the morning, Iâm just going to get a refund.
30 hrs after release still canât play. GG Blizzard!
The Game aint even out for 24 hoursâŚ
1 Like
By the time we get on, half the players would have hit max level and retired again! 
LOL
This is what happens when Activision infiltrates a good developer.
2 Likes
Itâs beyond Activision at this point. The original Blizzard team is gone. This is a new generation of inexperienced and incompetent developers that have no idea what theyâre doing.
7 Likes
oops! lol this is correct hahaha feels like 30hrs but its actually only 18hrs, my bad!
1 Like