Showing posts with label raiding. Show all posts
Showing posts with label raiding. Show all posts

Friday, January 20, 2012

Should Raid Nerfs Be Disappointing?

For those of us who enjoy raiding as a significant part of our World of Warcraft experience, "nerfs" (the weakening of encounters) to raids that are still current content tend to be a hot topic. Most of the (visible) response tends to be negative, with an even more vocal minority of that group moving toward the wailing and rending of garments.

Even the more moderate, though, generally are a bit disappointed when the raid encounters they're working on are made easier. Should we be disappointed, though?


"It's Too Easy Now"


What makes an encounter too easy? I can guarantee that if you weren't finding yourself a few percent short of getting the last tendon down on heroic Spine of Deathwing once January 31st rolls around, you're not suddenly going to find yourself blasting through the remaining content on February 1st. Challenge still abounds.

The fact of the matter is that the "correct" difficulty level of an encounter is entirely arbitrary. Had the raid encounters been released back in December with 5% less health and 5% less damage done, would that have been the "right" difficulty level? While a few more people may have been agitating from the start that the raids were too easy, the vast majority of those who are upset now would never have been upset at all, because they'd never have had the higher figures set in their minds as real and proper.

Increasing the difficulty of a game with a computer opponent where the rules are set by the game itself is trivially easy. You can always increase the power or mechanics of the computer opponent  until it is impossible to complete. So clearly the answer to what should be the correct level of difficulty is not "As high as possible." As high as possible is always unwinnable.

So where do difficulty levels come from, in gaming in general? The simplest answer goes to accessibility. Games manufacturers are doing what they do in order to make money. That means selling a game to the widest possible audience. There are two competing dynamics there.

At the most basic level, the largest possible audience is simply anyone that can fire the game up...it includes basically every computer or console user.

However, a game that only involves starting up obviously wouldn't be compelling to anyone. Therefore, it needs to have enough challenge that those who play it find it fun. If it is too challenging, such that it is impossible for any human to complete, then, again, almost no one will find it compelling.

So game designers have to create difficulty levels that are hard enough to be compelling, to make players feel like they're acquiring a skill and being forced to improve it, while being easy enough that a sufficient number of players can be successful.

The operative term and variable, there is "sufficient." For every designer, that's going to be different. No designer can aim for 0% of the game-playing population and 100% is probably untenable as well. Where you draw the line, in terms of percentage of population being able to complete the game, is arbitrary from a game design standpoint. Ultimately, it's probably going to be based on some complicated linear algebraic model determining what difficulty level sells the most games.

Raids in World of Warcraft are no different. Blizzard has a figure in mind for how many raid teams should be able to complete the raid, on normal and on heroic (different figures for each, obviously). The release difficulty is their best guess as to what will hit those figures.

But their best guess may be wrong.

When that happens, when their internally-tracked figures are showing that not enough raid teams are meeting the challenge, it tells them that the raid is actually too hard. Not that it was the correct difficulty and now they need to provide some charity to all of these fail raiding guilds.

"Too hard?" "Correct difficulty?" Based on what, again? Based on the same calculus of game difficulty that every game company works from: that enough people can eventually meet the challenge without it being so easy that it's not even challenging to do.

What does that mean? It means that the nerfed raid difficulty levels arriving on January 31st are the "correct" difficulty...by definition. That definition being the only way game difficulties are ever chosen from the arbitrary spectrum that ranges from "success just by loading the game" to "unwinnable by any human."

By choosing to play World of Warcraft, by choosing to raid in World of Warcraft, by choosing to play any game, you are entering into an implicit agreement that the correct difficulty level is chosen by the game company producing it. It can't be any other way. There is no "platonic game difficulty level" that a game company could use.

So if you've defined the correct level as whatever Blizzard defines it to be, and Blizzard (like all other game designers) has defined it to be "whatever allows X% of players to win the game" then Blizzard nerfing (or buffing) raid encounters is not reducing it from its "correct level." It's Blizzard tuning it to its correct level, because they got it wrong at release.


This Isn't New, It's The History Of Video Games


Video games largely find their genesis in the cabinet-style arcade games of the 1970s and 1980s. Pong is probably the best-known arcade pioneer, an incredibly simple video game that was meant to simulate table tennis. Through the 1970s and 1980s, and into the 1990s, arcade games exploded in popularity (while consoles and video game computers that were birthed from that success had a more up-and-down development curve), with such iconic hits as Missile Command, Pac-Man and Space Invaders. Double Dragon. Street Fighter II. (I forgot how much I missed arcade games. Or maybe I miss youth. Wow, this got depressing fast.)

What is probably less well-known about arcade games is that many of them had a feedback loop to dynamically regulate difficulty levels.

The game would spend a certain amount of time evaluating how well the player was doing, how quickly the player was progressing and then amp up or amp down the difficulty level to better match the player. After all, if a game was under-tuned or over-tuned, players wouldn't play it and you couldn't "hotfix" ten thousand or a hundred thousand cabinet games scattered around the country by releasing a patch over the ARPANET.

So what was the correct difficulty level? The correct difficulty level was just slightly above the player's skill level, which forced him or her to continually improve or face dying over and over at a certain point. That's perfect from both sides...the player has something to continually strive for without facing a brick wall that he or she can't get past, and the game producer has a steady stream of quarters it's earning as the player keeps dying in the process of improving. Everyone's got what they wanted.

Blizzard is doing essentially the same thing with these nerfs, just writ large. The period of polling or evaluating player skill is two or three months (instead of, say, 30 seconds). Instead of evaluating a single player, it's evaluating a playerbase. The game is then adjusted (sometimes with hotfixes, sometimes with a patch) and another stable evaluation period occurs.

In retrospect, are you disappointed that perhaps some of your Pac-Man scores were illegitimized by nerfs? (Of course, I'm dating myself a bit by implying that I have scores on Pac-Man cabinet games...many of you may not be old enough for that. That said, I'm sure you understand my point here. Also, this parenthetical comment has gotten really long.)

