In the sixth epic episode of BlizzCast, we spend a day with a developer and find out what life is like for World of Warcraft Lead Tools Programmer Monte Krol. Next, we take a look at StarCraft II unit design from concept to creation with Senior Art Director Samwise Didier and Lead Game Designer Dustin Browder. In our third segment, Bashiok spends some time with Anthony Rivero, senior artist for Diablo III, and discusses “bridging the gap” in the series’ character design. Bornakk wraps the episode up by answering some questions from the community.

~~~~~~~~~~~~

Welcome to BlizzCast Episode 6!  This is Nethaera from the World of Warcraft Community Team.  We’ve packed this episode with Interviews with designers from World of Warcraft, Starcraft II, and Diablo III.   

To start things off, I’ll be interviewing Lead Tools Programmer, Monte Krol in our feature, Day with a Developer.   

Also in this episode, RTS Community Manager Karune interviews Senior Art Director Sam Didier and Lead Designer Dustin Browder.  They’ll be taking us for a stroll through Starcraft II Unit design from Concept to Creation.  Diablo Community Manager Bashiok takes us into our third interview with Senior Character Artist Anthony Rivero where we bridge the gap in Diablo character design. 

Last, but certainly not least, Community Team member Bornakk takes us into our Q&A session where we will be discussing topics from the community with designers from World of Warcraft, Starcraft, and Diablo.

Day with a Developer
Monte Krol (Lead Tools Programmer for World of Warcraft)

Nethaera: Welcome to the Blizzcast Monte.  Monte, go ahead and describe a little bit of how you came to Blizzard, what positions you’ve held, and what a lead tools programmer does.

Monte: Sure, thanks Danielle. Well I’m a lifelong video game player. I started way back as early as I can remember and started on the Atari and had Atari computers and learned to program pretty early on. So I went through a couple of different majors in college and eventually popped out with a degree in computer engineering and with my shiny new degree went out and took a really lousy job. It got better though, and after that I was working on product development writing software. And I enjoyed that very much, but my kinda life’s passion, what I went home and did was play video games. I still, you know, all through college, all through high school, earlier, even after I got out what really drove me was games.

So after a couple of years of writing software, I thought, you know, I can do this game thing and I was living in Chicago at the time, I’m a native Chicagoan, and I found a little teen tiny game company out there called Game Refuge, and the founders of that were old arcade veterans.  They had done some really classic arcade games: they worked on Rampage, and Tron, and Spy Hunter, some cool old stuff like that. Kind of a fun group to work with and they took a chance on me it was kind of cool, so I spent a couple of years there.  They were a small shop though and after awhile we were looking, it was unclear if we were going to have some future projects. So I had to look a little bit bigger and better, and by that time I had already killed more hours than I care to talk about playing Diablo and Starcraft. So when the time came to start looking, I thought you know, I really love those Blizzard games, let me see if there is something I can offer Blizzard.  And, there was a job for a Tools Programmer, at the time, and what I was doing at the other place was writing a lot of tools and it was arcade development so it’s kind of different from what we do here but a lot of the skills lined up. 

So I applied and I got a job as a tools programmer and at the time, this was in 2000, I was working on technology that was shared between World of Warcraft, which was a tiny budding little project at the time, and Warcraft 3 which was in full development. So, for about a year we worked on shared technology and then we split the techs, and I finished up on War 3 and worked on Warcraft 3 and its expansion, and then Starcraft 2, and now I work on World of Warcraft.

Nethaera: Could you then go ahead and explain a little bit about what a Lead Tools Programmer does?

Monte: Sure, absolutely. So, the Lead Tools Programmer, as Lead Tools Programmer, I’m in charge of the tools group for World of Warcraft. I currently have five staff members, programmers, who work for me ( a sixth one to start very soon) and we build the programs that the rest of the team uses to build WoW.  We have a couple different kinds of programs. We have ones that we write from scratch and we have ones that are add-ons to other programs.  For instance all of the animators and digital artists use 3D-Studio Max and Maya in order to build and animate characters and then we build add-ons or plug-ins to them that allow us to extract data from that and put it into WoW. In addition to that, there’s about, oh, about a hundred designers and artists total on the floor that use one of our main programs called WoW Edit. It’s kind of our big flagship program in order to build everything else in the world.  They build the terrain. They add decorations to it. They place spawns or mobs out in the world. They build encounters. So we build the programs that they use to build the stuff for WoW.

