Diablo III woes plague launch day

For some people, trying to access Diablo III, the long-anticipated sequel to the hit role-playing game, has so far been more challenging than actually playing it.

A taste of Demon Hunter gameplay. Just don't equip any Templars with shields until Blizzard gives the green light.
(Credit: Blizzard/Activision)

The epic Diablo III role-playing game experienced several hiccups on its launch day yesterday, as players reported numerous errors preventing gameplay. Not long after the launch, some concerned players hit parent company Blizzard's support forums with concerns about "Error 3006", perhaps the worst error seen so far.

The bug, which only affects the Demon Hunter class, supposedly occurs when one equips a Templar follower with a shield early in the game. Performing this action reportedly causes the game to disconnect the player immediately, and then follows up with a disastrous repetitive "Error 75", which continuously prevents the user from further log-in.

According to Blizzard community manager Takralus, "The current workaround is to not give the Templar any gear until after you accept him as your follower through the UI pop-up." A hot-fix for the issue may come as soon as today, according to a Blizzard representative.

The Demon Hunter/Templar issue comes hot on the heels of lengthy queue times and repeated failed log-ins by those trying to play on launch day, due to high demand.

"It took about an hour for a group of nine people to log in after launch," said Jensik, a Diablo III player who spoke with Crave. When asked whether the day-one issues were surprising, Jensik responded, "Launch-day errors from Blizzard aren't really uncommon."

Blizzard brought down the North American Diablo III servers halfway through launch day, with an official follow-up statement: "We are in the process of performing an emergency maintenance for Diablo III servers in the Americas to resolve several issues that are currently impacting the game. This maintenance may cause some interruption in communication, ability to log in, use of in-game features and disconnections."

The servers were due to come back online today at 8.30am AEST, according to Blizzard.

Aside from the planned maintenance, common errors due to heavy log-in traffic included "Error 37", "Error 3005" and "Error 3006". The official Blizzard fix for these issues: "If you receive either of these messages while playing, please wait and try again".

Via CNET



Add Your Comment

Avatar
 

Be the first to comment on this story!


Post comment as


Sponsored Links

Recently Viewed Products