Diablo 3 - Interview @ RPS

[RPGWatch]

This Diablo III pre-release interview at Rock, Paper, Shotgun is almost irrelevant now but it features Leonard Boyarsky and gives me the opportunity to link some Diablo III error gags. A snip:

RPS: Just to go back to the world briefly, there was a shift from the first Diablo, which was very claustrophobic, a dungeon full of horrors, and then Diablo II planted a world on top of that. In the third game did you want to continue that progression?

Boyarsky: Well, we tried to open up the world because we want it to feel like a place you're inhabiting. But we did want to go back to...well, it's very hard in an action game to get that horror feeling, but we wanted to try and invoke that and get back some of the Diablo I stuff. That's one of the reasons we have you start in Tristram, besides the story itself. We thought it would be really cool to revisit that area and revisit the cathedral that you were in back then. We really wanted to touch on that and make it part of the experience.

While you're looking at that error screen and waiting to play, you might enjoy (or not) IGN's Best Error 37 Jokes and Qt3's Beginner's Guide:

After the jump, I bring you the wisdom that can only come from first-hand experience

Error 37 means the server is overloaded and you won't be able to connect. Error 315300 means that you CTL-C'ed the password from the front end of Diablo III and have been CTL-V'ing in a series of asterisks as a password, and that's not your password. Error 3006 means the game can't retrieve the character list you haven't even made yet because you've been getting errors 37 and 315300 for about an hour. Error 3005 is pretty self evident in that it tells you that you've been disconnected. Of all the errors, error 3005 is the most newbie friendly.