Nethaera: Let’s go over a normal day for you, maybe yesterday, what happened yesterday and what are you currently working on?

Monte: Sure well we’re pretty close to the end of Lich King (Wrath of the Lich King) now, now that it’s in beta, so our days are kind of anything but normal right now.  So we have kind of a mix. We have a lot of tools and WoW has been in development for a long time so there’s stuff that’s older, stuff that’s newer, and there’s a lot of what we call fire fights.  Sometimes there will be a bug that prevents someone from working and we’ll have to drop something and take a look at that right away. Especially if someone thinks they are losing data, that’s very serious to us, so we want to make sure that their work flows as smooth as possible. If we make the work flow good, the designers make great stuff with WoW.  So it’s really important for us to try to optimize that, make that really good.

So yesterday we had a bunch of fire fights. In between those fire fights we’re looking at bugs and getting bug reports from the field. We’re also trying to work strategically. Kind of, for the lifetime of WoW, what are the cool things we want to do?  What would make everyone’s work faster? What would make everyone’s work better? Our goal is to make the tools fun and easy to use and we want the designers to come into work and want to use our stuff so we spend a lot of time thinking strategically about how to make the UI better, about how to make parts of the program faster, about how to give them better feedback about what is going on, let them see encounters earlier. Let them work with more textures. Let them work with more creatures. Just all of these types of things that we look at to try to make it as cool as possible for them to build cool stuff for everyone to play.

Nethaera: Can you go into what a tool actually is and what they are generally created and used for? You kind of went into this a little bit. Can you get into a little bit more of the specifics for those people that are kind of looking at the idea of getting into this kind of design?

Monte: Yeah, sure. I’d love to do that. Broadly speaking we have kind of four categories of tools that we work on. So, in depth, I think that the biggest one, the one that has the most people dedicated full time to it is WoW Edit, certainly our most complex tool.  The entire world kind of gets built in it. The first people that get the crack at WoW Edit are the exterior level designers. They literally lay down the terrain.  They’re terraforming out there. They literally check out a chunk of the world, and it starts as a flat plain, and they start dragging it around to give it shape and form then they paint down what the world will look like on top of it. They add grass and rocks and snow and water and then they add roads and then they add bare patches and then they add transitions and scorch marks.  All of these things right on the world.

Nethaera: Right. They just layer everything in there.

Monte: They make it. They literally form the world right underneath our eyes. They also add what we call doodads. And doodads are trees and rocks and little patches of butterflies and other things that kind of go everywhere in the world there. And then it’s time to spawn the world and spawning is the process by which they give it life by adding mobs to it.     

And so another group takes over and starts spawning it and they start building the groups of mobs that are out in the world and they start building the encounters. Ultimately, they place the dungeons. They place the buildings. They place the guy who walks around and wanders in a circle. They place the crazy old guy who chatters at the edge of town. They place all the rare spawns.

They place all that stuff and then the quest guys get going on it and they attach quests to these guys and they start attaching rewards to them.  And the World Event Team eventually gets involved and they do crazy things like Brewfest and the summer festival, and all of these people are all working in WoW Edit.  WoW Edit has a 3D view of the world and probably 400 different aspects of the game that can be edited within it.  It’s pretty big and gnarly.

Nethaera: What kinds of tools would we maybe not create ourselves, and why not just always use tools produced by outside sources?

Monte: Oh, those are great questions.  And we agonize over that frequently to be honest. The types of things we haven’t produced in house, we haven’t produced anything like Photoshop or anything like 3D-Studio Max or Maya.  Both of those, or sorry, all three of those products have a really long development history and people much smarter than me have spent lots and lots and lots of time working on them. And frankly, they’re so good at what they do, I don’t think it would make sense for us to try to re-implement that in house, plus in those cases, those products are very flexible.  We’re able to add on to them as necessary in able to get data from them. It’s not always puppies and kittens, we sometimes have some problems, but for the most part, it really makes sense to leverage that big body of work. 

