Breaking Open the Black Box

The Secrets and Stories of Game Design

Pages

[mc4wp_form]

Post-Mortem 8: Netherspite

by

I’ve had more people ask me to do this post-mortem than any other in the history of every project I worked on at Blizzard.  What is it about this encounter that struck people so poignantly that 7 years later, I still hear about it?

Well, it all started with a drawing.

Nether Dragons

Scott: Good morning gentlemen.
Joe/Me: *mumbles/grunts*
Scott: Chipper, today.
Me: *sleepy 9 am glare*

Scott: I have just the thing to wake you up. TADA

Scott showed us a drawing of a very badass serpentine creature with energy flowing out in every direction.

Me: Oooh, cool!
Scott: Yessss.  And this is the creature Metzen and I think we should use in Medivh’s Observatory.

We had left the room empty for a little while now, as one of the optional encounters, it was less important to be filled out early on in production. 

Joe: What do you want it do to?
Scott: I’m not sure yet. Let’s discuss at the next meeting.

At the meeting the next day…

Geoff: Nether dragons look pretty cool. If the story goes that they existed in Outland though, how on earth did they get here.

Scott: Well, the current story is that the empty space outside of Karazhan is open to the Twisting Nether – which means these creatures just wander the empty space and fly in there.

Geoff: That’s still a little weird. What if it could open portals and it came in through one of those tears instead.
Me: Oh that’s interesting, maybe we could use it in the actual fight abilities.

Geoff: Ooh,  yeah, like portal open up and blast him with energy. Then spin around the room.
Me: Uh sure…. who’s working on this one again?

Scott: Hmmm… Geoff, you seem pretty excited. Do you want to take it on?
Geoff: Sure, but that would mean giving up the demon prince at the end.

Scott: Erm, no, nevermind then. I really want you to finish that one first. Joe?
Joe: I’m still working on the sacrifice mechanic for the Satyr.

Scott: Well, Alex, how’s Shade?
Me: Done.

Scott: *skeptical* Done?
Me: Well… I have to have more QA playtests… but I mean yeah, he works.

Scott: Alright, I guess the design for that fight was pretty tight. Go ahead and work with Geoff to come up with the kit for this one.
Me: Okay!

Nether Planning

Art by the talented John Polidora

Geoff: Yeah, so I am pretty busy. What do you think about those portals?

Me:  It’s a cool idea. Maybe the beams could come out and infuse you with power.
Geoff: Oh yeah! What if when the beams hit him he powers up and you step into the beams you steal the power for yourself.

Me: That sound awesome!

Geoff: Go ahead and be crazy with this one. Make the players like veritable gods when they have the beam on, hahaha.
Me: Alright!!

I hurriedly rushed off to create the kit. 

 

Netherspite Version 1:

I spent the majority of the next week crafting the scripts that made the portals “work”.  At this point in WoW’s development, the one gameplay programmer, Sam Lantinga, was in high demand… and it was nearly impossible to get new game features.
Thus all of the new features were generally forcibly scripted into the game with gratuitous amounts of Lua.  This one was no exception. After a week:
Creature Model
Abilities:
  • Melee – 50% harder than anything else in the game
  • Shadow Damage – unavoidable shadow damage to everyone in the room.
Blue Beam – Target deals 100% more damage.
Red Beam – Target takes 50% damage.
Green Beam – Target gains 50% healing and
restores 10% of max hp.

This boss was surely intense! Just look at those numbers! Such power, so amaze!

First testing attempt:

Jeff Kaplan: Okay! here I go!
*dies instantly*

Jeff: Ha! Okay, I just need to shield wall on the pull. Revive, I got this.
*dies 10 seconds later* 

Jeff: Uhm, okay. Maybe this is overtuned. I’m going to double my health.
*30 seconds into the fight, someone misses the green beam and netherspite instantly reheals* 

