Posts with tag blizzard-developers

More and more Blizzard developers are joining Twitter every day. It's a great thing for us fans, because they often see fit to post interesting tidbits about their work, many of which we probably wouldn't otherwise see. Unfortunately, Blizzard doesn't announce when one of their own hops on the Twitter bandwagon. Though other Blizzard folks do usually tweet about their newly-added colleagues, thanks to Twitter's ephemeral nature, if you happen to be away from your computer when it happens, you may go days or weeks blissfully unaware of all the fun you're missing.

In the spirit of prevention, WoW Insider has compiled a handy-dandy list of all the Blizzard Twitter folks we could find so that you don't have to miss any more of the good stuff. Check it out after the break, and make sure to update your Twitter lists!

BlizzPro has posted their BlizzCon interview with World of Warcraft Quest Designer Helen Cheng and Technical Director Marco Koegler about Warlords of Draenor and the future of WoW. The interview covers a variety of topics about the coming expansion, including why the team decided to return to a ten level expansion curve instead of sticking to the five it has been more recently (it makes for smoother leveling progression, plus level 100 is cool!), how (or if!) the time-travel aspect of Warlords will affect Azeroth itself (it shouldn't, provide we heroes rise to the occassion), and why there aren't any new playable classes or races for this expansion (new character models are resource-intensive).

But those are far from the only topics discussed during the interview. Cheng and Koegler also go into whether or not Garrisons will be character-based or account-wide, and what the different challenges are within either approach. Cheng also talks in depth about daily quests and their history in the game, the shortcomings of that particular design, and how Blizzard hopes to create a more balanced questing experience going forward so as to avoid some of the problems with quests in Mists of Pandaria.

Netherspite was overcomplicated to the point of absurdity and the most enjoyable way to approach the fight was to skip it. It required a level of coordination that players had never experienced at the time. Heavy movement, beam rotations, a need to run away to avoid death, then run back in to get beams back under control. Raiders today could pull it off without issue. Raiders back then, it was far above what most players had ever seen, and it was in the introductory raid. Its difficulty was far beyond the rest of the dungeon, even.

This is what Alex told me when I asked him to describe Netherspite for me. I wanted to know because I recently found out that the Blizzard developer who designed Netherspite was reassigned to work on simpler content in the game after designing that encounter. The reason? He'd let his desire for innovation get away from him.

At least, that's what he says. His name is Alex Brazie, and he's been blogging about game design the past couple of months. In his blog, Breaking Open the Black Box, he shares his experiences and lessons learned from working as a game designer at Blizzard. The whole blog is a sort of a meandering trip through the intellectual process of game design, which you'll probably find amusing if you've seen a fair share of raid encounters over the years.

And if reading about game design doesn't appeal to you, I'll admit that I've also been reading every one of his posts in hopes that at some point he'll explain why so many strange items in the game are named after him. Here are but a few: Brazie's Black Book of Secrets, Brazie's Guide to Getting Good with Gnomish Girls, and Brazie's Notes on Naughty Night Elves. Who is this guy?!

---

Recently, Blizzard disabled the WoWArmory Facebook application, signaling that the time of the modern WoW Armory is over and we will soon live in an age when new Blizzard APIs will transform our out-of-game experience. And change it, they will. These forthcoming APIs will change the way you interact with WoW outside of the game in ways you cannot even think up yet. How do I know this? That's the power of information facilitation, and some inventive hypotheticals will show you what Blizzard's APIs will do for you in the near future.

Over the past few months, Blizzard has been preparing to roll out a new set of APIs that will take internal information from the Armory, the new community site, and more, parse it into easily manageable data streams, and make those streams available to application developers. With these new streams of information, savvy developers can craft web applications, smartphone apps, social media plugins, and anything else under the sun to provide you with new and dynamic WoW experiences on the internet. I know that sounds horribly cliché, but hear me out -- this stuff is pretty cool, and the back end could bring about a new standard for information availability and MMOs.

I'm not a developer. In fact, a lot of us in the community are not developers. Writing this story felt like an exercise in obscurity because, frankly, all this back end information isn't in my wheelhouse. As I dug deeper and began to realize the potential of the systems being set up, I fell in love with the idea that Blizzard is opening up easy access to so much information. I thought it would be a good idea to illustrate for those of us who have no idea what APIs are capable of, to break through the programmer/developer talk and discuss what these APIs mean for us, at the end of the day.

Blizzard previously announced that certain APIs were going to become available for applications and players to access from the community website. We've finally got a preview of the information feeds that tap into character data in the near future. These feeds can be used in applications, websites, and more for user-created, World of Warcraft ... well ... anything.

Blizzard's opening up of these information feeds is pretty cool, and you will likely see some ambitious applications of this data being used in the near future. One of the illuminating aspects of this preview is that after finding the right way to do it, the devs are thinking about opening up quest ID information so that you can see what quests characters have or have not completed. There are tons of applications of that data out there and I'm sure the community is really excited to make use of this API information. Check out the full preview after the jump.