Now the flip side of that, why don’t we just use all external tools is, well… Part of the Blizzard character is, there’s a certain flavor to what we do. Our core competency is building real expressive art and animation and stuff that really captures the Blizzard character. And to do that we need certain levels of flexibility.  That means, it’s very strange, you would really need to understand the inner workings of what we do, but in order to capture a lot of that performance that the animators do, that our artists do, we really want to be able to really really have fine control over the data that comes from these programs.  So we end up writing our own tools in order to capture things that are maybe just handled too generically in some of these other tools.

Nethaera: Things that kind of add in that Blizzard style that we’re known for.

Monte: Yeah, absolutely. Yeah, very much so. There’s a lot of that, plus you know, we have a work flow that’s probably different …  It’s related to other work flows in the gaming industry but it’s very very specific to how we build WoW. So we want to build customized tools that help our people who are most familiar with their work flow and how they want to work, we can really maximize the productivity and help them make cool stuff faster.  That’s ultimately what my goal is as the lead of this group, is to help them just make the coolest stuff they can as quickly as they can and we can do that by really fine tuning, customizing the tools to how they make the stuff.

Nethaera: What’s positive about creating our own tools, versus the down sides to doing that?

Monte: Well what I think is positive about it is just that level of control that I was talking about where we can really, we can go talk to a designer and say, “Hey, what are the things that would make your job easier?”  And he can give us a list of things and we can go make those happen and then he’ll come back and say I’m able to do my job five times faster or ten times faster.  In one case a guy told us he was able to do his job twenty times faster because of a certain improvement that we made.  And we were like, well why didn’t you tell us that sooner? But that was hugely positive improvement to the work flow. 

The downside of course that is the downside in all software development is bugs.

Nethaera: Right. Bugs happen.

Monte: Oh, bugs happen and we’re affected by them too and when we have bugs we affect all of the production of WoW so it’s a little bit of a stressful kind of environment where we really have to take seriously that we can control how quickly WoW gets made, right? For good or for evil. (laughs)  So that’s something that weighs heavily on the team, but certainly the rewards outweigh the stress and the risk there.

Nethaera: What has been your most challenging task to tackle and what was the outcome?

Monte:  My most challenging task at work, I would say really taking over the tools team and just being in charge of WoW Edit.  WoW Edit is, it’s a product and it’s a product that we ship before WoW ships, we have to ship it beforehand and our customers live on our floor with us. You know they don’t write on the forums, they come and line up outside my office if there’s…

Nethaera: They can walk in your door and say, “Hi”.

Monte:  They sure can and they sure do.  So I think the toughest project we have is ongoing and that is to make WoW Edit really a world class, truly fun, truly productive development environment for all of the people who need to work on WoW.

Nethaera: What’s been the most fun task?

Monte:  Well programming or non programming?

(Laughter)

Nethaera: Programming

Monte: Ah, non programming I got to do some fun voice work, so that was a good time.

Nethaera: Oh wait, no, let’s hear one. What do you have for us?

Monte:  Well for voice work I had the opportunity to do some goblin voices, so uh, the goblin that kinda sounds sort of unhinged in the game, there’s a couple of different goblin kits, but the one that sounds really nuts? That one was me.  You want to hear a sample?

Nethaera: Yes, I do.

Monte:  Ok.  (Goblin laugh) “Time is money friend!”

Nethaera: (laughter) That’s great.

Monte: It only takes a little bit of caffeine for me to uh, kinda get up in that register there.

Nethaera: No sugar needed or anything? Just the caffeine.

Monte:  Nope, just straight caffeine. A lot of programmers run on just caffeine.     

Um, I would say the most fun task that we do are also some of the hardest. But a lot of the fun tasks that we do are building the 3D tools, the stuff that interacts with 3D Studio because that gives us the most visual, kind of hands on look into the art. When we do that stuff and we do it well, we get a lot of gratification in watching the artists build really cool characters and the animators make these really cool animations, and we get to see it come to life. So we build tools that allow them to visualize it, allows them to be able to dress up characters, allow them to add that stuff to the game. So, especially, the 3D part when we really kind of see the life coming into the game there. That part’s really fun, also, really hard some days, but it’s worth it.

Nethaera: For someone maybe looking to get into a programming position what would you recommend they do, how could they go about getting the knowledge and experience they would need to come work at Blizzard?

