Video summary
The video explores the intricate design philosophy behind two iconic World of Warcraft raid bosses, Patchwork and Loatheb, highlighting how Blizzard crafted encounters that tested every aspect of player capability rather than relying on simple mechanics. The designer explains that Patchwork in Naxxramas was inspired by a difficult boss from EverQuest called the Avatar of War, aiming to create an experience where success depended entirely on tight tuning rather than flashy abilities. To achieve this, the team faced several challenges: tanks had too much health for standard damage output alone, healers found spamming spells tedious, and players could simply bring excessive numbers of healers to trivialize the fight. The solution involved a unique "Hateful Strike" mechanic where attacks targeted off-tanks based on their current health rather than just threat levels, forcing DPS stands in poison rivers to lower their HP so they would be hit first. Additionally, an enraged timer was introduced as one of the earliest aggressive uses of such mechanics specifically to check raw damage output without relying solely on consumables or gear stats at that time.
In contrast, Loatheb presented a different kind of challenge by attempting to force healers out of their comfort zone and into dealing damage during specific windows. Initial attempts failed because disabling healing entirely would have benched players rather than making them useful; stacking debuffs caused panic instead of disciplined rotation management; and diminishing returns on heals made the tank feel like it was constantly dying while healers hesitated to cast spells that seemed ineffective due to low potency stacks. The final solution implemented a strict "one heal per healer per minute" rule, which forced raid leaders to coordinate perfectly so only one person healed at any given moment, allowing others to deal damage during their global cooldowns. To compensate for the reduced healing throughput and ensure tanks maintained enough threat without generating excessive aggro from DPS spells, Loatheb introduced spores that dealt damage without creating threat, effectively balancing the encounter's difficulty while maintaining high stakes through mandatory consumable usage like flasks and potions.
The discussion extends beyond specific mechanics to address broader design philosophies regarding player engagement and resource management in MMORPGs. The designer defends the requirement for extensive gold spending on consumables during raids, arguing that a true RPG should encompass all aspects of gameplay rather than isolating players into single modes like arenas or dungeons alone. While acknowledging that this approach is unpopular due to the financial burden it places on players, the creator believes that pushing characters to near-maximum potential requires engaging with every system available, including PvP and PvE content, to fully realize a character's capabilities. This perspective suggests that limiting oneself to only one aspect of the game prevents reaching true mastery, even if being 90% effective in any single area is sufficient for casual play; however, striving for absolute perfection across all disciplines defines what it means to be part of an elite raiding community where knowledge gaps and preparation determine success.
Ultimately, both encounters serve as case studies in how Blizzard balanced mechanical innovation with practical testing realities before the era of robust data tools like World of Logs existed. The team relied on internal testers pushing classes against dummies to establish baseline damage numbers, then intentionally padded boss health by 30% to account for clever strategies that serious raiders would inevitably discover during live play. This conservative approach ensured that when Patchwork and Loatheb shipped, they were genuinely difficult encounters that required precise coordination, optimal gear usage, and deep understanding of game systems rather than just raw power levels. The video concludes with a humorous note about the accidental anagram in "Loatheb" meaning "heal bot," but underscores the serious intent behind these designs: to create memorable challenges where every player role was essential and no aspect of the game world could be ignored if one wished to conquer its hardest content.
Read the full video transcript
I was the designer for the World of
Warcraft raid boss Patchwork in
Naxxramas.
>> You guys have watched one of this guy's
shorts cuz he talks about the design of
like vanilla WoW fights. This one's how
he designed Patchwork. So, those of you
guys who don't know how Patchwork works,
Patchwork is very much seen as a stand
there and do as much damage as you can
fight in classic WoW. Patchwork is it's
part of Naxxramas, the first boss in the
construct wing. It's very much seen as
very tank and spank cuz most of the work
that has to be done is done by the
tanks. Can tanks and the healers,
really. Because everybody just sits in
this river that makes them go low
health, which changes how the mechanics
work for the hateful strike. So, a
hateful strike is whenever a a boss is
fighting one guy. He's he's fighting the
tank, he's hitting the tank, but a
hateful is like somebody who's like
second on threat or second and whatever,
you go and hit that guy. It's just like
a bonus attack that hits another person
that's not the main tank. That's what a
hateful is. You see a lot of hateful
strikes in Burning Crusade, actually.
But, Patchwork has a hateful here. It's
often times seen as like the tank and
spank maximum amount of DPS that a class
can do is always done on the Patchwork
fight. They go full world buffs, they do
whatever, and they say like Patchwork
DPS is like the phrase that was used. I
don't know if people even still use that
phrase as much anymore, but that's like
how that fight works. So, this is the
guy who he he has a phone and also he
designed the Patchwork fight. So, let's
see.
>> I was the designer for the World of
Warcraft raid boss Patchwork in
Naxxramas. Let me tell you how he was
designed. Jeff Kaplan was reminiscing on
an Everquest boss called the Avatar of
War. As Jeff remembered it, this boss
wasn't too fancy. It just hit you really
hard. Tanks tanking, healers healing,
DPS doing their thing. All of the
difficulty and excitement of the Avatar
of War was based on how tightly it was
tuned. And he had a theory that a boss
like that in World of Warcraft could be
really exciting, too. [music] So, I got
to work. The first problem we had was
that tanks back then had a little over
4,000 health. But, even if Patchwork was
hitting for 4,000 on every hit, healers
had no problem keeping up. Raid groups
regularly had two to four tanks, so I
had Patchwork rotate his hits between a
tank and multiple off tanks. That's
where we ran into the second problem.
Simply spamming
>> So he's talking about the Hateful Strike
mechanic.
>> heal spells onto dedicated targets for
the duration of the fight gets tedious.
And so a custom attack prioritization
system was devised to allow Patchwork's
auto attacks to land on the primary
>> primary tank with additional big hits on
the off tanks.
>> Okay, so he's talking about the Hateful
Strike. So like the the thing is with
the Hatefuls here, Patchwork works a
little bit differently than like the the
entire rest of the game. Because he does
his Hatefuls not only like based on
threat, but also the amount of health
the target has. So that's why the DPS
stand in the river that like poisons
them and makes their health really low.
So the DPS will always just go run into
the river, stand in the river. That way
like the Hateful Strike prioritization,
it's not really just about the threat,
it's about the amount of health they
also have.
>> I named the ability Hateful Strike as a
temporary name because the algorithm
chooses amongst the three enemies with
the most
>> guy is fine with all this.
>> name Hateful Strike to ship, but here we
are.
Hateful Strike targets the off tank with
the most health to give healers some
extra reaction time if heals were
landing at different times due to
coordination issues or lag. The third
problem we had is that the right answer
just became bring 30 healers and just
DPS the boss down slowly. That's where
the enraged timer came
>> Enraged timer, yes, so you can't do
that.
>> Enraged timers are pretty standard
practice in modern World of Warcraft,
but Patchwork was the first time we
aggressively used an enraged timer as an
explicit DPS check.
>> I think there's other enraged timers,
but you never hit them. Like they're not
even really close. And Patchwork,
nowadays when you're playing classic
WoW, people know so much and they they
just they've gotten so good at the game
that it's not as much of an issue now.
But if you saw, or if you remember
playing like The Burning Crusade
pre-patch, you lose a lot of stuff. So,
running Naxxramas in The Burning Crusade
pre-patch is a little bit hard, even
harder in some ways. Even though you
have like a DPS increase, you lose a lot
of the consumables and the extra stuff
that you need to do Naxx. Part of the
problem with Naxx in general, and really
one of the difficulties of classic WoW,
like especially at the highest level of
classic WoW, is it costs a lot of gold.
You need consumables. You need to
consume a bunch of stuff. You need to
get your world buffs. Playing the game,
it's not limited to what your character
can do, or like being competitive at the
game, right? Competitive not like on a
Elo level, but more so on the level of
like playing the game at a high level.
It's more like a knowledge gap. But, a
lot of people have that knowledge these
days, so.
>> And this led to the final problem that
we had. Back in those days, there just
wasn't robust data on how much DPS a
player could realistically put out. This
was before World of Logs. So, we had top
players in the company test every single
class against the target dummies to try
and put out as much damage as possible.
And then, because we knew that serious
raiders always find clever ways to push
the game to its limits, we padded
Patchwerk's health by an extra 30%
>> [laughter]
>> just for good measure. Now that we were
fully straining tanks, healers, and DPS,
Patchwerk was ready to ship.
>> That's super funny. That's wonderful.
Take the top dev's damage and add 30% to
it. The game design story behind WoW's
Loatheb. Okay.
>> I designed Loatheb, a Naxxramas raid
boss in World of Warcraft.
>> This guy's good at explaining. Yeah.
Devs are smart, man. In fact, okay, so I
have a take.
This is my take, chat. I have a take.
Devs are smart. They're smart people.
But, sometimes, if you're too smart, you
can't tune your brain down to the
average level, and it makes it really
hard to see the perspective of how
somebody else who doesn't have the same
amount of intelligence or knowledge on a
subject that you have, uh how they'll
see it. A lot of devs have like
engineering brain. And you know how like
I mean different people learn
differently, different people think
differently. There's like engineering
brain. I feel like it's like you're a
math science guy, and you were just not
you're not a word wizard, right? There's
a lot of guys like that who are not
particularly word wizards, but they can
go and they can map things out that you
can't even like begin to imagine. And
like, "Hey, like I understand this this
this this this whatever." You're just
not good at explaining things. They're
not good with their words. Then you have
other people who are not that smart, who
are word wizards, and they're really
charismatic, and they have a way of
being able to speak and be able to like
captivate an audience of people and make
people like even to teach people things,
but they I mean then they themselves
might not be that smart, but they can
teach really well. Sometimes people are
really smart, but they can't teach well.
It all started with a simple question.
Could we make a fight where the healers
would be called upon to DPS? A naive
design would be to just to say disable
healing completely during the fight.
Pretty quickly, we realized this
wouldn't result in healers DPSing. It
would result in them being benched. So,
the first real attempt was a stacking
debuff on the tank. Consecutive heals
would reduce healing. The hope was that
healers would space their heal Dude, I
got to say so so
every time on the low with that fight,
every time you heal, you can't heal
again for another minute, okay? And
that's what he's he's he's about to
explain this, right? But
>> it sounds so simple on paper, but I
swear it is like pulling teeth sometimes
trying to get all your healers to to
press a one heal. You get one heal cast
per minute.
Press the button one time. Hey, I just
healed. So-and-so is next, right? I
don't know why it's the hardest thing in
the world. Like sometimes somebody would
heal, and then I just forgot to say
anything. I'm like, "Bro, now there's a
bunch of different ways you could do
it." There's a bunch of different ways
you can do this fight, but like that's
that's how I like to do it. Just like,
"Hey,
you heal, and then you call out who's
next." Who And you have an order
predetermined. Like, you don't have to
think. You just have to know who's who's
next. So, then that person hears their
name and they're like, "Oh, hey." But,
you just you get in this like a rhythm.
It's crazy.
>> heals out from one another and then
spend their time between heals doing
DPS. What actually happened was if the
tank was getting low, everybody started
panicking and healed harder. People
would try to heal through the deep. We
got more healing, not less. The next
idea was to have a stacking debuff on
the caster after every
>> Oh, so this is the different things that
they did. I was like, "Wait, there's no
debuff." So, this is how they got to the
final the final result.
Oh, okay.
>> the heal. Imagine a debuff that could
cause diminishing returns on the
effectiveness of your heal spells. Your
first heal lands at 100% effectiveness
and then 80%, then 60%, and so on. This
turned out to be super un-fun. Imagine
your healer sitting with say three
stacks of the debuff
>> And you burn your mana.
>> so you're at 40% healing effectiveness.
The tank needs a heal. What do you do?
Doing nothing feels like a mistake.
Casting a heal to save the tank feels
like digging a deeper hole for yourself.
This is how we got to the hard cap that
finally shipped. One heal per healer per
minute. Raid leaders would want to bring
healers for that coveted heal
>> Dude, this is so interesting cuz he's
right.
>> But, once you've cast your heal, you
might as well DPS while you're on the
healing time out, right?
With the core mechanic in place, the
next concern was that with less healing
going around, tanks might not get all
the rage that they needed to generate
enough threat. That's where the spores
came from.
>> So, then they then they do more crits.
>> players a buff that lets them do damage
without generating any threat. There's
no doubt Loatheb requires farming a ton
of consumables.
>> Yeah, there's a whole consumable cycle
that you have to give for this fight.
want a
>> starts to over-gear the content, you
start using fewer consumables. But we
knew Loatheb, because of his mechanics,
would likely continue to require
consumables even after on-farm status.
When we're testing content internally,
developers have cheat codes that let us
spawn in potions, flasks, or whatever
instantly. But players don't have such
luxury. I don't love it, but after some
internal debate, we decided that as the
final boss of Naxxramas wing, the
requirement was okay. So, funny thing.
>> I'll be honest. I know this is an
unpopular sort of opinion. I like the
use of consumables in raids. And And
Blizzard really started to move away
from this literally in the in the patch
after this raid came out because they
added like Guardian Elixir and they
added the Battle Elixir system. So, you
can't stack potions anymore. They
changed it to where the protection
potions don't last for like 2 minutes
and you can like double stack them. You
know, like you would pre-pop a
protection potion and They're sorry, not
2 minutes.
Um protection potions would like six I
think they would last 60 minutes,
wouldn't they? Either way, it was always
getting burned cuz you'd pre-pop it and
then you'd have some and then you'd pop
another one. So, I think I'm pretty sure
it was 60. Anyway, I actually think it's
okay. I know this is not a very popular
opinion, but the reason why it's
unpopular, I understand, is because
people don't like having to go spend a
bunch of gold to raid and farm up a
bunch of gold and do all that to raid.
But that's kind of like whenever you
talk about a game that encompasses like
all aspects of it. Now, I I think that's
important when you're talking about
making an RPG or an MMORPG. I think
something that's very important is you
have the whole game as part of the game.
And you're not doing this like sort of
like theme park sort of situation where
you you only do one thing. Like you only
do arenas, you only raid, you only do
Mythic Plus, you only you only level,
you only do dungeons, you know? That
type of stuff I don't think it's like I
understand how there's certain [music]
people that only like a certain part of
the game or certain aspect of the game.
Myself being somewhat one of those
players, right? Whenever we talk about
Burning Crusade, like I love arenas. I
can go and I can do Burning Crusade
arenas all day. If I have if I have good
teammates, if I have if I have the
people that I want to play with, if I
have nothing else going on in the world,
I could just sit there and just spam
arenas all day every day, right? As long
as the queues are there, which they
usually are whenever I'm playing. But,
still, I'm kind of one of those type of
players, but I understand for like good
game design, and that's really what the
core of vanilla WoW is. Like, I think
it's okay to have your character and
like your player power be like 90%.
[music] Like, your character can be like
90% as as good as he could possibly be
doing one thing. But, in order to like
take your character and be like the most
maximum amount of power that you could
have. I I say 90% is like an arbitrary
number, maybe 95, right? It doesn't
matter. But, just a little bit less than
the best. To be the best of the best of
the best, I think you have to be able to
PvP and PvE to get all the rewards that
you can and to to push everything to the
highest level. That's that's how you get
the most out of your character. I think
that's good design. Talking about
playing the entire game. And I think
that's that's part of being an RPG. As
fan, your hair looks glorious today. I'm
glad you guys are paying attention.
Thank you. That's the last part of this
video.
>> Requirement was okay. So, funny thing,
after Loatheb was finished, I learned
that Loatheb is an anagram for heal bot.
Believe it or not, that was not
intentional. I know, totally
>> What? There is no way. There is no way
that wasn't on purpose. I thought that
was a on purpose thing that they named
him because they designed. I'll watch
more of this guy's stuff in the future
because I do have a phone.