Here Are Some Diablo III Issues You Ought to Watch Out For

Posted by Alex (2391 posts) -

Since undoubtedly many of you out there in Giant Bomb land are either busy already plundering the depths of Sanctuary, or eagerly counting the hours until work/school's end so that you can go home and play already, I figured it might be a good idea to wave a quick caution flag regarding a few bugs and issues that have been reported since Diablo III's launch last night.

Error 37 is the least of anyone's worries now.

The biggest and most terrifying of the bugs is a genuine game-breaker, according to various threads in the Blizzard forums. In this case, it appears that anyone who equips a Templar follower with a different shield will suddenly encounter a synchronization error and be dropped from the game's servers. Users are additionally reporting that even upon restarting the client and attempting to log back in, a dreaded "Error 3006" message appears and prevents them from doing so.

This error may be limited to the Demon Hunter class, but regardless of class, it's probably best if you hold off on doing any shield switching with your Templar buddy until Blizzard posts a fix (which Eurogamer reports is on the way), just to be safe.

Blizzard has also addressed a couple of other issues, including a character creation error that somehow maxes your character list, as well as the more nebulous errors 14009 and 315300. For the character creation bug, Blizzard suggests that simply logging out and then logging back in may fix the problem. For the other errors, the current workaround involves creating a new Windows user account with admin permissions, and try again from there. Not exactly an ideal solution, but it's what they've got right now.

Between these errors and some of the more innocuous login errors related to high server traffic, Diablo III's launch certainly has a few landmines to navigate. While it's possible (probable, even) that many players won't run into many, if any of these issues, that's probably not going to be much comfort to those that have.

#1 Posted by Alex (2391 posts) -

Since undoubtedly many of you out there in Giant Bomb land are either busy already plundering the depths of Sanctuary, or eagerly counting the hours until work/school's end so that you can go home and play already, I figured it might be a good idea to wave a quick caution flag regarding a few bugs and issues that have been reported since Diablo III's launch last night.

Error 37 is the least of anyone's worries now.

The biggest and most terrifying of the bugs is a genuine game-breaker, according to various threads in the Blizzard forums. In this case, it appears that anyone who equips a Templar follower with a different shield will suddenly encounter a synchronization error and be dropped from the game's servers. Users are additionally reporting that even upon restarting the client and attempting to log back in, a dreaded "Error 3006" message appears and prevents them from doing so.

This error may be limited to the Demon Hunter class, but regardless of class, it's probably best if you hold off on doing any shield switching with your Templar buddy until Blizzard posts a fix (which Eurogamer reports is on the way), just to be safe.

Blizzard has also addressed a couple of other issues, including a character creation error that somehow maxes your character list, as well as the more nebulous errors 14009 and 315300. For the character creation bug, Blizzard suggests that simply logging out and then logging back in may fix the problem. For the other errors, the current workaround involves creating a new Windows user account with admin permissions, and try again from there. Not exactly an ideal solution, but it's what they've got right now.

Between these errors and some of the more innocuous login errors related to high server traffic, Diablo III's launch certainly has a few landmines to navigate. While it's possible (probable, even) that many players won't run into many, if any of these issues, that's probably not going to be much comfort to those that have.

#2 Posted by binhoker (82 posts) -

aw hell

#3 Posted by Mystyr_E (1195 posts) -

Seems Diablo 3 has a secret boss and its name is Error 37

#4 Posted by LordCmdrStryker (345 posts) -

I switched my Templar's shield immediately and had no problems, soo... yeah. Maybe Blizzard should have *gasp* delayed it.

#5 Posted by dusker (170 posts) -

I don't think these are that crazy given the size of the game. I haven't run into them though, so maybe I'm biased.

#6 Posted by Roger_Klotz (795 posts) -

I'm glad I have to wait to purchase it. Hopefully the problems will be patched before I get to buy it.

#7 Posted by Adziboy (702 posts) -

God damn.

#8 Posted by Floppypants (798 posts) -

I didn't experience the Templar shield bug while playing as my Wizard this morning.

The rest of the issues seem to stem purely from the servers being crushed. It took me about 90 minutes to login this morning, but once I was in I was golden.

#9 Posted by thatdutchguy (1283 posts) -

just lol

#10 Posted by Corvak (1172 posts) -

Error 37 is just traffic control for the login server. Beta had it too, just keep trying. Better than it just up and crashing like the WoW login used to do.

#11 Posted by depecheload (497 posts) -

Utterly pathetic and inexcusable bullshit.

#12 Posted by TheInternets (11 posts) -

Many of the issues mentioned were already posted on the US forums by EU players earlier in the day. The same issues were addressed by GMs and many people did not read them which caused even more issues. Error 37 is this: "Error 37 - This error indicates that the Diablo III server is full and is likely the result of high login traffic. If you receive this error message, please wait and try again."