Monte: So that’s a great question, Danielle, and I would absolutely recommend Computer Science.  I really think that getting a degree in Computer Science really really gives a good strong foundation for the kind of skills you need to come work on my team.  Within that I do have a couple specific recommendations.  We use lots of C++, I get the question all the time, what kind of languages should I learn? I’m working with C Sharp.  I’m working Java. I’m working with C++.  I look for generalists, you know, people who are good on their feet , who can kind of use the right tool to solve a problem that we have. By far the largest set of that happens in C++, so I would recommend, learn C++.  The other thing I’d recommend is learn math.  Math turns out to be really important : linear algebra, trigonometry, a lot of stuff we checked out in turns out to kinda come back in force.

Nethaera: Actually have some use, huh?

Monte:  Oh, it really does. Especially when we do 3D graphics.  It’s really really important. Trig is important. Linear Algebra. Matrix Math.  That stuff kind of comes back in force.  It sneaks up on you too, you think “I won’t need this to program” but then all of a sudden, “hey!”

Nethaera: And then suddenly you’re looking at a problem going, “Oh, yeah I might need that.”

Monte: Yeah finding the math book is like the moldy tome out on the shelf there.  Crack it open, hopefully the pages are still intact and see if you can find the uh…

Nethaera: Flip to the back where the answers are…

Monte: yeah

Nethaera: And hope that it’s there.

Monte:  Yeah right, the chart in the little overleaf, look for that.

But, the math turns out to be really important, so I would definitely tell people to make sure to study the math. 

So, a couple of more pieces of advice.  Since I look for generalists or people who are kind of quick on their feet to solve problems, there are a couple of other languages that can be sort of useful doing one off development or data processing kind of stuff, so I look for people who have some background in something else maybe, maybe a little bit of Perl or Python or Ruby, those all turn out… Those are popular today and they turn out to be really useful for solving problems.  So I think that’s some good stuff, I look for that. 

And my last piece of advice for getting involved is to get involved.  I know that sounds kind of like a totology there but there’s a lot of opportunities to kind of, without having to go out and actually get a job, there’s a lot of opportunities to get involved in game development. For instance a lot of people who want to maybe get involved with WoW, we recommend that you… Like if you’re not sure, you’ve never worked in programming and you’re not sure if you’ll like it, not sure if you do, you can try writing an add on for instance for WoW.  And the UI part is written in XML and the programming part is written in LUA, which is another programming language that’s pretty easy to pick up.  It’s similar to some of the other ones we work with and it’s a great way to kind of get a feel for the kind of work we do.  And when we interview, we look for those sorts of sets of skills and some interest. So if you’ve written a WoW add on, or a War 3 modification, or like a conversion for Half-Life or a Quake mod or those kinds of things, those go a long way towards helping get into our industry.

Nethaera: Alright, well I’d like to thank Monte for coming on BlizzCast Episode 6.

Monte: Danielle, it was a great time being here, I had a lot fun, thanks so much.

Nethaera: Thank you. Up next is Karune with our Starcraft segment.

StarCraft II - Unit from Concept to Conception
Sam Didier (Art Director - StarCraft II, Dustin Browder - Lead Designer - StarCraft II)

Karune: Welcome Dustin, Sammy, we have Dustin Browder our lead designer for Starcraft 2 here and also Samwise our art director for Starcraft 2.  We’re going to be talking a little bit about how units are created from the concept to final creation of the unit actually in the game.  Welcome guys.

Sam Didier: Hail!

Dustin Browder: Hey.
Karune: So for units, I mean how do these units actually start up.  I mean I don’t think a lot of people wonder, you know, does it start from a gamplay element like you guys have a specific unit in mind for a certain gameplay mechanic or does it actually start from the art side, you know this unit looks really rad?

Dustin Browder: It’s a pretty organic concept. I think it sort of depends, right Sammy, on which way we go.  Sometimes we start with the art first, sometimes we move from the design first and sometimes we have different, you know, we have a piece of art we have a piece of design and we try to marry them together. 

Sam Didier: Yeah a lot of the times the artists will just have a cool idea we’ll show it around and everyone will go “Yeah we got to get that in the game.”  And then sometimes the designers will have an idea or two “Hey we need something that will ‘this’ and ‘this’ and then the art team will start concepting things up and from there we just let it roll and iterate, iterate, and iterate and at the end of the day we have a finished unit that we will redo three or four times. 

