Showing posts with label thinking. Show all posts
Showing posts with label thinking. Show all posts

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..."

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.

Monday, March 21, 2011

What Can Healers Learn From Great Athletes?

It's quite a conceptual twist to compare healers in World of Warcraft to elite athletes. After all, the image of healers is that of somewhat effete, scholarly individuals in robes (bafflingly, even mail- and plate-wearing healers often get robe-like garments) who worry over injuries. The clinical term for this image is "sissies." But, in fact, healers perform the most like elite athletes and, hey, it's a good self-image to foster, so let's go with it.

Since WoW is not a physical game (outside of dextrous fingers, perhaps), it is really the mental side of things that I'm discussing. I'm a fairly big fan of watching great athletes perform and one trait has become clear to me as common among all top athletes and that trait is crucial for top healers. That trait is how to think in the heat of the moment.


Thinking Is Bad


I know, I know. You've always been told that it's good to think. When it comes to the mental side of life, you won't find many people who are anti-thinking (opportunity for political joke purposely passed up). But honestly, where has it gotten you? If you're an athlete or healer, the answer is "Not far." At least, not while you're in the midst (opportunity for sexual joke purposely passed up).

You see, athletes struggle when they fall into the thinking trap. Professional sports moves at far too quick a pace to be pondering your next move. If you get the ball, turn to face the defense and think about what you're going to do next...chances are, by the time you decide, the ball has already been taken from you and scored on the other end. That's too slow. The state you have to be in is having encoded a high level pattern-matching into your neural pathways such that you can see the defense and instantly transform what you see into an action. We could call that instinct, but that connotes a born-in nature that is not necessarily the case. You can acquire some or all of this from massive amounts of practice and experience. In some sense, you're completely bypassing the conscious thought center of the brain and operating on a subconscious level. This level is woefully inadequate to handle life in general, but can possess specialized synapses for transforming a scene in front of you, in a specialized situation (like a basketball game), into a series of commands to your muscles. By the time your conscious mind catches up, it's only to realize what you've already done...the play is over.

That kind of read-and-react magic is instrumental for healing in a raid, for anyone who's not a dedicated tank healer. A dedicated tank healer is much like a DPS...they don't have to process as quickly (though, quicker processing is always helpful) because they tend to fall into a more reptitive rhythm with much tighter constraints. DPS, these days, is no longer the purely reptitive "rotation," but even with a priority-and-proc based system, the range of possible situations is quite a bit lower than is faced by healers. This is in no way meant to diminish the difficulty of DPS...great DPS is just as difficult as healing, but in a different way. A way that I'm not concerning myself with here (but, if I were to use a metaphor for it, I'd use a great musician, not an athlete).

As a healer who has multiple people to keep alive, you simply cannot be operating at the relatively slow speed of: "Okay, what heal should I cast now? Let's see, four people are hurt, but they're not all in the same party...further, one is especially hurt...but a different person is more important to keep alive...maybe I should cast..." Even at the speed that the mind can go through all those conditions (much faster than it took to write or read those words), it is still too slow. You can't consciously be breaking down the situation every GCD in order to make a decision. Damage goes out far too quickly for that, especially in certain stages of the fight.

No, you have to be Michael Jordan or Gale Sayer or Barry Sanders (yes, that was an awfully American-centric list of great athletes; I'm American, that's how it goes. Okay, okay, I'll throw in Pelé for the international crowd). You have to be moving before your conscious brain has processed what you're doing. It has to be pure pattern-matching automatic reaction. Developed instinct.

How do you develop that instinct? Lots and lots and lots of practice. You have to heal a massive amount of fights. And the fights that will help you the most are the hard ones...the ones that make you think healing is a shitty, thankless job of keeping stupid people alive despite all their stupid mistakes. The more damage that is happening, the more you have to do in every moment, the more you're burning in patterns by a very natural and biological process of automatically connecting actions with results. In this situation you cast a Prayer of Healing and it did a laughably bad job of saving anyone. In this situation you used a Greater Healing Wave followed by a Riptide followed by a Chain Heal and kept everyone alive when you thought they'd die. The process of successes and failure creates patterns of neural activity that are then better equipped to match an action to the next scene of healing it sees...which reinforces and refines those patterns of neural activity that are then better equipped to match an action to...well, rinse and repeat. It's the feedback loop of learning. But it takes a lot of exposure to what you're learning.

The more you refine those neural patterns, though, the less your conscious mind will interfere with your ability to "feel" the situation and fire out the right action, moment by moment. Just like Jordan attacking three defenders near the basket, or Barry Sanders encircled by five defenders all intent on doing him harm. They don't "know" how they get through those defenders...they just do get through the defenders and they do it automatically. Later, maybe they or an outside analyst could break down what they did...but it was all by the magic of pattern matching at the time. They saw the defenders, their neural circuits transformed the vision into actions and their muscles carried it out. That is how you heal Magmaw or Chimaeron or Lady Sinestra. See the damage in your Grid, see the fail spot that may be under your feet and let your neural circuits transform it into actions.


Thinking Is Good


Wait, but isn't thinking bad? Didn't I just write an obscene amount about that very topic? Yes, yes I did. But I changed my mind and didn't want to delete everything I just wrote.

Well, not really. There are different levels of thinking. There's the short-term "What do I do next?" thinking and then there's the long-term big picture thinking. This second sort of thinking goes more like: "Where are we in this fight? How should we be deploying our resources for the next phase of the fight? Why were we put here on this Earth? What does it all mean?"

Those last two questions are beyond the scope of this piece. But, hopefully, you get the idea. Not having to consciously think about what you are doing moment to moment does not mean you should zone out and dream about winning the lottery. You could do that, but what a waste...what, then, would you think about when zoning out in work meetings? No, what freeing up your conscious mind does for you is allow you to monitor the fight overall, figure out how it's going and start determining your personal strategy for later on in the fight.

After all, there are cooldowns to be employed and possibly large scale positioning changes to be made and maybe you'll want to hand off a healing target to another healer, or take on theirs, for one reason or another. All these things are good things to be pondering while your fingers are busy doing what they do (opportunity for masturbation joke bypassed). Your subconscious mind is hard at work pattern-matching while your conscious mind is hard at work monitoring and strategizing. You see, contrary to popular legend, we use all of our brains...we're just consciously aware of only a part of it.


I Think I'm Done Here (The Big Finish)


Healing and DPS are as different, as I alluded to before, as being a great athlete is from being a great musician. They are both exceedingly difficult, but in different ways. For DPS, it's about muscle memory and establishing a dynamic rhythm. For healers, though, it's about creating specialized patterns of neurons that have "learned" what patterns of damage visible in your raid frames result in what actions. There are an infinite amount of patterns of damage, so these neurons don't work like a list of damage->action rule pairs. They see the damage as overlapping courses of action, with one of those courses of actions winning out at any given time.

So be like Mike, as our corporate overlords urge. Develop these instincts and free your conscious mind for wondering why you're even in that raid, healing a bunch of losers who stand in fire. It's a much better question to be pondering than what healing spell to cast next.