Jeff: Uh… that sucks.
*1 min into the fight, someone with the blue beam pulls aggro and instantly dies* 

Jeff: Hahah, Joe! Learn to hit evade.
*2 min into the fight, someone misses the red beam and Netherspite instantly one shots him* 

Jeff: OKAY, WHAT THE FUCK?!
Scott: I thought I was standing in the beam.

Joe: I thought the same thing too… but I couldn’t be sure, the dragon was right in my face.
Alex: It was really hard to tell…. because it shot over your head.

Scott: Why does it do that?

Alex: Well, what are my other options? The bloody wyrms are floating 10 feet above you at that scale.
Scott: Ugh. I’ll go talk to the animators.
An hour later… 
 
Scott: Uh, guys.  I have some bad news….
Alex:  They couldn’t fix the animation?

Scott: Uh… worse. All of our animators quit…
Joe: …

Alex:  So …

Scott: Just make the beams snap to the ground and replace the model with that transparent green dragon model Roman Kenney made for now. We’ll replace it with something better before ship.

Alex:  Got it.

Life Lesson:

Unpredictable shit happens. When it does, you need to make the best of it.

Joe: Oh yeah, and Alex, these beams should be fun for the people who use them. Can you do something to make them a little bit more
Jeff: Also… if I’m in this beam, I want to be like the god of tanks.
Alex: Okay…
Joe: But Jeff, if you’re the god of tanks… why would anyone else ever want to use it?

Geoff: Oh yeah… that’s a good point. It really seems like you should want to switch around who is using each beam.
Alex: How would I go about doing that?

Geoff: I don’t know… force them to switch who is on the beam… just kill them or something.
Alex: Alright….

Netherspite Version 2:

“Temp” Dragon Model
Abilities:
  • Empowerment – Gains 100% additional damage 15 seconds after being aggroed.
  • Shadow Damage – unavoidable shadow damage to everyone in the room.
Blue Beam – Target deals 100% more damage.
Dies if in the beam for 20 seconds.
Red Beam – Target takes 50%
damage gains bonus health.
Dies if in the beam for 20 seconds.
Green Beam – Target gains 50% healing
and restores 10% of max hp.
Dies if in the beam for 20 seconds.

Mindset:  I’ll do exactly what I’m told. That’s totally going to work, right?

Life Lesson:

Listening is good. Blindly obeying is bad.

2nd Playtest:

Jeff: Okay! here I go!

*10 seconds later*

Jeff: Sweet! I’m alive.

*15 seconds*

Me: Jeff. Give someone else the beam.

Jeff: What? No way, this is awesome.
*20 seconds*

Jeff: Shit! What killed me? Did I get crit?
Me: You didn’t give anyone the beam…

Jeff: Why would that kill me?
Me: Because if you keep it for 20 seconds… you die.
Jeff: *facepalms then starts laughing* Oh god.

Next attempt:

 
Everything goes smoothly. Joe and Jeff swap the beams.  Repeat for 5 minutes.
Joe:  Hm…
Geoff: Yeah…
Jeff: Well, it worked…
Me: Great!
Geoff: Not exactly… well… its kinda…
Joe: Boring. It’s boring.
Me: But I worked so hard to get those beams working.
Geoff: Yeah… that impresses us… but the players don’t really care. Ya know?

Life Lesson:

It doesn’t matter how hard you worked on something if the end experience isn’t great.

Joe: There’s a couple things here… one… there needs to be more going on. More tension… and well… anything else to break up the fight.
Jeff: Go ask some other designers for their thoughts.

Life Lesson:

Farming other people for opinions is a great way to get new, raw ideas.