Bashiok specifically said right after the Asia Diablo 3 server openings that Error 37 was something they implemented for the launch but just didnt rename it because eventually they will be removing it. In his words, players just need to keep retrying the login.

#13 Edited by Pr1mus (3946 posts) -

Silly people trying to play a blizzard game on day 1. People ought to know better by now.

#14 Posted by alibson (165 posts) -

Well at least this game doesn't have the worst DRM in existence and you can just play singleplayer offline.

OH WAIT

#15 Posted by Winternet (8053 posts) -

It's an MMO launch so no big surprises there. Oh wait . .

#16 Posted by RainbowWeasel (3 posts) -

Kind of used to PC releases of this magnitude having a few issues when launched, but Blizzard is usually pretty quick and decent about fixing it. It's gotta go better than some of the game Bethesda has published in the past year. I doubt these problems will hurt Diablo in any meaningful way like it did Brink.

#17 Posted by Sweep (8976 posts) -

In terms of a percentage, though, how many people are actually having issues? Relative to the huge number of players I bet the frequency of such issues is insignificant.

Unless it's happening to you, obviously. In which case it's the worst thing ever.

Moderator
#18 Posted by Vodun (2370 posts) -

@depecheload said:

Utterly pathetic and inexcusable bullshit.

How do you figure?

#19 Posted by leejunfan83 (1001 posts) -

Over hyped ass game nothing new nothing special

#20 Posted by Depth (357 posts) -

Game is fun as heck and these issues are a bit silly.

#21 Posted by Glottery (1388 posts) -

While I do think that it sucks for some folks (no sympathy for any loud-mouthed idiots) that they're having issues with the game, I personally haven't experienced any trouble. Started playing around 7am local time, no logging issues or such.

But with how many times I've jinxed myself by now, I'll probably end up receiving an error, resulting in my account being deleted...

#22 Posted by Davvyk (694 posts) -

Been playing for the past few hours. All has been fine for me.

#23 Posted by CosmicQueso (572 posts) -

@Sweep said:

In terms of a percentage, though, how many people are actually having issues? Relative to the huge number of players I bet the frequency of such issues is insignificant.

Unless it's happening to you, obviously. In which case it's the worst thing ever.

It doesn't matter if it's 0.0001% of users. The internetz will rage over nothing. Some of the comments on this are just so typical. It's a huge software launch. There will be bugs no matter how much testing happens. Blizzard will have them patched in no time. Carry on.

#24 Posted by Tennmuerti (8174 posts) -

My only remaining issue right now is that sometimes achievement progress is not registering at all, this would not be an issue but the achieveement system feeds into your banner customization. So far I'm missing huge amount of unavoidable achievements for Act1.

#25 Posted by MythDarK (558 posts) -

I feel the urge to play SC2.

#26 Posted by PaulKemp (114 posts) -

No templa bug with my Witch Hunter either.

For me, this has been a smooth launch. Only had to try like 3, 4 times at 00:40 yesterday to maneuver the error 37. Way less issues than feared.

Online
#27 Posted by LiK (925 posts) -

online only is a drag

#28 Posted by ribeye (411 posts) -

jeez really? create a new windows profile? right click and run-as administrator anyone?

#29 Posted by depecheload (497 posts) -

@Vodun said:

@depecheload said:

Utterly pathetic and inexcusable bullshit.

How do you figure?

I'm in that ever-increasing minority that bugs should NOT be in finished games, unless they are related to unexpected/updated hardware configurations. I'm sorry, you spend years making a game and testing it, then it should work right the day it comes out, stop shipping unfinished games.

There's no excuse for it. I'm a freelance writer, if I turn in an unfinished article, my ass gets fired.

#30 Posted by TooWalrus (13256 posts) -

Hopefully this is all sorted out by... this evening.

#31 Posted by Deathpooky (1443 posts) -

Getting the game purchased and installed was a bit of a challenge last night with Blizzard's websites crashing like crazy, but logged on this morning and played a couple hours with no problem, on my Macbook Pro no less! A little lag at times, which is annoying since I'm playing single player, but nothing bad.

#32 Posted by mracoon (4978 posts) -

I'm going to wait until after my exams before picking it up and hopefully by then most of the launch issues will be sorted.

Moderator
#33 Posted by l3illyl3ob (285 posts) -

I'm pretty glad I didn't pre-order a digital copy and try to get in on the server's launch. A friend tried to get in for an hour and a half last night.

Thanks for the heads up about the shield bug alex. Was maybe gonna roll a demon hunter when I got the game today.

#34 Posted by yyZiggurat (1026 posts) -

Three cheers for always online policies!

