You realize power burns don't always do damage on a 1:1 ratio, right?
Pretty sure that with this one you just take 100 damage for every point of rage you have when it hits, before DS/IDS modifier. So for a prot tank, 8460 is the max possible hit from the power burn component. Browsing some WWS bears this out. You'll see 8460 as the max in logs often.
That fits perfectly with my combat log as well.
I never thought I could be too slow at getting rid of rage until I met this mob.
No, more like something your tank has to be aware of. Burn your rage or you'll get burned. (TM)
Run BigWigz, call out timers on vent. We use anything that can dispell to remove the Rune Shield ASAP (Dispel/Purge/Spellsteal), so kicks aren't missed and the roation potentially skewed. All of our rogues have Assist and use a macro for kick
/cast Kick(Rank 5)
/rw Kick 1 Done! X (Player next in order) next!
It's generic and gets the point across, we also use a mod that confirms if our kick interrupts a spell, but thats guild-coded and ours =D
Either way, watch BW timers for Deaden, don't kick it, don't miss shock, and dont suck!
We're having a couple of locks summon felhunters at the end of phase 1 and putting on autocast devour magic for rune shield, sure its nice if a mage can get the shields but shaving off a few split seconds of human error and server to client delay (something pets dont have) can make all the difference on stopping spirit shocks that may have been casted under rune shield. You can also resummon (preferably with fel dom) a new felhunter to refresh its mana bar if this phase drags on slightly longer than you'd like.
Thanks! Should help me do better and be less likely to get killed next time time through, like I said, we didn't really spend a ton of time in P3 learning so I didn't remember the name, and I am not personally proficient at searching thottbot by mob name for skills.
Yeah I usually look up something myself if I'm curious on it's functionality, just never really needed to for the scream because it wasn't causing an issue, just something nice to know. I'm sure someone /combat logged the fight I just didn't personally and I didn't ask cause I was at work.
If you have an exact Soul Scream timer for Big Wigs or whatever other boss mod, dropping rage to stance switch might help. Otherwise, this seems to be too much of a hassle.
By the way, if anyone wants to try this, you can go def > def to drop rage without actually leaving defensive stance by making a hotkey for it from your spellbook.
Dont even need to shift out of def stance to drop a full rage bar. If you have your stances macroed and hit the same stance you are currently in, it will function just like a normal stance change.
Regardless, Reliquary stands as a great test to see if your rogues are up to snuff for Tier 6 content. Keeping good DPS cycles up and putting out the deepz is great, but doing this while keeping to a kick rotation, not missing a shock, and NOT KICKING DEADEN, is the difference between a Tier 5 and Tier 6 quality player.
I generally tend to agree with this. It's not hard. However, after yelling at interrupters for some dumb wipes last night, I went back and looked at the combat logs closely.
What do you do about this?
7/10 01:08:18.970 Essence of Desire begins to cast Spirit Shock.
7/10 01:08:18.970 Essence of Desire gains Rune Shield.
7/10 01:08:19.405 Essence of Desire's Rune Shield is removed by Shabadu's Purge.
7/10 01:08:19.759 Wodin interrupts Essence of Desire's Spirit Shock.
7/10 01:08:19.781 Wodin's Kick hits Essence of Desire for 170.
7/10 01:08:19.998 Essence of Desire's Spirit Shock hits Paches for 8082 Arcane damage.
Or this:
7/10 00:31:54.724 Essence of Desire begins to cast Spirit Shock.
7/10 00:31:54.724 Essence of Desire gains Rune Shield.
7/10 00:31:55.143 Sarthun casts Devour Magic on Essence of Desire.
7/10 00:31:55.173 Essence of Desire's Rune Shield is removed by Sarthun's Devour Magic.
7/10 00:31:55.345 Khazal interrupts Essence of Desire's Spirit Shock.
7/10 00:31:55.547 Chocula interrupts Essence of Desire's Spirit Shock.
7/10 00:31:55.611 Essence of Desire's Spirit Shock hits Paches for 8229 Arcane damage.
To me that looks like the RS purge isn't registering fast enough to properly remove the interrupt-immunity from Essence of Desire. I can't exactly fault my players for having 500ms reaction times, latency considered, on things like purge and kick/pummel. Is it just the combat log being misleading and the players were just plain slow, or is it something others have experienced too?
To me that looks like the RS purge isn't registering fast enough to properly remove the interrupt-immunity from Essence of Desire. I can't exactly fault my players for having 500ms reaction times, latency considered, on things like purge and kick/pummel. Is it just the combat log being misleading and the players were just plain slow, or is it something others have experienced too?
I haven't done EoS, but this is an issue I have experienced before as well. If you attempt to interrupt a spell too close to when the cast goes off, there can be lag between client and server and the interrupt won't register and the mob will cast successfully. This happened to me on a Kael attempt, where I kicked a pyroblast and it came up as an "interrupt" in my combat log, however the pryo still went off. I've also had this issue on Raise Dead from Shadowy Necros.
I don't think it is your combat log being misleading, because if it was an issue with a purge not being registered quick enough, then it would say Immune to the kick and Absorb for the damage. It's kind of lame that the timing gets that tight for a 1 second cast with the EoD's buff needing to be removed as well, but I would blame it on latency.
Can't say I'm offering a solution, but that's probably very closely related to stuff like mobs/players parrying backstabs, heals landing and consuming buffs like Nature's Swiftness yet not 'landing' in time before a tank dies, etc. Short discussion about about it came up on #elitistjerks a while back.
It seems there's a short delay between when an action is checked for validity and when its 'payload' is delivered. Another hilarious instance -> http://www.mediafire.com/?ftbvxvjzxbt - although this one is apparently being fixed in a patch soon, probably by more checking before the Mangle debuff is applied.
And no, it has nothing to do with client-server latency. It's just as likely to occur at 50ms as it is at 900ms. (Believe me, for an Oceanic guild learning Patchwerk back then, you'd think that with 600ms latencies on a significant fraction of our healers the problem of "heal lands, tank dies" would have been very pronounced if it was client-server latency. It wasn't) My guesswork is that it's all server-side timing inconsistency. If anything, it'd be related to how busy the server is at the time.
Not looking forward to that, in any case. Dispel and interrupt on a 1-second cast when most of us run at latencies half that long... doh. :/
I've had issues interrupting spells before, but it supports the theory that theres some serious syncing issues. If its after the last .2 or .3 seconds left of the cast time I almost always get "Spell has been interrupted" and then it still goes through and hits. Its actually pretty annoying, if it wasn't for that bug it would be significantly easier to interrupt 1.5 second casts while on global cooldown.
It seems to be a larger issue on faster casting spells for me as generally with things that have 3+ second casts you can really wait till the last moment to interrupt without seeing that glitch.
That is pretty rough Praetorian - sounds like a tuning mechanic. But as it is usually on these end bosses, not a lot is tweaked, and annoyances are generally considered part of the acceptable limit that the few guilds that reach the encounter will tolerate anyway - and chalked up to "difficulty."
The timers on that are a bit harrowing considering so many of us play with 200-300 ms latency. Some of this is tested in-house on LAN servers perhaps?
Praetorian : we had the same issue, we could get to p3 but like 1 out of 3 p2 tries because of syncing issues. A mage respecced 41 arcane yesterday and put slow just before the shield, it works very well. It's only .1 sec more or so on the casttime but it seemed enough for our rogues to always interrupt shocks, even when synced with a shield. However, the slow bot mage obvisouly provided a bit less dps than the others and it made our phases 2 harder. We reached the 0 mana timer with essence @ 6% on our kill, but managed to do it, thanks to inner focus dispel for the rune shield ;o
We wiped yesterday almost whole night on the same issue: the shock after a rune shield simply got through way too often, and going to p3 with dead people was not working. We had 2 fel hunters auto-devouring it, and we even added 4 extra interrupters that were out of the normal rotation for it. In the end we simply assumed that at least one of the shocks will go through and MT will be confused, and adjusted our tactic based on it a bit. We could not test this though since on our kill try, none of the shocks went through, every Deaden was successful, and we hit 0 mana just when p2 ended. P3 was still brutal, we were maybe 6 seconds away from total wipe when it died.
If you are using Fel Hunters, have a lock resummon it before they themselves run out of mana, so the pet get's a new manabar and can continue dispelling after the raid is oom.
Lightwell object increased in size to make it easier to click.
We just assume that one or two interrupts aren't going to get through in the course of the fight, and I offtank it in DPS gear. As long as I don't get it just as the deaden happens, I'm fine. We have had a few DPS issues using this though, as I like to keep a slight barrier between me and the tank so others have to be careful on threat. Inner focus dispel is win.
We just assume that one or two interrupts aren't going to get through in the course of the fight, and I offtank it in DPS gear. As long as I don't get it just as the deaden happens, I'm fine. We have had a few DPS issues using this though, as I like to keep a slight barrier between me and the tank so others have to be careful on threat. Inner focus dispel is win.
Yeah this is exactly what we ended up doing, with the same consequences. Our interrupters got every normal shock, but missed some of the shield+shock combos, so we had a bear #2 on aggro, but that meant that other melee had to hold back a bit (or if rogues blew vanish in p2, then they'd be fucked in p3), which had us coming up a bit short on p2 DPS a lot of the time. It works, as noted above, but it's a bit clumsy and I just wanted to make sure we weren't missing something.
If I could make one suggestion for changing RoS, I think the fight is close to perfect, but I'd give RoS a very very short (like 0.5sec or 1.0sec) global cooldown after casting Rune Shield, so that he can't Shield and instantly start an 0.8sec Shock cast in the same hundredth of a second. I guess this would be a "nerf" but honestly interrupting something in a ~0.3sec window between the shield dispel and spell completion doesn't really strike me as a reasonable design element. I'm just thankful that our rogues mostly have good connections. If we had interrupters with 300ms latency, it'd be like a repeat of Thaddius on the old hardware. Not fun.
I kind of like that 'feature' that causes you to basically be forced to eat a Shock now and then.. it requires you to have an offtank basically, since you're gonna have an extra tank or two in the raid anyway, it gives them something to do.
07/03/07, 12:23 PM
Similar Threads