Wyatt: Movement? You know, I got a lot of movement by using those void zones in Naxxramas.
Kevin: Huh… I noticed everything is percent max health, damage, whatever… wouldn’t it be better if some of this stuff scaled with gear?
Stephen: Its really hard to SEE changes like percent reduction… like buff the crap out of them in a way they can notice.
Eric: Instantly dying is bullshit. You need to give them some sort of warning. UI can communicate this perhaps if you do it right.
Jeff: Tedious fights that do the same thing over and over again get boring. Please mix it up somehow.
Scott: Keep in mind there might not be two tanks in this group. Make this fight work with like one tank and a melee shaman or rogue please.
Joe:  I keep running out of energy on my rogue. This means I’m way worse in this fight than everyone else. That’s not cool.
Alex A: These names are really placeholder. Can you spice them up a bit?

Life Lesson:

Raw ideas are great. However, getting overwhelmed by all of those ideas… not so great.

Me: Augh! This is way too much. Fuck it. I’ll just do all of this stuff at once. Also, I’m going to make it way easier to tank this.
Me: In fact, why should I even make the tank worry about aggro? I’ll just give it to him. What makes tanking work? Defense? Fine. MORE DEFENSE FOR ALL.
Me: I also don’t think its cool that the healers get to have all of the fun. Know what? No energy costs in the green beam.
Me: Hell, fuck those DPS guys who just stand in the blue beam. They should want to get out of that beam.
Me: Names? I can DO names…. oh yeah! Get Thesaurus’d, baby!
Me: Crazy? A break? Fine. Uhm… crap… all of that work just took a very long time. I have less than a week to finish this instance up. Ugh, I’ll slap on a mode where he does knockback on random people for a while.
Me: Shit. This is really hard to tune. I’m going to make separate versions of the beam effects for Netherspite and players.
Me: Predictable? PAH. I’ll show them unpredictable. What if you can’t predict where the portals will be. SITUATIONAL AWARENESS. Oh yeahhhh!

Life Lesson:

You really, really need to stop when you get on a roll.

Netherspite Version 3:

“Temp” Dragon Model
Abilities:
  • Empowerment – Gains 100% additional damage 15 seconds after being aggroed.
  • Void Zones – Opens a massive void portal that lasts 25 seconds.
  • Shadow Damage – unavoidable shadow damage to everyone in the room.
  • Every 90 sec, Netherspite banishes the portals and randomly cast Netherbreath on all targets.
  • Netherbreath: Knocks back an enemy, dealing damage.
  • Portal Resummoning: Portals randomize their positions after each Netherbreath cycle.
Dominance – Gain 1 stack per second.
Netherspite: +1% magic damage per stack.
Player: +5% damage dealt per stack.
Player: -1% healing received per stack.
Player: damage taken by spells increased by 8% per stack.
Perseverence – Gain 1 stack per second.
Netherspite: -1% damage taken per stack.
Player: Netherspite will attack you.
Player: -1% damage taken per stack.
Player: +5 defense per stack.
Player: +32,000 health.
Player: -1,000 health per stack.
Serenity – Gain 1 stack per second.
Netherspite: +4000 health per second per stack.
Player: Healing done increased by 5% per stack.
Player: Spell and ability cost reduced by 1% per stack.
Player: Maximum mana reduced by 200 per stack.














Me: Huff… huff… WHEW. Good deal. I got all of that shit in.  Boom! Play this game my way. Bwahaahaha.
Scott: What the hell… Brazie, those tooltips are a paragraph long each.
Me: So…?
Joe: Uh… does this even work?
Me: Well… QA managed to beat it… Once.
Geoff: …
Joe: …
Scott: …

Ship it.

At a certain point, you run out of time.  When we playtested Netherspite, he worked and with some iteration, we found he was consistently beatable, took a unique strategy to beat and was highly memorable.
Players adapted. They shared their strategies, in the form of webpages, wiki entries and images.
The encounter seemed fine to many… but I could never shake the feeling that something was wrong.
Even minor errors were punished. Few situations were recoverable. As Steve Burke would later say: “It was a dance. You had to take exactly the proper steps or you failed.”
Looking back many years later, with more design experience under my belt, I understood. It was such a highly “plotted” experience… you were completely forced to play it exactly the way I built it.
That was what was wrong. It wasn’t really a game. It was a physical execution and coordination check. There were few windows for unique success, personal glory or even sacrifice for the team. You just did your job, collected your loot and wandered on.
It showed in the long-term play results. Players skipped Netherspite, regularly heading to the Chess event. Later, when better geared, some groups would beat it for their resto shaman. But few felt the effort was worth the price.

