Monday, June 28, 2010

Losing a tank in 1.5 sec - a Beacon of Light story

Yesterday Chase posted a fairly vanilla writeup on Beacon of Light (BoL) best practices, which is probably fairly useful to his target audience - brand new Holy Paladins. He covers the basics of putting BoL on the tank, or yourself, or switching for things like Bonestorm - but he forgot one little caveat that goes with Beacon of Light. Unfortunately, it's a big one.

Haste vs. Damage

As a Holy Paladin I'm constantly slamming as much haste onto my paper doll as I can - to the point where I even passed up a 277 upgrade the other day because I'd lose 80 haste in the process. My Holy Lights are pushing 1.2 seconds, and I'm dangerously close to being over 1000 haste. Between my own CDs and a pocket innervate - I can destroy any content without fear of mana or my target dying. I guarantee that unless my tank gets one shot, there's nothing out there that will take them down. There just isn't a boss that can out damage my Holy Light spam (again, short of one shots) - providing all I have to do is stand in one place and heal one target.

Unfortunately, I have more to worry about than just a single tank. I generally am covering at least both tanks, and providing backup healing for the raid. I'm keeping an eye on environmental damage, Valk's, flying ooze balls, etc. This means I have to occasionally move or shift my healing, which means my perfect stream of 24k HL bombs gets interrupted. It also means that I occasionally have to rely on some of my other tools to get me through the night.

Enter the Beacon

BoL was a great addition to our healing arsenal, and I can't count all the ways that I revel in its deliciousness and awesomeness. Healing the party/raid while having BoL on myself (and just ignoring environmental damage). Laughing in PvP while keeping everyone alive (until that shaman/priest show up and purge/dispell it off me). Mocking healers who struggle to keep two tanks alive on Blood Queen.

Until that is, this happens.

Awesome McAwesomsacue tank has died.

WTF? How on Earth did that happen? No special abilities were used, I had BoL on them - I mean, there's no reason why they should have just gotten turned into a plate pancake. My heals can't miss (although I have done things like BoP the tank by accident), he's well within the 60yd range of well - everyone, and the person I was healing is alive! How is this even remotely possible?

Pulling out the death log, I see something horrifying. While the tank was sitting at around 60% for two seconds, there's a 1.75 sec gap between heals landing. This can't be possible, I'm mashing the HL key like my life depends on it, and my cast time is sitting near 1.2 seconds. My Judgement was still up, BoL was up, hell even Sacred Shield was up. This death was unpossible! Now I'm left standing here trying to explain how I just let a tank die on H-LK (or worse, trash) when I'm supposed to be Hasty McHasterson the great Pally healer. Guess that Val'anyr isn't really getting it done eh?

The hidden killer

In reality, what just killed my tank was the inherent lag that takes place in a BoL heal. As best as I can figure (from parsing logs and checking EJ), is that the heal actually has to register on your target before the system will pass the heal on to your BoL target. From a programming point this makes perfect sense, but it does get a little aggravating when you watch your BoL target get folded because the heal didn't get there in time. This means that all the haste we're stacking, will still result in your HL taking about 2 seconds to land every single time.

If this isn't a selling point for more haste on your gear, I don't know what is. Every single cast you put out will take about .5 sec longer to hit your BoL target. That's about the difference between having a judgment up or not - something we definitely strive for.

Avoiding this gib

There's a couple of ways to get around this little bit of lag accidentally interrupting your perfect string of awesomenss, and thereby avoiding the ire of your party/raid.

Know the encounter

This should go without saying, but you need to know the encounter. While a lot of this will come with experience, you should never be surprised when something happens during a fight. Let's face it, 95% of the encounters we face are so scripted that we have a wide variety of mods and addons to run timers for us. You know when that first Mark is going out, you know when Defile is coming, and you KNOW that Soul Reaper is about to hit your tank for Texa$.

Know your tanks

Right behind knowing the encounter, because in a PuG knowing the encounter is more realistic, is knowing the tanks that you're working with. Start cataloging their survivability. Are they taking a lot of damage on trash? Did you find yourself reaching for additional CDs on the first boss? Keep a mental log and use past experiences to prepare you for the upcoming encounter. While the odds of every PUG tank you heal using ORA2 or some other addon that will let you know when they've used their defensive cooldowns, you should be on the lookout for it if you can.

Heal the BoL target