Dustin Browder: (laughs) Right and be balanced a thousand times before it’s finally done. 

Karune: So what are some of the examples for a gameplay unit?

Dustin Browder: So some of the gameplay units we’ve had like, I think the Colossus is kind of a good example.  There’s a unit that we had an idea for a cliffwalker we wanted to do for the Protoss, we wanted something very large that could do some area affect types of damage and It obviously kind of suggested, maybe, a kind of art for it but then the artists really took that core mechanic and ran off and did some really cool stuff with it. 

Sam Didier: Yeah we did all drawn inspiration from some of the giant walking robots and tripods but if you notice our Colossus has four legs, not three.  So our tripod is way better then everyone elses because we have one more leg.  Take it!

Dustin Browder & Karune: (laughs)

Karune: So what about the art side?  Is there a particular unit you guys have in mind that came specifically from art?

Sam Didier: Well we had an idea, on the Terran side, we had the old Goliath.  It was cool.  We had the Valkerie.  It was cool.  But we wanted to kind of make the Terrans a little bit more new.  We wanted to add some more transforming to the Terran side so we said “Okay well what if each of those was one stage of the unit and then it transforms?”  So now you have an air attacker, you have a ground attacker, whatever they end up doing at the end of the day whether it’s machine guns on the ground, missiles in the air, whatever, we knew we wanted to have some kind of transforming robot.  That was one of the areas of sci-fi lore that we hadn’t had.  We all grew up in the eighties and nineties watching transformers so that was something really dear to our heart that we wanted to put in. 
Karune: Everyone was waiting for that.

Sam Didier: STARSCREAM!

Dustin Browder: (laughs) Yeah I think units like the mothership, I know when I first got to the studio from the original movie for the beginning of Starcraft had a very huge Protoss ship in it that shot a terrible beam and destroyed the small terrain salvage ship and this was a unit that was part of the lore but we never actually saw in the game so the idea of a mothership, I think, had been floating around the studio for quite some time just based on that opening cinematic on that really cool piece of art.  And so there was an example of a unit that sort of came from art and lore first and then we’d been working on different mechanics for it now for quite some time to make it work in the game. 
Karune: Interesting. Are there units created specifically for single player that isn’t for multiplayer?  How do those units come about?  How do you decide they are for single player or multiplayer?

Sam Didier: We’ll come up with a unit and we’ll all like it and then we’ll decide it’s too powerful or unmanageable and it will end up getting delegated to just single player play but we also create a lot of things specifically for single player.  Like we’ve created the Jackel now I believe it’s called the Hellion and we will take variations of that, strip off the black paint, make flames on it, and then it becomes a single player civilian vehicle. 

Karune: So what are some of the challenges in creating these units when they first come up?  How do you decide if we’re going to go idea A or B or C and so forth?

Dustin Browder:  It’s usually pretty obvious to me when we got something good.  We got a nice piece of art really if we don’t have mechanics for it you’re pretty enthusiastic to come up with cool mechanics for a nice piece of art.  At the same time, because we’ve been able to play our multiplayer for so long if we’ve got a nice game mechanic, I think a lot of the art guys are pretty enthusiastic to come up with cool art to match that game mechanic.  So when you’ve got something cool it’s pretty easy to get enthusiastic about it.  It’s just making sure we have enough of those in the game to make it exciting. 
Karune: Can you guys guide us through one of the units you guys created and maybe the process on how that unit was created?  Any challenges you guys faced while also creating that unit?

Sam Didier: One example was for the Terran side was the Thor: big giant, earthshaking robot.  Great, cool, cool, sounds awesome.  We ended up doing the concept then we started the modeling and we always tweak when we’re in modeling nothing ever really follows a concept a hundred percent.  And then after that we animate it, texture, animation and all that.  The problem with it we had in the concept is we had these giant guns on his shoulders.  ‘Real cool!  Yeah that looks awesome!’  Well anytime we have something cool in the art like that we have to justify it in gameplay.  So it had these giant guns, what’s it do? Well we already have a siege tank that rains death upon the battlefield so what do these big guns do?  Rain bigger death?  That makes the siege tank obsolete.  So we couldn’t do that. So one of the problems with this unit is we went with the art first and because it had the big cool guns now were trying to figure out what to do with it design wise.  At the end of the day it will be perfect mind you.  But you know we’re still working on that sort of thing.