Retrospective

Looking back, I see a million places to simplify and improve this encounter.  Telegraph abilities that require moments of protection from the beams.  Simplify the beam mechanics. Simplify the spell layering.
But most of all… create situations that allow the players to use their own tools, not just yours.

What did you think of Netherspite? Share in the comments! I’ll post the best ones here.

Brett Hundley – Machinama: “looking forward to some good stories in the comments, whatever guild I was with in BC was certainly not attempting him and his scary magic, haha”

Guest Post: Letting the players (w)in, or how encounter design is like operating a roller coaster.

by

Today’s article is by Joe Shely. Joe and I worked together  at Blizzard Entertainment for many years, developing raid bosses in Kharazhan, Mount Hyjal and far, far beyond.

Letting the players (w)in

How encounter design is like operating a roller coaster

“You must prove yourself to me by completing these sixteen devilish challenges,” Impossibos bellows, generating a tiny line of text in the chat log and charging headfirst toward the group of players waiting to fight him.
Only it isn’t Impossibos shouting that, not really. It’s the eight-year-old kid turned junior designer who finally has an audience for his Hero Quest campaign. The fifteen intervening years have given him plenty of time to come up with the most complicated, overwrought challenge ever. He knows it’s perfect because it’s passed the point where even he can beat it.
Our designer loves video games, loves to play, loves to create. This is his dream. He’s an expert player, probably ranked 4th on some low-population shooter or arcade title, and he’s finally made the most challenging boss fight of all time. Unconsciously, he believes earlier designers haven’t made a boss this tough because they don’t know how. They probably weren’t as skilled as he is.
Hopefully the players about to be mauled by our designer’s boss are testers, people paid to play unpolished and untuned encounters to look for bugs and provide feedback. If we’re lucky, someone stepped in before Impossibos went live and the people about to be crushed beneath his titanium spiked boots aren’t logging on after a long day to check out the new content patch with their friends.
It’s easy to blame our junior designer. After all, he has no idea what he’s doing. He hasn’t yet learned one of the core tenets of game design: the point of a boss is to be defeated. The players are the heroes of the story, and they get to win in the end. Yes, there can be heroic sacrifices. Yes, there can be struggle and challenge. But a theme park where you’re not tall enough to go on any of the rides is no fun at all.
Players do want to earn their victories, but each player has their own definition of what ‘earn’ means, and it varies from “three tries while watching TV” to “months beating heads against brick walls.”
And it isn’t enough for the encounter to be technically possible; the best encounters are the ones where every player believes they can win. This turns out to be quite a challenge, because every single player in the game has a different skill level and learns at a different rate. And most games have only three difficulties.
Hmm.
Maybe some players can contribute in different ways, or opt into specific roles that they enjoy. Maybe it’s okay if not every player is challenged equally. Maybe the sign that reads “you must be this tall to enter” doesn’t have to be the same height for everyone. But how could a single encounter work on so many levels? It can’t be too complex for the player watching TV, but it needs enough depth to appeal to the brick wall crowd.
Sounds like a perfect challenge for our junior designer.
My advice?
Tell him the boss can only have two abilities.
Oh, and don’t be too hard on him when one of the abilities has sixteen parts. He’s going to need some help with that one.


You can see more of Joe’s work over here (http://joeshely.com/project-trinity/).

Welcome to my desk.

by

Welcome! If you migrated here from my original blog, welcome back.

Please bear with me as I transform my little blog into something more… substantial.