#35 Edited by cassus (388 posts) -

Can we un-god blizzard at this point? They used to be "that dev that always released polished games etc. etc." but with this launch, and the fact that they have the always online thing (which may or may not be an issue to people, I don't really care as I'm a stationary PC dude, and I'm always online.. Mostly anyways, barring ISP issues.) can we finally put Blizzard in with all other devs? Well, aside from Valve, obviously. (fricken free MASSIVE expansion pack for portal still boggles the mind..)

A bit tired of Blizzard being held in such high regard even after butchering WoW, releasing StarCraft 3D at idiotic prices, and now Diablo 3.. They're no better than any other dev as far as I'm concerned. They're good and all, but no better than any other good dev.

#36 Posted by Hangnail (193 posts) -

Great idea leashing a game to the internet Blizzard!

#37 Posted by PresidentOfJellybeans (307 posts) -

Man... not even Blizzard can make a game that works at release anymore. That's a damn shame. =(

#38 Posted by buft (3320 posts) -

played all night without issue, got logged in at 12:30 without incident, playing the demon hunter with several friends so no companion which is possibly how i avoided that bug.

#39 Posted by virtorio (252 posts) -

That's what happens when you rush development to get your game out as quickly as possible. 
Oh wait.

#40 Posted by Andtheworld (33 posts) -

This is why I never buy games with always online DRM bullshit.

@CosmicQueso said:

@Sweep said:

In terms of a percentage, though, how many people are actually having issues? Relative to the huge number of players I bet the frequency of such issues is insignificant.

Unless it's happening to you, obviously. In which case it's the worst thing ever.

It doesn't matter if it's 0.0001% of users. The internetz will rage over nothing. Some of the comments on this are just so typical. It's a huge software launch. There will be bugs no matter how much testing happens. Blizzard will have them patched in no time. Carry on.

Nothing? This ain't a fucking MMO, man, it's a goddamn dungeon crawler. People shouldn't have to deal with server issues when they want to roll in single player.

#41 Posted by djames216 (398 posts) -

This kind of crap is inexcusable, given the amount of time they have worked on it.

#42 Posted by thefjk (142 posts) -

To be on Blizzard's side... this game is huge and it randomizes everything and is online, probably impossible to figure these things sometimes.

To be against Blizzard's side... WTF mayne? I thought number of years was directly proportional to game's quality... NOT!

#43 Posted by MachoFantastico (4889 posts) -

Only issue I have come across was with the Blizzard downloader and that was easily fixed. So  far very much enjoying it. 

#44 Posted by 014 (348 posts) -

My first thought is I'm glad my Diablo III parties are planned 1.5 - 2 weeks after launch. My second thought is, man, it's really sad and disappointing these errors weren't ironed out during the beta testing. I am not buying the game until pay day. This news makes me happy I may have avoided a lot of frustration.

#45 Posted by Swoxx (3008 posts) -

@Mystyr_E said:

Seems Diablo 3 has a secret boss and its name is Error 37

Z...zing?

#46 Posted by probablytuna (3823 posts) -

The wait to join the game was torturous, perhaps it's because everyone's trying to log in at the same time when the servers went online but other than that I haven't any trouble playing the game. Oh yeah and the character creation bug was weird, kept saying the request timed out and when I logged back in I had like 10 different Monk characters on my screen.

#47 Posted by NickyDubz (272 posts) -

@Andtheworld: maybe you should bitch at the people who steal things and make this a necessity for a company to make money...

#48 Posted by Soulblitz (350 posts) -

It blows my mind how we still have this problem in 2012. You'd think a developer like Blizzard, with all that money and all those servers, would be able to handle the traffic. Surely they knew how many people were going to be buying the game and trying to play it at once?

It just seems crazy to be that after all the big launches, we still get this problem. I mean, how can they not have enough bandwidth/whatever to let everyone play? Ugh.

#49 Posted by Rasgueado (719 posts) -

Not quite a nothing problem. I tried to login and play over the course of 2 1/2 hours last night until I could finally even create a character. I started plowing through a dungeon and then got dropped from the server, which booted me back out to the man menu. After another ten minutes of trying to log back in, and I found myself back at the start of the game. So great... losing connection to their server means you can also lose game progress. Sweet.

#50 Posted by MeatSim (10939 posts) -

Well I guess it's a good thing I didn't get Diablo 3 yet.

This edit will also create new pages on Giant Bomb for:

Beware, you are proposing to add brand new pages to the wiki along with your edits. Make sure this is what you intended. This will likely increase the time it takes for your changes to go live.

Comment and Save

Until you earn 1000 points all your submissions need to be vetted by other Giant Bomb users. This process takes no more than a few hours and we'll send you an email once approved.