Dustin Browder: I’m not too worried about the Thor these days.  The Thor using his cannons in the back for long range anti air has been pretty successful and that’s a great example there of a unit that started with art first, we all got behind, that everybody was really geeked up to see a giant battle robot on the Terrans, it really fit in the sci design really well and it looked awesome on the battlefield.  And then we’ve been really working on the mechanics to make them as tight as we possibly can.  And so far that’s done really well.  It’s been a very successful example of how we sort of marry these two things together. 

Sam Didier: All you guys out there listening, you should have seen how big it was before uh . . . we had to make it playable. 

Dustin Browder: (laughs) They’ll see that version in solo play I’m sure. 
 
Karune: Just for some of the non-Starcraft users Dustin, can you tell us about the Thor’s current role right now in Starcraft 2?

Dustin Browder: So the Thor does two things for the Terrans: It gives them a sort of tip of the sword kind of unit, something you can push up front that can take a lot of damage from enemy fire.  It’s very survivable, very tough, very hard to kill.  And you can use that sort of push past an artillery barrage or push directly into an enemy base to sort of lead your smaller lighter marines into battle.  And it’s also got these huge cannons on its back that can strike against air targets so you can use the Thor to defend your forces from enemy air threats and it’s a very powerful weapon in both of these roles.  So it really gives the Terrans some additional flexibility in the battlefield they haven’t really had before. 
Karune: Nice, nice.  Obviously a very sweet unit.  The Thors a great example for a unit that really came from art, could we talk about another unit that came specifically from gameplay side and what some of the challenges were in that terms?

Dustin Browder: Sure.  So I think a unit that maybe we’ve been working on a little while, we’ve liked for a long time on the gameplay side is the roach.  And this was just an idea to have a very simple zerg unit that regenerated very, very quickly.  And when you combo this with some clever micro using burrow or even just a straight attack move, this is a unit that creates a lot of choices, a lot of fast paced gameplay for both the owner of the roach and the person who’s fighting the roach as well.  And so it was definitely a unit we’ve wanted to have for quite some time.  We’ve worked on it for quite a long time before the art really got into play. 

Sam Didier: Yeah and basically art-wise when the designers came up to us and said they wanted this type of unit and the name for it at the time was the roach, we kind of just ran with that.  We wanted a squat little nasty beetle looking thing that like a real roach will survive nuclear bombs and siege tank barrages and all that.  So that sort of dictated the art.  One of the things that happened recently was, I say recently within the last year, years are like minutes here, it was actually a melee unit.  It would get up close and just chomp at you.  But now it’s a ranged attacker. 
Karune: So for the roach unit, could you tell us a little bit about the process of actually creating the unit on a the more technical side?  Going through animation and modeling and so forth. 
Sam Didier: Yeah basically, I think I covered a little bit early, but we’ll have a bunch of our artists do some concepts and we’ll look at the different pictures and say ‘Oh I like that.  Oh that part looks cool.  We should add that to this one over here.’  So after a couple of iterations on the concept we’ll settle on one and then we’ll sic one of our artist to start modeling it.  And they’ll model it up, they’ll start mapping it, we’ll have our texture guy, if it’s not the same guy who modeled it, start working on it and then it’s ready to be handed off to the animators.  And the animators will hit up and we’ll go through various stages of the animation, we’ll have a, here’s a quick walk skittering across, here’s one that makes it look like it’s lumbering.  We’ll see which one looks the best because the walk is basically what you see the most with all these units.  Then after that we’ll pick one and then we’ll go on and settle on an attack.  ‘Oh we want it to really reach out far.’  We want it to ‘this’ or ‘that.’  After that the unit’s all done then we’ll move in on to the portrait.  This is where you get all the character on the unit.  You know you can’t really see their faces on the field of battle so we have the little portraits there.  And that’s where we’ll come up with, ‘Okay the roach needs to have this.  We want to focus more on little beady eyes.’ And this and that and lots of little teeth.  And so after that, we may need to go back to the unit and tweak the face that’s on the unit to match more to the portrait.  But after that it’s pretty much done and then, barring any design changes or if we’re allowed to add more polygons, we hopefully have a finished unit there and then we’re done with them. 