Dynamic retuning of a game that is in progress (and current content raids can be considered "in progress" for as long as you're doing them this tier) is not at all new. In fact, it's quite standard practice. Going hand-in-hand with the fact that are no platonic difficulty levels for games is the belief that everyone is best off by making sure that the designer's vision of where accessibility and challenge intersect is continually being enforced.

So instead of being concerned or annoyed that Blizzard has decided you need a booster seat to get to the creamy desserts in the middle of the table, it's probably more appropriate to view it as Blizzard deciding they made the table far too large and that only the people with freakishly long arms are getting enough dessert and that they didn't intend the desserts to only be for freaks.

And remember that the "desserts are meant for more than just the long-armed freaks" principle is solidly entrenched in video game history...gamers are happier and, therefore, game companies are wealthier when games are continually redesigned to better match the original vision.

Sunday, November 13, 2011

Can You Go Double Disc?

A question that emerges with discipline priests, moreso than any other healing class-spec I would say, is whether you can viably accommodate two of them in a ten man raid healing team. The reason this question is especially prominent for the discipline flavor of priests is because they are seen as reliant on a very particular spell: Power Word: Shield.

There is no question that Power Word: Shield is an iconic spell of the specialization and, most would agree, the spell that the spec revolves around.

What makes this tricky when compared to the central spells of other healers is that Power Word: Shield doesn't play nicely with another priest's Power Word: Shield because you cannot put more than one Power Word: Shield on a single target. Two Wild Growths work fine together, ditto two Renews, two Divine Lights, two Chain Heals, etc. Other healing class-specs largely focus on healing spells and healing spells almost always stack (as they must, since multiple healers often heal the same target). Power Word: Shield is something of an unusual mechanic in that it's a healing spell that doesn't heal.

This means that, at least on a superficial level, more than one discipline priest in a single raid group will be competing for shield targets. If one discipline priest shields a target, another one cannot shield that target. Each discipline priest, therefore, cannot operate with a free hand.


Or So It Would Seem


This would have been the beginning and end of the analysis in the latter stages of Wrath. Discipline priests were bubble-bots first and foremost. Played properly, their first duty was to keep everyone shielded whenever possible (whenever that pesky Weakened Soul wasn't on a target) and only secondarily (in ten man raids) heal raid members.

In such an environment, each discipline priest in a ten man raiding environment would be handicapping any other, as both couldn't be casting Power Word: Shield on every target (this was not so much of an issue in twenty five man raiding groups, since there were so many targets, two discipline priests could viably split up targets to shield). That meant that one or both discipline priests would spend quite a lot more time casting direct healing spells. That wasn't disaster, but it wasn't what discipline priests did best, so it was at least a mild nerf to one or both priests.

Cataclysm, however, changed the picture considerably. It did that in a few ways, but the net effect can be boiled down to this: Blizzard made discipline priests much less reliant on Power Word: Shield to be solid contributors to a healing team.

Let us count the ways in which Cataclysm gave discipline priests alternative casting patterns (spoiler alert: the number of ways is two.)


The Subjugation Of Tank Healers By Holy Paladins Has Been Broken 


Time was, the tank healing community resembled an Old West saloon. You had your standard allotment of cow pokes, card sharps and...stable hands (I guess?) who got the job done, in a manner that was not flashy or spectacular. Quite workmanlike. Then a shadow fell across the room as a man in black (or white) swaggered in, a pistol on each hip. He looked around with a sneer and everyone who looked up to see who had walked through the swinging doors then quickly looked away, unwilling to meet his gaze. This fellow's superiority was palpable, it was unquestioned.

That gun-slinger was the holy paladin. The rest were discipline priests or restoration shamans. You could use another class to do your tank healing, but you only did so if you simply had no holy paladin available. It was sub-optimal...very sub-optimal.

That's changed. Holy paladins are still capable of healing tanks very well (and not quite so good on the raid), but all the other healing class-specs have become viable tank healers and discipline priests have really seen the biggest jump in this respect. It's no longer sub-optimal to put a discipline priest in charge of keeping your tank(s) alive. The interplay between talents like Renewed Hope, Divine Aegis and Inspiration, an interplay that was kicked up a notch by the patch 4.2 change that increased the output of critical heals, in addition to the interplay between direct heals like Greater Heal and Flash heal and the talent Strength of Soul made discipline priests extremely powerful in healing through major and continuous damage on specific targets.


Prayer Of Healing: Now With More Divine Aegis


Prayer of Healing used to be a spell that didn't have any special synergy with discipline talents. Discipline priests, when they weren't shielding, focused more on single-target spot healing. Prayer of Healing was more of a tool utilized by holy priests in their quest to AoE heal all the things.

Cataclysm has made Prayer of Healing a core discipline tool through a modification of the Divine Aegis talent. Divine Aegis, which has always (since it was introduced in Wrath) proc'd an absorption shield on the target of a critical heal, was now able to place automatic shields on every target healed by Prayer of Healing, critical heal or not. This was modified further to also proc extra shields on Prayer of Healing targets when the spell critically healed. Suddenly, Prayer of Healing had strong synergy with a core discipline talent...Prayer of Healing was now a vehicle to get non-trivial absorption shields out to lots of people, in a way that was spammable (as opposed to Power Word: Shield, which cannot be spammed on the same target due to Weakened Soul).

Combined with the actual healing that Prayer of Healing did, these absorption shields made Prayer of Healing a powerful raid healing tool for discipline priests, with a component of preventative medicine that has always been the discipline priest's stock-in-trade. Discipline priests could both use Prayer of Healing to heal the raid back up, or use it ahead of incoming raid damage to reduce the hit to health bars. It was most powerful when it could do both at the same time, with predictable waves of incoming raid damage.


tl;dr Version


Discipline priests can therefore settle into several roles. A Power Word: Shield-heavy role, a single target tank healing role or a Divine Aegis-powered raid healing role. By prioritizing different stats (mastery for heavy shielding, crit and haste for tank healing or Prayer of Healing raid healing) and minor changes to talents and glyphs, a discipline priest can play in a very different way from another discipline priest and still be equally powerful. No longer must multiple discipline priests step on one another's toes.

Indeed, discipline priest partnering with discipline priest is fine everywhere, not just in New York and Massachusetts.

Thursday, October 27, 2011

No Loot Is Healer Loot

Well, except for that spirit wand, right? Surely that...no self-respecting mage or warlock would want it, with 60%* of a secondary stat completely useless. Only a priest would want it...only a heali... 

*Reforged 

Well, there's the rub. A shadow priest would like it just fine, since spirit can be converted to hit for any ranged DPS spec that's part of a hybrid class.

So why does that matter? Isn't the spirit wand still healing priest loot, even if a shadow priest can use it, just as any spirit gear is healer loot even if other DPS specs can use it? And, for that matter, as healers become less beholden to their blue bars, isn't any intellect gear they can wear that contains no hit rating also perfectly viable healer loot?

Hello. I'm a healer. And in all of those cases, my answer is a categorical no. That's why I took a bold step.

In our raid group, we have a very, very simple loot system. It's round-robin. We maintain a loot list and when you get a piece for your main spec, you drop to the bottom of the list. The list adjudicates who gets a piece when multiple people want it. Highest person on the list receives the loot. It's meant to be fair, impartial and distribute loot relatively evenly across everyone.

And I want no part of it.

Thus we come to my bold step: I asked to be removed from the hallowed loot list.

The consequence of this is that it's never "my turn" for loot. Anyone else in the raid has a higher claim than me, by this decision of mine. I'll still receive upgrades, but only when no one else needs the piece.

Am I just that noble? Well, yes, I am. However, it's for a reason that I feel is perfectly rational. The subject of which shall be meat of this post. 


Defense Sells The Tickets, But Offense Wins The Game 


For those of you not steeped in the ceaseless avalanche of cliches that is sports commentary, there's a popular saying that "offense sells the tickets, but defense wins the game," suggesting that people enjoy watching scoring but ultimately preventing scoring by the other team (the "less glamorous" role) is what matters most.

I'm here to tell you, that it's reversed in World of Warcraft. If I were to craft a pithy maxim that makes sense within the context of the game, it would be "Healers* win normal modes, but DPS wins heroics."

*When I say "healers" here, I actually mean "tanks and healers." It's just not as pithy and catchy when you throw in "and tanks." 

The reason for this can be summed up in two words: enrage timers. Heroics, pre-nerf at least, tend to have hellaciously tight enrage timers. This is why many raid strategies for heroic modes advise raids to cut healers and tanks wherever possible, to pack in more DPS.

When doing normal modes, you're learning the basics of the fight for the first time. Tanks and healers are the most important for this step, because they extend the raid's lifespan. The longer you live, the more of the fight you see and the more practice you get. Go healers!* 

*And tanks 

Once you mosey on into the heroic modes, though, the focus changes. You mostly know the fights. The heroic modes have somewhat different mechanics, but most of the original mechanics are still there and the concept of the fight is usually very similar. You might want a few "Just survive as long as possible so we see the new mechanics" wipes, but you don't gear around the first few looks at the fight. The main thing is the DPS. It must be high...very high. Obviously, everyone is going to have to play well, but the fights really shift away from healers as a main focus. DPS must beat the enrage timer and everyone must avoid as much avoidable damage as possible. That's the design of heroic modes, it's how they're balanced.

Therefore, "getting over the hump" means getting DPS geared enough to beat the enrage timer. After that, gearing up healers certainly helps...the stronger the healers are, the more margin for error the raid team has. But no healing team is going to make up for the "didn't beat the enrage timer" error. 


Healers Cannot Reach For The Stars 


Remember when our mothers and fathers told us that we could rise as high as we wanted if we worked hard, that there was no limit? They didn't mean healers, they only meant DPS.

DPS has an infinite horizon. You can always do more DPS. More gear, more skill, more buffs will all equal more DPS. Further, you can do more DPS and that unholy death knight you hate can also do more DPS...at the same time! It's not zero sum...one person doing more DPS doesn't lower the ability for someone else to do DPS.

The healing game is very different, for three key reasons.

One is that there isn't infinite capacity to heal. A healing team's healing output is strictly capped to the amount of damage done to the raid team by the boss (and his or her minions). You cannot heal damage that doesn't exist. If a raid boss does 21 million damage over the course of an encounter, the maximum healing the team can do is 21 million.

Number two is that as your raid team gets better at the fight, the damage taken is going to go down. Some damage is unavoidable but lots of it is not, a design choice aimed at making dance skill matter. The better you do the dance, the less damage you take. So as time goes by, that maximum amount of healing available to be done shrinks, leading to lower output from healers.

Finally, healing is a zero sum game. Since healing to be done is, as established, a capped resource, every healer in the raid is competing for a piece of it ("competing" in a literal sense, not necessarily from an attitude point of view). One healer pushing their healing up massively simply diminishes the possible output of any other healers in the raid. All the healers cannot simultaneously heal significantly more unless they were woefully over-matched from the start.

So when you have one group of players (DPS) who can turn gear into bigger and bigger output and another group (healers) who cannot, it makes a lot of sense to bias the gear distribution in favor of the group who can convert it into no-questions-asked larger output. 


Personal Reasons Are Personal 


While the idea that DPS can use gear upgrades more powerfully than healers is the large majority of why I made the decision to remove myself from the loot list, there was another reason that was simply a personal choice (which is why I'd never even suggest to my fellow healers that they do the same as me).

I want to de-emphasize loot for myself. There have been times when I've been frustrated over not getting the piece I need to drop, or losing it to someone else. I know, though, that loot is not why I play. At least, that's what I believe. WoW Insider had an article a month or two ago (I'm too lazy to find it and link it) about how everyone, at base, is motivated to raid by loot. The writer said (paraphrased), "If you don't believe that you are [motivated by loot], ask yourself how long you would raid if you never got a single piece of loot."

Not long, but I think that's a meaningless question. Never getting loot is the same as never raiding, because you'd soon no longer be geared enough to raid. Loot is necessary simply to be able to raid. The question is how much you're motivated by the Gollum-like desire for shinies.

But we wants it! We'll reforge the expertise to spirit!

So a better question is, "How long would you raid if you were always the lowest priority for loot?" That's what removing myself from the loot list accomplishes: placing me at the lowest priority.

I think I'll keep raiding for a long time.

Thursday, October 20, 2011

The Terrible Secret Of Space

In case you don't get the (old) meme reference of my post title:







Okay, now that that's out of the way, let's talk about "healing space." This is not an alternate zone that healers live in, perhaps like the Emerald Dream area in the Valthiria Dreamwalker encounter. This maps out where each healer excels, when able to do what their class abilities optimally allow for, to create maximum synergy between the healers in your team.

This is much more crucial in twenty five man encounters, when you have more healers and significantly more overlap. It does happen more often in ten man encounters that healers get isolated more on their own healing islands, in which case you cannot "specialize" as much. However, as you push into heroic modes, even ten man raids are well-advised to try to organize the encounters such that all the healers you're using can cover all the same targets (everyone). This is not always possible but, when it is, that's where heal space analysis is valuable.

The long and the short of it is that if two or three healers can cover the same targets, you maximize their effectiveness by A. making sure the two or more healers have complimentary powers and B. having each healer bias their spell usage toward specialization.

So what heal space does each class inhabit? Let's take a look.

Note: The next four sections are a quick look at what constitutes the core of each healing class (and spec, in the case of priests). If you would find a run-down of these class-specs dull, skip past the sections with class headings. None of those sections contain theory, just my views on what (essentially) makes each class-spec unique. That "healing world view" is important to the theory that comes later, of course, but I don't believe my healing world view is controversial.


Druid


For the last (large number here) tiers, druids have been the reigning overall healing throughput champions. With their "creeping heals" (my term for healing that's always creeping upwards, everywhere, all the time), they're almost like the inverse of a damage aura...they provide a healing aura (as it feels from the outside, this is in no way to suggest that it's passive on their end) as everyone's life bars are always moving upwards thanks to them. They can Rejuvenation blanket when everyone's taking AoE damage, Wild Growth on cooldown, Swiftmend to create a healing circle under a group of people and keep potent HoTs (the aforemention Rejuvenation and Lifebloom) rolling on the tank(s).

And then, of course, there's always the raid healing bomb of Tranquility lurking.

The reason druids have been such potent raid healers is because they're not provided any absorption or mitigation abilities (leaving aside the personal cooldown, Barkskin, which is of only niche value to a restoration druid). Their contribution is entirely wrapped up in moving life bars, so they move them a lot.

While they can use direct heals to keep someone, like a tank, alive through continuous damage, it's not where they excel and it's not the optimal use of their mana. "Optimal" is the crucial word for this analysis, since we're trying to maximize a healing team.


Paladin


For the last four or so tiers, at least, paladins have been somewhere between very strong and broken-strong (ICC days) as tank healers. They've been given some new tools in Cataclysm (notably, Holy Radiance and Light of Dawn), but neither has changed the fact that the bulk of their work is done with strong single-target throughput. Their healing space will probably have to be re-evaluated once patch 4.3 arrives, due to the major changes to how Holy Radiance will work.

Holy Radiance (thus far) has been constrained by a cooldown, making it unspammable, and Light of Dawn is a holy power release, so it's also unspammable, since they need to build up holy power in between usages.

That leaves paladins the most beholden to the "Three True Heals" model that Blizzard has tried to build into every healing class (with varying levels of reliance across classes). Since their "quick, mid-level heal" Flash of Light is not generally considered a good use of mana, they end up heavily reliant on four spells with a heavy emphasis on the first two (being the ones without a cooldown or holy power requirement): Holy Light, Divine Light, Holy Shock and Word of Glory.

So direct heals are what paladins will be dealing in, largely.


Shaman


Shamans have an interesting concept. The majority of their healing is direct, though they also use an area HoT (Healing Rain) and a more traditional HoT that procs from one of their main direct heals (Riptide).

What makes shamans interesting is their mastery, Deep Healing. The upshot of their mastery is that the lower health their healing targets, the more powerful their healing spells are.

So shamans are a mixture between direct healing and healing over time, with potency inversely related to the health of their target.


Priest


Priests come in two flavors, of course. There is the Discipline flavor and the non-Discipline flavor (I kid, I know that one of the healing trees is named Holy, even if Blizzard doesn't).

Discipline priests have always had a unique mechanic (which holy paladins have recently infringed upon with their mastery, but not very successfully except in niche cases) known as absorption. These are shields that absorb some of the incoming damage before it can affect the player. Shields are the centerpiece of the discipline spec. And while discipline priests (like all healers) have an assortment of direct heals, the other thing they have which is more or less unique to them is mitigation. This is similar to absorption, in that it prevents damage rather than healing it, but rather than absorbing it, it reduces the degree of the damage by a percentage basis. So instead of absorbing 45,000 damage, it will reduce the incoming damage by 10%. One of their signature mitigation spells is a tank cooldown, Pain Suppression.

Holy priests on the other hand do very little absorbing and mitigation. They are more similar to druids in that they use healing over time and direct heals to do lots of healing over the encounter time. While druids bias more toward HoTs, holy priests bias more toward direct heals. Unlike druids, holy priests do have a potent tank cooldown, Guardian Spirit. As you might notice, Guardian Spirit is kind of the reverse doppelgänger of Pain Suppression. While Pain Suppression mitigates damage by 40% on a target, Guardian Spirit allows for 40% more healing on the target. Guardian Spirit has the added benefit of preventing a death, which does make it a bit more powerful but also compensates for prevented damage being less risky than healing damage after the fact, a factor that makes damage mitigation more powerful than a healing boost.


Healing, Economics...Same Thing


If all of that was a fairly old hat recap of the healing class-specs, I apologize. In terms of structure, I felt it was important that we establish what each healer is doing at his/her core before we start parceling out territory in the healing universe.

The central concept of healing space is this: While every healer can do a variety of things and fill any role, especially direct healing of all the things, the highest efficiency is achieved by each healer focusing on the things they do best and avoiding the things they don't do as well as another, even if they can do it well. If you've studied economics, this should be a pretty familiar idea, because it's mirrored perfectly by the idea of Comparative Advantage. By specializing in what you do best (rather than doing everything you do decently), you increase the efficiency of your team. To make the parallel to the economic theory, if you analogize your healing team to a world economy, your healers are trading products (throughput) for currency (mana efficiency) with each other.

The economic theory of comparative advantage is wonderfully counter-intuitive to most people when they first encounter it. It generally isn't an immediately obvious idea that, even if you're good at a number of things, if you exist in a world with potential partners who do anything better or worse than you you're better off specializing rather than doing everything you're good at.

Blizzard made sure every healing class can fulfill any role competently with the advent of Cataclysm, because they didn't want raids to feel locked into specific class make-ups rather than just bringing the people who were either best or else they most enjoyed playing with. So the changes they made to achieve this made every class a jack-of-all-trades to a certain extent. However, they didn't give every class and spec every ability or equalize their power in every role. They just ensured that every class and spec reached at least a minimum baseline in every healing role. This leaves enough difference between the class-specs to leverage for the sake of efficiency (and when I say "efficiency," I mean optimizing throughput for a healing team).

So how do we leverage this? To put it very simply, we identify where each class-spec's best use of mana lies and create a healing scheme whereby each healer is biasing their spell choice heavily in favor of that best use of mana. That is optimizing healing space.

This may sound like what healers should always be doing, but it's only possible in group play in which there is more than one healer. In a five-man environment, for example, where there is only one healer, you cannot specialize. You must cast all the spells necessary to keep everyone alive. This means some amount of direct healing as a druid, for example, even if direct healing is not your forté, because HoTs alone aren't going to keep a tank up through heavy damage. The economic theory of comparative advantage is useless if you are alone on a desert island, and optimizing healing space is worthless when you are a healing island in a five-man group.

No, it gets interesting when you are in a ten man or, especially, a twenty five man raid. The larger the group, the more healers. The more healers, the more specialization each healer can engage in, because a lot of niches can add up to a coherent whole. A single niche is just a niche.


Establishing The Foundation Of Healing Space


I primarily raid in ten man groups, so I'll primarily use that as the example. However, I'll note how this really flourishes in twenty five man groups at the end.

My raid group generally employs a healing team of a restoration druid, a holy paladin and a discipline priest (hey, that's me!). This has actually often been called the "holy trinity" of ten man raid healing teams and for good reason as we'll see from a healing space analysis. How do we leverage these three classes optimally?

The simplest approach for a healing team is what I like to call "see damage, heal damage." If someone is below full health, cast the appropriate spell (factoring in time urgency, amount of healing needed and mana efficiency required). This isn't particularly organized but it can actually work, especially if the healing team is extremely familiar with one another. The primary drawback here is that the disorganization can lead to sub-optimal healing: multiple healers addressing the same damage (leading either to overhealing or else a healer canceling their spell mid-cast, wasting some amount of time) and certain targets not receiving heals quickly enough.

One step up is straight healing assignments. Healer A will heal the main tank. Healer B will heal the off-tank. Healer C will heal all the non-tanks. This is much more structured. Overhealing will be reduced because, at least notionally, healers are not cross-healing the same targets. Every target has their dedicated healer and thus knows exactly what healing that target is receiving because it all comes from himself/herself. The primary drawback here is that overly strict adherence to assignments can leave healing potential on the table (Healer A being idle when the main tank is at full health while Healer C struggles with a burst of raid damage) and deviance from assignments leads to a greater and greater descent into the previous "see damage, heal damage" paradigm, with its own attendant drawbacks.

While the second option (assignments) is generally better regarded, each paradigm actually has its strengths. "See damage, heal damage" ensures that all the healers are capable of remaining active at all times (at least, all times in which there is damage to heal) which prevents useable healer casting time and mana regeneration from being wasted (a healer sitting at full mana is wasting all their itemization and talents that provide mana regeneration), while assignments provide the structure to keep healing from being wasted.

The ideal situation would be to marry the strengths of each paradigm into one, without also importing the attendant weaknesses. A healing space paradigm does just that. Let's look at how this works.


Crafting Healing Space


A restoration druid, as we noted, is best at keeping continuous healing "growing" on lots of targets at once, whether that's through Rejuvenation on multiple targets, Wild Growth or Efflorescence parked below a stack of raiders.

A discipline priest excels at preventing incoming damage.

A holy paladin is most powerful at pumping out strong direct heals on single targets (the value of which is amplified by their "reflection" mechanics, Beacon of Light and Protector of the Innocent...much as a battery of mirrors serve to focus and intensify a laser beam).

So we craft a healing space in which:
  • The druid does keep her HoTs "growing" on as many targets as she can sustain and/or makes sense for the encounter but does not cast many single target heals.
  • The holy paladin does cast her powerful single target spells on targets who are either particularly under siege or else are particularly low but does not concern herself with damage prevention (gears away from mastery) or heals over time (Holy Radiance, which has a mana opportunity cost).
  • The discipline priest does cast her shields and mitigation spells often to slow the damage on targets likely to take damage in the near future, but does not spend much time or mana casting HoTs or direct healing spells.
A crucial point here is that there are no explicit target assignments. You are not assigning the holy paladin to one or both tanks and the discipline priest to one or both tanks. You are not assigning the restoration druid or the discipline priest to raid healing. Instead, if you'd like to think in terms of assignments, you are assigning each healer to a specialization.

A discipline priest is optimally using his mana when he casts a shield likely to be consumed by incoming damage. A restoration druid is optimally using his mana when he casts HoTs (whether single target or multi-target) that are likely not to go as overhealing. A holy paladin is optimally using his mana when he casts a powerful direct healing spell on a target at a low enough health that little of the direct heal goes as overhealing, and the target of the heal reflection also is low enough health that little of the reflected heal goes as overhealing.

The result is that, as long as there is damage to be healed, you have healers who can be active and engaged, yet there is implicit structure that minimizes the overhealing that chaos can cause. The druid is a champion of overall healing, but all that creeping healing is useless if targets die before they can tick back up to a safe level. That's where holy paladin direct heals come in, swiftly (relative to druid HoTs) pushing a dangerously low target back to a safer level where the slow healing over time can finish the job passively. But the paladin's big heal is useless if the target dies before the heal lands (or before the paladin can find time to cast on that particular target). That's where discipline shields come in, providing an instant buffer on targets in critical condition, keeping them afloat until the healing of the paladin and druid can save them.

At a more abstract level, the discipline priest provides a preventative umbrella over everyone, underneath which the druid's garden of HoTs provide a "healing aura" constantly moving everyone upward and the holy paladin combats spikes downward in health to anyone with spikes upward in health through spells.


In Conclusion, More Explanation


In this healing space, each healer has a clear-cut role, which allows them to fluidly move between the same targets, but in their own space. Think of it as a separate dimension...each healer is their own island, in their own dimension. You, as a healer, are responsible for everyone...but only within that dimension. As long as every healer optimizes the throughput of the spells that make up their dimension, the healing team is optimizing their overall throughput.

Except when necessary, you need to resist moving into a fellow healer's dimension. Each time you do so, you detract from the efficiency gains. Your healing team has only so many GCD's (global cooldowns) and mana to work with over a given encounter length. Using your GCD and mana to address a small bit of damage on a target, when a druid's HoTs can address it, may seem harmless enough, but it's a GCD and mana you could have used casting a Power Word: Shield. On a one-off basis, it doesn't matter much...but these little decisions add up over the course of the encounter and undermine the benefits of specializing within the crafted healing space.

For the sake of brevity (this post is barely more than a haiku in length and I like that succinctness), I won't go through a similar healing space crafting for every combination of healing classes. But you can see the format: identify what a healer does that is an optimal throughput use of their time and mana and give them that specialization across the entire raid and task them to use non-optimal spells as little as possible. A shaman, while not included in my example healing space, can easily be crafted a space based on their unique power on low health targets. All that's necessary to create these types of healing spaces is multiple healers. There can even be duplicate class-specs as long as each of the duplicates can, through talents, gearing or playstyle, provide a different specialization (two holy priests can each specialize differently based on different chakra states, two discipline priests can provide absorption and direct heals, etc).

The key is for each healer to decide, for an encounter, what they will be spending their mana on, working to make that efficient (through itemization and talents) and then sticking to it as much as possible. If you've geared and talented for making your direct heals as powerful as possible and then bias your spell choice heavily to direct heals, you can achieve a lot more than spreading your gearing and talents out and trying to do lots of different things...as long as other healers are picking up the other forms of healing.

As I mentioned previously, this can be taken to an even greater extent in twenty five man raids, where instead of two or three healers, you're working with five or six healers. Since every healer is still responsible for everyone, you handle more healers by breaking healing space into even more granular roles. How about a holy paladin who specializes in stacking mastery for absorption and focuses on overhealing targets to build up larger and larger bubbles on targets she expects to take big damage soon? That's happened in some world-ranked raid groups. How about a discipline priest who stacks crit and haste in order to pump out Prayers of Healing to coat the raid in Divine Aegis bubbles (since Power Word: Shields can't have constant uptime due to Weakened Soul)? These are the types of niche roles that ten man raid healers simply can't afford to try because it's too small a niche for the roughly 33-50% of the total healing you're responsible for. The more healers, the more specialized you can afford to be and the more specialized your healers must be to fully leverage each healer.


I'm Done, Thanks For Reading


We are here to protect you from the terrible secret of (healing) space.

Friday, September 9, 2011

Elune, We Have A Problem

Sometimes when progressing through raid content, you encounter an unusual situation: you're failing. To be more specific, you're repeatedly falling victim to an avoidable damage mechanic. Hopefully, this situation doesn't arise often for you but when it does, it's vexing.

The other night, I found myself in this predicament. This is quite unusual for me. I'm not an infallible superstar by any means; I sometimes make mistakes with decision-making or will die to something I shouldn't have. However, I'm usually extremely good about not getting blown to bits by a straightforward, avoidable mechanic and I almost never make the same mistake repeatedly.

That being said, that is exactly what happened to me against Ragnaros. When he does his Sulfuras Smash (bringing down his hammer somewhere on the platform you engage him from) three waves of lava spawn from the impact point and rush away from the hammer: directly away from Ragnaros and in each direction perpendicular from the vector of the wave racing away from Ragnaros. (It's simpler in reality than to explain, basically it's right, left and forward).

This should be easy to avoid. Every guide says it is, it looks like it is to me and it's the type of thing I usually avoid with ease...without even thinking about it. Be that as it may, I was not avoiding it with ease. I wasn't getting hit by it every time (thankfully) but I was dying to it far more than I should have, which put a strain on my fellow healer and, thus, the raid.

So what do you do when this happens? It's frustrating, all the more so because it feels so out of character and you wonder if your raidmates are silently judging you. Maybe it's just a bad night, or perhaps it isn't. What's called for is a diagnostic process! We love processes here at Holy Word: Delicious. If all of life could be boiled down to a process, we here at Holy Word: Delicious would die happy (according to a proper death process).


Step One: What is the nature of the fail?


Obviously, you have to start with identifying what's going wrong. Nothing drives me to distraction more than someone responding to a "How did you die?" query with "I dunno."* If it wasn't apparent to you when you actually died, check logs and figure out what it was. Not knowing means it's going to happen again. And again. There are some useful tools to figure these things out, even during the raid. Make sure you always have some way to go back and check what happened, if it wasn't clearly apparent. You always have the in-game combat log, if it comes to that.

*You can get the craziest accounts from these types of people. "It was so weird, I was just standing there and then suddenly I was dead! Might be some kind of bug, because I was totally not standing in anything and didn't do anything wrong. What's that? There's a debuff the boss puts on you during that stage that makes you explode if you don't /point and then /dance? I didn't know that but I'm pretty sure that's not what happened. I don't think I had a debuff. I think it was a bug."

In my case, it was the above-mentioned Lava Waves that are produced from the Sulfuras Smash. Pretty cut and dry. I saw it hit me, I saw the DoT it placed on me and I saw my charred corpse immediately after. The arrow of causality isn't too hard to draw there.

The first step of the process, then, is knowing what the fail is.


Step Two: Why are you failing to that?


Would you like to be killed by this mechanic? (Y/N)
> nah
You do not fail.
> pew-pew
You critical strike the boss for ***48302*** damage!

This is not how World of Warcraft works ever since build 2938.12.21 in the original beta. Sadly. If we could simply choose not to fail, we never would. We are (generally) trying to never fail. So when we fail to something, there has to be a reason why. Why, despite presumably not wanting to fail, did we fail? (Believe me, even if you're not asking yourself that question, your raid leader likely will be eventually.)

So you have to have some sense of self-awareness. You have to be thinking about what's going on, or at least passively recording the events in your mind so that you can revisit them from memory after the fact and do a post-mortem. You need to know why that mechanic was a problem for you.

Here it was in my case: We were two healing Ragnaros (ten-man raid, obviously), which is quite do-able. I was primarily responsible for the tanks, but couldn't focus entirely on them. When two-healing the encounter, the raid can't afford one healer to be healing the tanks and no one else. There's too much damage to too many spread out people when things like magma traps are set off.

The tank damage was fairly spiky. The tanks swap due to the stacking Burning Wound debuff that Ragnaros applies to the tank he's currently pummeling (exacerbated by the Burning Blast ability that causes damage based on the Burning Wound stack). Ragnaros himself hits like a truck and the tank who isn't currently absorbing Ragnaros' abuse with his/her face is still taking enough damage from the aforementioned abilities (that take 20 seconds to drop off even when not tanking him) that that tank's health will still drop rapidly if ignored.

So. The tanks were leaking health rather rapidly and there were other raid members to heal. My best instant, Power Word: Shield, has limited value in the fight because someone who has just taken damage (other than the tanks) is not necessarily likely to take damage again within the duration of a Power Word: Shield (15 seconds). A shield that simply runs out of duration is nothing more than mana thrown into the fire (pun intended). So I don't have a ton of mobile healing. The feeling that someone would die kept me feeling anchored. This doesn't explain the failure (healers needing to move in addition to healing is nothing new), but the post-mortem isn't over.

The above issue naturally led me to trying to move the least distance possible to avoid the lava waves. Nothing wrong with that, that's what you should be trying to do. However, it led to a couple of issues.

  • If the hammer came down next to me, all I did was move to a diagonal vector from it, which is what you're supposed to do to be in the "safe zone" (since the waves move toward compass point directions relative to the hammer). However! If you're standing right next to the hammer, the waves are too close together for the diagonal to be safe...you'll still be clipped (annoyingly, the effect radius is larger than the visual radius, but that is nothing new in World of Warcraft).
  • If the hammer came down far, far away from me (like on the other side of the pretty enormous platform), I was making hasty guesses as to where the straight line vectors of the waves would take them by the time they reached my vicinity and moving quickly to where I figured the "cone of safety" would be. Sometimes I guessed right, sometimes I died.

These two situations were what were undoing me. This ties into the stationary feeling of having to heal without pause because, frankly, I was using flawed strategies to avoid waves in those two situations to minimize casting down time.

Now, let's be clear. This is an explanation for the purpose of personal diagnosis and improvement. It's not an excuse. I was not justified in dying to those waves, I wasn't the victim of unfairness. I'm laying it out, here, not to exonerate myself in your eyes (I mean, if I worried about your judgment, I wouldn't even have mentioned this, now would I? Right?) but to provide a concrete example of how, in my view, one should approach understanding the problem to solve it. You need to be able to explain it in your own mind. This really shouldn't be for public consumption (that is, for your raid) because it will sound like excuses. And you really shouldn't be intending to use it as an excuse. Explain it to yourself and understand it but do not confuse it with excusing yourself. You need to fix it.

So step two of the process is understanding why that identified mechanic is putting you in an early grave.


Step Three: So what are you going to do about it?


Breaking your keyboard is not the right answer.

Once you've identified the problem mechanic and discovered why it's a problem, the final step is to figure out the work-around. Every problem has a solution, unless you're pushing a world's-first on a boss that wasn't released on the PTR--then the problem may not have a solution until Blizzard hotfixes it while you're in the middle of your raid. But I digress.

You've broken down the ramifications of the mechanic and identified which aspect is making it difficult...so what action will neutralize it? Sometimes it can be as simple as an add-on giving you a BIGGER WARNING on your screen (complete with Christmas lights and a wacky waving inflatable arm flailing tube man). Sometimes it will require mapping out an actual movement or spell choice strategy ahead of time. In my specific case, it was the latter.

I had identified which situations were problems: hammer dropping next to me (not on me, I never got hit by the hammer itself!) or hammer dropping very far away from me. The hammer dropping at some midway distance was no problem...seeing the diagonal quickly and moving into it was easy.

The answers, once I knew the precise nature of the problem, turned out to be easy.

  • In the case of the hammer dropping right next to me, I had to move away from the hammer on the diagonal vector. Standing next to it, even on the diagonal, wasn't sufficient. If I saw that the hammer was going to be right next to me (and you do get an indication ahead of time), it was time to shield the tank, maybe put a Renew up, a Prayer of Mending and then get the heck out of Dodge. Get to the new spot and then spam fast heals to make up any deficit I had fallen behind on while moving.
  • In the case of the hammer dropping far away, I had to move forward into melee range, not backward looking for the diagonal. The hammer is always dropped far enough away from Ragnaros that a wave will never blast through his hit box. I can't stand in melee all the time to passively avoid waves because (designers being crafty like that) Ragnaros has a silencing knock-back...if you're standing in melee range and casting when he does it, you get locked out of the spell school you were casting in for something like 5 seconds (which is an eternity when the tanks are dying). But running into melee range and then back out immediately, after the wave has raced past, causes no ill effects.

Once I put these fixes into action, things got better immediately. It was immensely easier to avoid the waves and with minimum thought and movement (the better to use that thought and time for healing decision-making).

So the third step of the process is to create a plan that will work around the problems you've identified.


Step Four: I Forget What Four Was For


So, that's The Process. It's always nice to have a process to work through to solve problems. Admittedly, none of the steps I laid out are a revolution in logic, philosophy or spirituality, but it's good to formalize a thinking process rather than fall into the "Well, that sucked, I'll try to do better next time" trap. That's surprisingly easy to do and very tempting...you know the mechanic, you messed up, you'll just try harder next time. However, if there's a specific problem that's causing you to miss the mechanic, you'll probably keep failing at it until you (implicitly or explicitly) go through the above process.

Ultimately, if you still keep struggling with the mechanic, it's probably a bug. Or latency. Or a lag spike. "It was the craziest thing..."

Wednesday, September 7, 2011

How To Win Raiding

Those of us who enjoy the raiding aspect of the game are always seeking to raise our games, step up our efforts and engage in other sports/corporate cliches. In short, we want to be the best raiders possible. However, raiding guides usually deal in rather obvious tips like "Stay out of fire" and "Always have a food/flask buff." Those might help, but if you really want to become a truly pro raider, you need the advanced secrets of raiding.

That's what this piece is about. How to squeeze out the extra throughput that average raiders simply don't attain. Read on.


Select The Right Music


The right music in the background will make or break you as a raider. Average raiders listen to the default encounter music within World of Warcraft or to nothing at all. The finest raiders in world ranked guilds select the proper pop/rock/hip-hop/electronica/R&B/soul music to push them to higher levels.

So what is the proper music? That's a trickier question, as it doesn't follow simple rules. This isn't something basic like gear itemization; this is complicated. It has to be a playlist that energizes you at the right times but provides some chill cooldown when you need to recover your intensity. Ultimately, this is a difficult one to spreadsheet, though I'm working on it*.

*Preliminary research is revealing that balearic dance-pop is likely the "primary sound" that will be the baseline against which all other genres will be weighted, for all classes


When Forced To Move, Jump While Moving


You move faster when jumping. This has been empirically proven*. Further, jumping when casting an instant spell supercharges it slightly (though it's a non-stacking buff, so don't jump multiple times before casting it). I think Elitist Jerks had a thread on this at some point. In any case, I've never seen anyone specifically deny this. If you have to get out of poison, jump while moving to your new position.

*"Empirically proven" means "it feels true."

I shouldn't need to explain this...the faster you move, the sooner you can start DPSing or healing again. And stronger spells are always nice*.

*There is a reason restoration druids always top the healing meters.


Mentally Tack On A "Loot Phase" To Every Boss


Beth'tilac has three phases. The phase which she spends her time atop her web, the phase in which she descends to attack the raid directly and the phase in which you collect the loot she drops. Rhyolith also has three phases. Etcetera. When discussing boss strategy, it's important to know that this is the phase you need to reach*.

*This also makes explaining the fight to new recruits much easier--just get to phase 3 (or whichever phase is the loot phase for a particular boss)


Bonus Patch 4.3 Exclusive Tip: Dress For Success


This is really not a tip you can put into effect right now, but it's worth discussing since you'll soon be able to address this issue. Currently, Blizzard has introduced an RNG obstacle in raiding--the negative effect of ugly raid gear. Some tiers the gear is decent in appearance, some tiers the gear looks designed by a bored monkey. You have no control over this and Blizzard intends for this to be an RNG effect...it's filed under "demoralization effect" (distinct from disorientation, fear and stun effects).

However, patch 4.3 will introduce transmogrification...an ability meant for prepared raiders to remove this randomness from encounters, much as tanks push crushing blows off the table. You'll be able to modify the look of any visible piece of equipment you wear to any other similarly-slotted piece of equipment that you own, with a few restrictions. This means that it is incumbent upon you to create a fashion style that will remove the demoralization effect any time that your raid gear looks terrible. If you don't do this, you cannot honestly claim to be giving your raid your best effort.

Monday, August 8, 2011

Raid Leading For The 21st Century

Raid leading is an activity that can be both overrated in importance and underrated. Like coaching in professional sports, ultimately the "talent" being managed has the biggest impact on success. No matter how good a leader you are, you need smart, dedicated players. If you have that, though, smart and efficient leadership can either maximize the efforts of those players or leave a little potential on the table.

I do not currently lead a raid, but I have in the past. My thoughts on how a raid should be led are partially based in what I've done and partially based on what I've seen others do while in the raids they led. As my focus on this blog seems to have evolved into thinking about processes in playing World of Warcraft, I thought I'd try to formalize my thoughts on the process of leading a raid team.

I should also note that these principles are meant to apply to guilds that are progression-minded. Guilds who have a more casual, social mission are just as valid and worthwhile, but will probably want to proceed in a different manner.

Follow me, then, on this intellectual raid. I cannot promise you'll get the drops you hoped for, but hopefully the fight itself will be reward enough. </tortured-analogy>


Populate Raids For Fairness Not Inclusiveness


Rotating raid members so that more than the maximum your raid format allows (10 or 25) can play is great...if all the raid members in question are of relatively similar ability. That doesn't mean small variations in ability should deny certain members from ever getting a raid spot, but you don't do anyone any favors bringing people who can't quite pull their own weight, unless it's for farm night. Not only does your raid team start struggling to down the bosses they would have normally, it's not going to fun for the person shoehorned in to feel the pressure of being the reason for the struggles.

Like any other competitive endeavor where spots are limited, you'll create the healthiest environment where implicit competition (that is, the best performers--counting in awareness--go to raids) rules. This does not mean that it should be a hyper-competitive atmosphere, with elitism and trash talk being tolerated. Being dedicated and competitive in no way requires fostering a society of assholes, to put it directly. Assuage your guilt, if you feel it, for not inviting certain people to the progression raid by working with them (if they're receptive) to close the gap. Make sure you get them into farm/alt raids. Your goal should be to legitimately have more qualified raiders eligible for the rotation, not artificially forcing unprepared raiders into the rotation.


Keep Fight Explanations Concise


I'm going to be honest--anyone who deserves a raid spot should already know the general mechanics of any fight that it's plausible that your raid might encounter that night. That means, at a minimum, the encounter your raid team is currently working on and the encounter you plan to get to next. No one should be joining the raid and winding up at the boss pre-pull needing to know how this fight works. If you want to stress a certain point or two about the fight for people to especially focus on, or a quick note on how you might plan to deviate from the popularly accepted way to attack the encounter, that's fine. Explaining the entire fight, every phase and mechanic, costs the raid team time and focus. Many people zone out during long explanations, right when they should be entering a state of sharp focus.

There is one major caveat to this: If you're bringing in a new raider to your rotation, who has yet to enter the raid instance you're doing, it may be that you have five or six bosses on farm and it's the seventh that you're working on. It can be overwhelming to demand that the new raider learn up to eight encounters for the first night (though, it's far from impossible...I've done it!). If this is the case, limit the fight explanations, before each encounter, to just the things that single person needs to know. A new DPS doesn't need to know about the tank swap on Cho'gall. A new DPS doesn't need to know about what to do while flying, against Alysrazor, if they're going to be on add duty. If they would like to know the entire picture of the fight, ask them to consult their local library. For now, they just need to know what they, personally, must do to help the raid defeat the boss.

Again, blasting through each of the twenty mechanics in play on an encounter isn't going to do anyone any good. Not even the person who's benefit it is for...there is little that is more disorienting than getting a rapid fire recitation of three phases, each with six items that occur, that you need to memorize and utilize with no time to process and consolidate the information. Even the new person will be far better off with an explanation laser focused to just the mechanics that they, specifically, will deal with.  Wasting precious raid time and benefiting no one is clearly a mistake when leading a raid.


Transparent Loot Council


This is probably going to be the most controversial element of my post, but let's be frank: people, like raid leaders, already have a large element of control over what loot an individual member gets. By selecting who comes to a raid or encounter, they've determined who even has a chance at loot. Crafting materials, often very valuable, are also often not distributed by DKP, EPGP or /roll. Many guilds take the crafting materials for the good of the guild and distribute it later based on their view of need.

So, it's not like the concept of people in the raid or guild making decisions on loot is repugnant to most people. What I think generally is repugnant is a loot council that operates like a secretive cabal. That's when suspicions of favoritism or poor decisions happen.

(I recognize that in many guilds, loot distribution policy is determined by the guild master and/or officers, not the raid leader specifically. In those cases, consider this section to be more "guild management as it relates to raids" rather then specifically "raid leading.")

Let's first go into why a loot council is valuable, assuming this loot council is run correctly (which I'll get into later). Loot serves two purposes: fun as individual fulfillment of getting a new piece of gear and a tool to strengthen the raid to aid in the fun of downing difficult raid encounters. The more progression-oriented a guild is, the more they should want to focus on the second, viewing loot less as individual reward and more as tools to be efficiently deployed in maximizing the raid's overall power.

That is certainly not to say that the fun of personal progression (your individual power increasing) should be completely forgotten--but it should be secondary. That means that a clean rotation of loot is not necessarily ideal; if a piece of loot can best be used by someone who happened to get the last piece of loot, you're weakening the efficiency of the raid if you deem that person ineligible for this piece of loot. There is personal fairness (everyone rotates getting loot) and group fairness (improving the team's chances of winning). The members of a progression-oriented guild should have little problem with prioritizing team fairness over personal fairness--assuming they can be assured that "team fairness" is being served.

That's where we get into transparency. While the initial chatter of the loot council, the back-and-forth discussion if any, doesn't necessarily need to be broadcast to everyone, the reason(s) for the ultimate decision certainly need to be. "TraderJoe is going to get the bow," is not an acceptable statement to the raid. "While both TraderJoe (a hunter) and VicRush (a warrior) can use this bow and the stats can benefit both, the agility will benefit TraderJoe much more and ranged weapon DPS is a huge factor for hunters while it has no effect for warriors. Therefore, TraderJoe will get the bow" is an acceptable statement to the raid. It forces behind-the-scenes favoritism out of the equation--at least, overt favoritism. Favoritism could still rear its ugly head via weak rationales aimed at moving loot to a specific person.

That is why these loot council positions should be elected spots, voted on each month. Presumably, the raid will initially elect the three (or however many people you decide to place on the council) most trust-worthy and knowledgeable individuals in their eyes. If it turns out that any of them were actually ill-suited to the position, that can be set aright. You can vote each week, two weeks, a month...the period is really up to what works for your guild. But they should be accountable for their decisions, so they have incentive to make good decisions.

The fact of the matter is that just rotating loot doesn't always yield the optimal distribution. A lot of guilds will invoke the "common sense" clause in their charter regarding loot distribution, but one person's common sense may not be another's. Involving several people, people that the raid/guild members respect, and keeping those people responsible for making wise decisions and communicating those decisions reduces the risk of bad outcomes and the ensuing guild drama.

There's a saying that the best (conceptual) form of government is a "benevolent dictator." The reason for this is because a dictator can rule most efficiently (lacking the bureaucracy to slow their efforts) but, being benevolent, uses that power for good, not evil (greed, ambition, etc). I'd modify that to say that best form of loot distribution is enlightened loot council. A loot council that is picked for knowledge of how classes work and trustworthiness, can be modified if they overstep their bounds and distributes loot to those best able to use it.


Did You Ever Have To Make Up Your Mind?


Decisions. You must make them. Further, you must make them quickly and decisively. It's perfectly reasonable to solicit some input...the bigger the decision, the more input is reasonable. However, when it is during a raid--like deciding which boss to attack next when you have choices--time is of the essence.

As an example, imagine a raid rolled into Firelands on their first raid night doing heroic content. Perhaps their choice was to go after Beth'tilac first and Shannox second. They thought it would take the entire night, at least, to get both down. To their shock and delight, they one-shot both bosses, never having done the encounters before on heroic mode. Great...but now what? They have half (thanks to trash) or more of the raid night remaining. Perhaps the guild knows both the Alysrazor and Lord Rhyolith fight on heroic (from reading up on it). Which boss to go to next? The raid leader, talking it over with officers and perhaps others, takes fifteen minutes to make this determination. In a three or four hour raid night, fifteen minutes is a pretty significant chunk of time. Raiders also lose some focus as they wait around for a decision.

That should not be you. You'll have to make decisions quite a bit...whether it's choosing the next boss, shuffling the raid make-up on a per-fight basis, calling for a wipe in a pull gone poorly or perhaps even deciding when to call a raid night to an end for one reason or another. Taking undue time in making these decisions will not destroy the raid, but it will weaken it a bit, dropping its potential slightly.


The Great Communicator


As a raid leader, you must be a good/great communicator. Your job is not merely to make decisions--it is also to communicate those decisions to anyone affected. Your decisions will negatively affect some people, obviously, and it falls to you to ensure that they are given a reasonable explanation for why they got the short end of the stick. A "reasonable explanation" means an explanation that a mature adult can understand the logic and fairness of, delivered without rancor.

You may at times have to play counselor. Any leadership position involves managing people, which means understanding their concerns and displeasure and helping them get past those without adversely affecting the raid itself. If you don't have patience or the willingness to discuss issues outside of raid times, you can't effectively raid lead. We'd love for everyone in a raid to be an efficient machine that leaves emotion out of the equation--but that doesn't even happen for sports teams consisting of highly-paid athletes. Given that, you certainly can't expect it from a group of people playing a game and playing for your raid for free (by which I mean, the guild or raid doesn't pay them...not that World of Warcraft is free). People will get angry or unhappy or frustrated from time to time, and it is definitely your job to handle it gracefully. If you feel that it's unfair to have to play therapist in a game, then you should pass the raid leadership to someone else.

Finally, you need to foster a sense of camaraderie and good spirit within your raid group. People can play together with no sense of connection, but people in all walks of life tend to perform a little bit better when they're a part of a social interaction that they enjoy. It also makes your raid members more willing to deemphasize personal progression for the good of raid progression and less prone to drama flare-ups.


Leadership Is Just Facilitation


Really, the core idea behind all of these principles is being the person that makes raiding smoother. No more, no less. You're not there to "raise everyone's game" or to be a scolding parent or to keep everyone on the straight and narrow. You're just there to ease everyone else's raiding experience, allowing them to focus purely on their efforts within each combat. If you're doing your job well, people will only notice smooth, enjoyable raids...not you.

Thursday, August 4, 2011

Ragnaros Wants You To Try Harder

I haven't posted in a while. Did you miss me? No? Well, straight to the text then.

Recently, I feel that I've fallen into a common pitfall...common in World of Warcraft and common in the Real World. Reaching a point of comfortably adequate performance and settling into cruise control. I think I'm a competent healer. Better than competent; a good healer. It's notoriously difficult to rate healing proficiency and notoriously difficult to self-evaluate (what with competing dynamics of seeing yourself in a sympathetic light--after all, you know what you meant--and wanting to be tough on yourself), so I couldn't say with great certainty how successful a healer I am, but I'm secure that I'm somewhere in the top half and not the bottom half. Hopefully, anyway.

The main thing, though, is I feel relatively sure that I'm not holding my raid team back. If we struggle on a boss, it's probably not due to me. Now, I mean this in general...on any specific wipe, it could certainly have been due to me. I'm far from mistake-free. But if we're hitting a temporary wall on a boss, I am probably not the bottleneck. Hopefully, anyway.

I think this has led me to (at a subconscious level) feel comfortable doing what I do, as far as decision-making and awareness. That's a big mistake, but an easy one to make. I think most people are prone to end the evaluation at "Am I playing well enough to help my team? Am I a problem or an asset?" If the answer is "asset," all is well.

All is not well, though. Playing well enough to help the team or playing well enough not to be the reason for team failure isn't the correct goal and, put explicitly in that fashion, I think most people would agree. But at a subconscious level, "I do enough" is a tempting evaluation cul-de-sac.

The aim should be to find ways to be more of an asset. You may not be the reason for failure (whenever failure crops up) but perhaps you could be the factor that averts some failure. Maybe you can do your job and help with another job. Or, find a job that isn't being done but would be useful and do it. Often, the "job" can be something as vague as "knowing mechanics that you, specifically, aren't responsible for carrying out and making sure they're not being lost in the shuffle."


An Example...My Kingdom For An Example


Let's take the Shannox fight. Let's take my role in the Shannox fight. I, as long-time readers will remember, am a discipline priest in terms of my main character. My explicit role in the Shannox fight changes over the encounter; I start out healing the Face Rage targets of Rageface (instant shields are a nice quick buffer). When Rageface dies (as we choose to focus him down right away), I become the tank healer for the Riplimb tank. When Riplimb dies, I join my fellow healers in keeping the Shannox tank, and the raid in general, alive until loot time.

I make mistakes (especially at first, before I made sure Grid was showing the Face Rage target /facepalm), but by and large I think I do a good job keeping the people alive that I'm responsible for. I mostly do a good job of avoiding traps (except for a night last week where I got hit by two of them, after never having been hit before... /facepalm). That's essentially the extent of what I'm supposed to do. Keep my targets alive, don't die or get entombed. And if I do those things, I'm an asset, clearly.

But could I be more of one? There are always more things to do. When healing the Riplimb tank, it's not that stressful...there are times when the dog is playing fetch with a spear and I have time to do something else. One thing I could do is obvious: heal someone else. And if someone else is in range and below maximum health, I do that. A less obvious thing I could do is remember that if Riplimb is pulled too far away from Shannox, they enrage--an eventuality to be avoided.

So tonight when we were doing the encounter, even though it's a farm encounter, I decided to expand my role a little. The tanks have their own things to keep track of; in particular, the Riplimb tank is generally looking for crystal traps to freeze the dog, which can take away his attention. So I watched where Shannox was being pulled and tried to suggest to the tank when he may want to move the dog a little closer.

Of course, the first time I did this, my warning came a few seconds before they enraged. The second time, mindful of what happened the time before, the tank was already moving the dog. So all in all, I don't think I added value in that way. But I could have, had I been a little quicker to decide I was going to try to help. The important thing was not really whether I successfully averted something that time but rather that I was making the effort to push beyond the bounds of my role that I had become comfortable in.


Examples Aren't Sufficient


So what is it we should be doing, more generally? I think this is what we should be striving for: keep track of as many things about the current fight that you can before it starts degrading your performance on your main tasks. It doesn't matter what value you add at the margins if you're failing to do what you're paid for--whether that's keeping people alive, keeping the boss faced the right way as it pounds your face or putting magical bullets in the boss. Nothing matters until you have that locked down.

However, once you realize that you're doing your job and starting to put it in cruise, it's time to add more to your plate. Think like a raid leader...orchestrate the fight in your head and watch what's happening. If you see something headed in the wrong direction, be prepared to either warn the person who can act on the warning or else take steps yourself that will avert the crisis before it happens (while not lapsing on your assignment).

To some extent, this advice is dependent on how your guild operates raids. If there's a clear cut raid leader who is the only one allowed to call things out or issue warnings, then that option is off the table for you. Despite that, if you act as raid leader in your mind, you will undoubtedly see opportunities to add a little bonus value.

Whether your official role is healer, tank or DPS, we all unofficially have the same role: find the gaps in the clean route from pull to kill and fill them.

Monday, June 27, 2011

What Is Pride?

Recently, I was (very indirectly and not in any sense singled out) accused by a guild member of not having enough pride in raiding. We hadn't defeated an encounter prior to (what is expected to be) the next tier of raiding coming into existence tomorrow.

What made her angry was that most people (myself included) didn't choose to devote the entirety of the (anticipated) final raid night of this tier to trying to complete the encounter (we killed off our farm bosses in Blackwing Descent first). She felt that this displayed the weak nature of the raid team, a "wimping out" (my words, though I don't think it's a distortion of her feelings), if you will.

I cannot speak for anyone else on the raid team, I only know my own motivations and it led me to wonder: what is the role of pride in raiding? In what ways should one display pride?


Pride In Effort


This post will in no way be a response to that guild member. She's perfectly entitled to feel as she does and I'm not interested in changing her mind. I only mentioned the context in order to explain why I was provoked to think about this issue. I'm not going to spend any time "justifying" the event that annoyed her (because, like many things, it's only right or wrong depending on your approach) but I will mention her occasionally simply to note the differences in our outlooks that may have led to the difference in reaction (which I think is something everyone should bear in mind when evaluating others).

I can confidently say that I do feel a sense of pride in raiding. I think that any time one engages a lot in an activity that involves a skill, one tends to discover a desire to do it as well as possible. Pride, then, comes from the degree one meets that desire. I am certainly not exempt from this when it comes to raiding in the game.

When I raid, I want a few things from myself. I want to be geared well, gemmed and enchanted intelligently (no pun intended as a caster) and possessed of a talent spec that I carefully considered (both based on research and my own experiences playing the class). That's the first and most basic standard: proper preparedness. Secondly, I want to focus as deeply on the task of each encounter as possible. Finally, I want to learn (both encounter mechanics and my own role) swiftly and whenever possible.

Those are where my points of pride come from. I do believe in perseverance. I'm actually quite willing to beat my head against an encounter for days or even weeks. But this is probably the first place where my angry guild member and I part ways a bit. For me, there is no pride in perseverance. For me, perseverance is always balanced against fun.

Generally, this is not an issue that takes consideration. There have not been any raid encounters I've yet run across that I didn't enjoy. Sure, some were difficult and frustrating at first, but even that was fun in a way: trying to unlock the secret. Al'Akir was frustrating at first, because it felt far too random. I actually came to enjoy that encounter, though, as I discovered ways to ameliorate the randomness. That learning process is extremely enjoyable for me.

So, if a boss is blocking progression, I'm happy to fight him for the next ten weeks (though I'd be a little concerned if we, as a group, were taking that long to defeat an encounter). If the boss in question is not blocking progression, and the raid wants to switch to a different boss, I am fine with that, too.


Pride In Being Relevant


A further point of pride that I experience, which is unrelated to my personal performance, is feeling that what I'm doing is "relevant." That quite simply means that I'm working on, at least, the highest current tier of raiding. I don't have to be on the bleeding edge of progression, but I certainly don't want to be working on the tier behind the one that most raiders are on.

I don't, however, have much of a sense of pride in getting a certain achievement or title while it's relevant, "just to say I did." In fact, achievements are relatively unimportant to me in general. I raid for the social aspect of working as a team and the excitement of defeating a difficult boss for the first time. I don't care if I can say that I got the "Light of Dawn" title before patch 4.0.1 dropped (which is good, because I can not say that). This I know is another point of departure between myself and the guild member who felt I (we) lacked pride. I know she feels fiercely passionate about "being able to say" that she did certain things when said things were considered relevant. That's fine, it's simply not where I derive my pleasure or pride.


So Wherein Lies Pride?


I'm a healer. I'd like to heal well. I'm a raider. I'd like to raid on tier. I'm a guild member. I'd like to be considered an obliging, considerate team member.

So my points of pride essentially revolve around those fairly straightforward statements. I don't really consider my place in the greater World of Warcraft universe (world- or server-progression). I have my own views on what healing well entails, but I rarely compare myself to even my fellow healers. Foremost, I'm raiding because it's a game I greatly enjoy playing with others. Pride may goeth before a fall but it sure doesn't goeth before fun, as far as I'm concerned.

I feel badly that my guild member is unhappy about not accomplishing her (guild) goals for this tier. I understand why it upsets her. While I cannot speak for anyone else in the guild, I can say that her goals (in a general sense) diverge from mine subtly but crucially, which leads us to very different concepts of where pride comes into the game and, therefore, what issues are a matter of pride and what issues aren't.