That's right - there's nothing that says you can't switch to the BoL target when you need to. While it's certainly not ideal, neither is losing the target to an internal lag mechanic that you can't fix. This is something I'll do during H-LK. Even though I have BoL on the LK tank, unless someone is in immediate danger of dying, I'll heal the LK tank directly during a Soul Reaper. We had enough problems on this fight when we were working on it. This was a situation I could control, and I wasn't going to pass it up (obviously if Infest is running rampant, I don't have this option).

Change your BoL target

This comes with experience, and knowing where your heals need to go. After losing the Shambling Horror tank to BoL lag a few times, I swapped BoL to the LK tank and healed the Horror tank instead. Problem solved - except for when he'd eat a 70k+ shockwave. Sry:(

This also comes into play on fights like H-Sindragosa. During Phase 1 I'll keep the tank beaconed in case I need to touch the raid, but I generally just heal the tank directly (see the point above). During Pase 2 I put BoL on myself and just heal the tanks for all I'm worth. I rely on HL splash to cover the raid when I have to drop my stacks, but this method lets me build up 10+ stacks of the mystic buffet (though that does make me pucker up).

Communicate with your other healers and the tanks

I put this last, but it's really one of the most important aspects. Working with your tanks and other healers for coverage in heavy damage situations, or to coordinate cooldowns, can mean the difference between a spectacular wipe (where it just says LOLOLOLOL@U in the damage log) and that clutch downing. Rarely is the weight of the entire raid on your shoulders, though it often feels that way.

Conclusion

BoL is an amazing tool, and one of the most powerful spells in our arsenal. No other healer can provide the sheer throughput that we can using HL/BoL on multiple targets, though druids can rack up some impressive HoT stacks. BoL isn't a cure all though, you can't simply slap BoL on your MT and then forget about them. Part of improving as a player is looking at all the little things that have taken place in a raid in finding ways to counter them. Recognizing that your BoL target will be slightly behind in healing received means you may have to keep healing, even if their damage intake is low.

Oh, and stack on more haste.

10 comments:

  1. Absolutely! Good post there about BoL. I've had a few occasions myself where some squishy tank was in danger of going splat if I didn't switch targets.

    And yes, haste is awesome. I'm doing my very best to get as much haste as I can. As soon as I get my T10 headpiece, I'll get an awesome boost on haste, because I can then also replace my crappy T10 gloves. Why oh why do the T10 drops in VoA have to be the gloves and legs?

    ReplyDelete
  2. I really do love Beacon of Light, but there are times to ignore it and spam the tank, praying he doesn't die. Festergut Ph3 comes to mind as the most recent example of what you're talking about - when we were learning it I made that mistake, and the beacon lag "killed" my tank. I can only blame Beacon once; after that, it's my responsibility to prevent it.

    Haste is delightful. Absolutely delightful.

    ReplyDelete
  3. Depending on the version of Festergut that I'm doing (H25, etc) I actually just beacon myself and heal the tank directly (H-25m for sure, reg 25 if the tank is squishy feeling). I pop my Hyper-speed accelerators (followed by a Speed Pot if I need it) and drop my HoSac on the tank.

    ReplyDelete
  4. Not many guides/blogs mention the small lag in Beacon heals, so thank you.

    ReplyDelete
  5. This is a really good post! It's a topic we don't stop to think of much.

    There are a few occasions where I prefer to direct heal the tank too just for the added control, usually when the tank is taking really intense damage and every fraction of a second counts. I still do prefer to keep the Shambling Horror tank beaconned because of the holy light splash on the melee during infest, but our healing team composition usually gives me that luxury.

    ReplyDelete
  6. I don't get to heal raids much on my paladin anymore, but when I did, I had a habit of directly healing the tank if I was afraid they would die, even if they had Beacon on them. Once they were out of the danger zone, sure, go back to healing someone else and letting BoL dupe the heal, but I hated the idea of losing someone to that split second delay.

    ReplyDelete
  7. Thank you for this post, this is one of those things I probably 'knew' but didn't really KNOW, (especially since I'm very off-spec holy, I only do it when we need a 3rd healer, so, progression fights, when it matters that I don't suck too bad but I digress) and this probably explains why tanks have 'unexplicably' died on me before.

    ReplyDelete
  8. Ophelie - this is why I started off with my BoL on the Shambling tank. Since I was generally only doing 10m raiding, I depended on the 2nd healer to keep the raid alive in P1.

    Glad to know this information helped some folks out.

    ReplyDelete
  9. Am i missing something here.

    Even with two seconds lag response on beacon of light, assuming you're not talking about your very first HoL, your spam on the BoL'ed target will still be 1.2 seconds per received heal, just registered afterwards?

    1.00 Normal heal 1 1.20 Beacon heal 1
    2.20 Normal heal 2 2.40 Beacon heal 2
    3.40 Normal heal 3 4.00 Beacon heal 3
    5.00 Normal heal 4 5.20 Beacon heal 4
    6.20 Normal heal 5 6.40 Beacon heal 5
    7.40 Normal heal 6 8.00 Beacon heal 6

    Even though there is some lag with the received heal, during HoL spam, the timings of healing received every 1.2 seconds is the same. If you're implying there is more lag and it accumulates, you're saying that Beacon heals are lost?

    ReplyDelete
  10. I don't know if they're lost, and I'm sure that they're not stacking in a queue - otherwise we'd see 30 of them go off after a fight ended.

    I'll grab some log parses tonight if I can to 'prove' the theory. Here's what I 'know' though.

    I'm going to redo your chart above, since it has a little bit of error on it (the base is the same, just fat fingered a number I think). We're going to assume this is a HL spam situation, so Lights Grace, JotW is up, etc. Also going to assume a steady .2 sec lag.

    1.20 HL on MT, 1.4 BoL
    2.40 HL on MT, 2.6 BoL
    3.60 HL on MT, 3.8 BoL

    This is what you'd expect to see, which would show that yes, your heals are still at 1.2 on your BoL after the initial one goes out. Unfortunately this isn't the information that I'm seeing when I'm healing.

    This is what I think we're getting. Notice that each HL is cast 1.2 sec after each other, but the resulting BoL is landing 1.4 seconds later - even though the difference between the HL and the BOL is growing.

    1.2 HL, 1.4 BoL - .2 sec
    2.4 HL, 2.8 BoL - .4 sec
    3.6 HL, 4.2 BoL - .6 sec
    4.8 HL, 5.6 BoL - .8 sec
    6.0 HL, 7.0 BoL - 1 sec

    What we're seeing is a growing gap between when the HL lands and when the BoL lands, but the time between the BoL landing is remaining constant. Now I can't be sure, but it's almost like the system won't apply the new heal until the other has cleared the casting queue.

    This will require additional math and work.

    A very quick way to test this out would be to have 2 people strip their gear and then do a BoL with a Holy Shock and check the logs.

    I do know there is a lag time between the heal landing and being applied, I just don't know how it's working. More data will follow on Thursday when I have had a chance to run some log numbers.

    ReplyDelete

Note: Only a member of this blog may post a comment.