Karune: Kind of a side question: What is your favorite PIP animation or your portrait animation for the units in Starcraft so far?

Sam Didier: So far, I think for the Terran side, I like the Thor.  I don’t know if any of you guys have seen it yet.  The marauder also has a killer portrait.  For the Protoss, for some reason the zealot, it was our first one but I think it captures the Protoss look.
Karune: That’s the one from the announcement right?
Sam Didier: Awesome yeah and the high templar.  And then the Zerg we have a couple new ones that I don’t know if people have seen but we have one’s for the baneling and for the mutalisk and those are just looking killer
   
Karune: So, on average, how long does it actually take to create a unit from this beginning portion when you guys concepted and then to finally creating everything with the PIP animation, the death animations and so forth?

Sam Didier: About six years.

Dustin Browder: (Laughs) It really does depend.  Sometimes it does take quite a long time.  A unit like the baneling for instance went through the whole process extremely quickly and hasn’t had any significant changes since it first went into the game.  More complicated units like a Mothership or a Viking or a Reaper sometimes go through some significant changes as they go throughout the process and they can take a lot longer especially if we end up moving around the design a little bit.  If we end up changing some of the core mechanics on the unit like we did with the roach where we changed it from being a melee attacker to be a ranged attacker that obviously has an impact on the art and it obviously lengthens the amount of time it takes them to make that unit work in the game.

Sam Didier: Yeah we have a lot, even now, in games that people are playing now we have a lot of placeholder art still.  And we have that in there so that if the designers have a new idea they want to try, we’ll come up with some place holder art that looks cool but it’s not one hundred percent polished because there is no reason to polish this unit all the way to one hundred percent if we’re going to end up taking it out or…

Dustin Browder: If we’re going to chuck it or change it or…

Sam Didier: Yeah, we’re still going over, and I’ll talk with Dustin say,

‘How are we on this now?  Are we good to go? ‘

‘We’re good to go.‘   

‘Okay.  Ninety percent or a hundred? ‘

‘Ninety percent.’

‘Okay Ninety percent is good enough we’re going to finish it off.’
Karune: Are there any other units or anything that the public hasn’t already seen as far as with Starcraft 2?

Dustin Browder: That they haven’t seen yet?  Well I think we’ve been talking about the giant voltron unit made of all of the vehicles; and units of the entire Terran race.  Is that right Sammy?

Sam Didier: Yeah see that’s more of a designer thing.  Personally, guys on the forums, I don’t think that would work so you know if something like that gets in where every single unit on the Terran side turns into a giant robot, that’s probably not anything to do with my decision.  It’s probably Dustin’s. 

Dustin Browder: What about the flying two headed ultralisk that breaths fire?  I thought we were going to do that one as well.

Sam Didier: Yeah I think that one could work

Dustin Browder: That’s probably what’s coming up next: the flying two headed ultralisk that breathes fire will be on the website next.

Sam Didier: You’ll be seeing those in single player only probably.
Karune: So it seems today we’ve seen a lot of units come from either a gameplay origin or an art origin in how it first starts, which is better do you think for Starcraft 2.

Sam Didier: Well if you want something that’s totally bean ‘countery’, you know, predictable and kind of boring then yeah the design one is the best. 

Dustin Browder: And if you want something that doesn’t really play and it’s just pretty but it’s no fun then I think you want to go with the art way.

Sam Didier: : Oh is that how it’s going to be now?

Dustin Browder: That’s how it’s going to be.
Karune: We got some weapons here in the sound studio…

Sam Didier: I don’t need a weapon for him!  Please.

Karune: All right guys, thanks a lot for talking to us

Sam Didier: All right, thank you.  Dustin.  I’ll be talking to you later.

Karune: (laughs) Take it easy guys.  Hope you guys enjoyed our Starcraft 2 segment.  Next we have Bashiok with Diablo 3. 

 

 

2 comments

« Wrath of the Lich King Breaks Sales Records

Athene's Mother Gets Involved in Level 80 Fiasco »

You must be registered and logged in to post comments.