Recent Features

The Diablo 3 Podcast #150: Legendary Gems II/II
The second part of our analysis of every Legendary Gem newly added to Diablo 3. We cover the last 11, discussing all of their strengths and weaknesses, what type of build they’re best for, twinking uses, melee-bias, and more. Featuring Flux, Katniss, and Ynzerg. See part one of this podcast for all the basic info […]
The Diablo 3 Podcast #149: Legendary Gems I/II
Everything about Legendary Gems in this two-part show. LGem basics, how they’re found and upgraded, why they are so awesome, and then detailed discussion of the best builds, upgrade values, and uses for every gem. Featuring Katniss, Ynzerg, and Flux. Due to the amount of content to cover, with 14 legendary gems, this show is […]

More Details on “Ask the Devs”

Posted 25 Jan 2013 by

Fans posted questions about the questions for upcoming Ask the Devs and got blue replies. The full thread gets redundant and nit picky due to people not reading the OP Blue announcement, so here are quotes of the core bits. Click to the blue source if you want to read every word, though it’s mostly people asking if the questions must be about v1.07, why the questions are about v1.07, if anyone knows what the questions are supposed to be about, etc.

For this particular series, though, we want to have a topic not only for the reasons I listed above, but also because it works better with the format. We’re going to be collecting the top questions from each of our regions, translating them into English, getting the developers to provide responses, translating those responses back into the other 10 languages we support, organizing everything in a readable layout, and then publishing the information globally at the same time — all within a week. Open-ended Q&As tend to work better in real-time and when they’re being conducted in only one language; the scope would just be too large for the Ask the Devs, especially if we’re looking to provide responses quickly.

We’re not asking for PR-friendly questions. In fact, we encourage critical inquiries that are detailed and provocative.

What we are asking for are questions that actually can be answered by our developers. They’re not going to be able to share release dates or necessarily confirm upcoming projects, but they can provide insight into design choices, acknowledge awareness of certain issues and concerns, as well as discuss (in a more broad sense) their direction for the game.

Sounds like this could be pretty good; lots of questions, direct answers, and a fast turn around time.