The epicrole-playing game experienced several hiccups on launch day today as players reported numerous errors preventing gameplay. Not long after the midnight launch, some concerned players hit parent company Blizzard's Battle.net 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" that 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 off 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 if 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."
Blizzard says plans to bring the servers back up at 3:30 p.m. PT.
Aside from the planned maintenance, common errors due to heavy log-in traffic include "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."