Unleash

That just doesnt make any sense to me. I watch my combat logs quite often and when things go wrong, im sitting there scrolling through it to see exactly what went down. I have never seen a "failed to dispell" or anything besides a successful spellsteal or a resisted one.

Screenshot it next time?

 

◊ Praetorian

We've never seen it before either.

Here's the combat log:

8/11 20:37:45.079 Stion casts Spellsteal on High Nethermancer Zerevor.
8/11 20:37:45.130 Stion fails to dispel High Nethermancer Zerevor's Dampen Magic.
8/11 20:37:48.622 High Nethermancer Zerevor's Arcane Bolt hits Stion for 12997 Arcane damage. (1274 absorbed)

Next attempt:

8/11 20:44:15.452 Stion casts Spellsteal on High Nethermancer Zerevor.
8/11 20:44:15.670 Stion fails to dispel High Nethermancer Zerevor's Dampen Magic.

And then we had this happen on the third pull:

8/11 20:50:26.334 Stion casts Spellsteal on High Nethermancer Zerevor.
8/11 20:50:26.651 High Nethermancer Zerevor steals Stion's Dampen Magic.
8/11 20:50:28.354 High Nethermancer Zerevor's Arcane Bolt hits Stion for 13527 Arcane damage.

(wtf, 1.5 seconds later and it still hasn't registered?)

And then on the fourth pull it worked normally.

 

Trouble

We had that happen once when we were learning it last week. We couldn't figure out what the hell it meant. Also one time the combat log said that Zerevor Spellstole the shield back instantly once it was stolen??? Many people in the raid saw this, the combat log definitely said exactly that. Both these things happened on the initial pull, never during the fight. Our only explanation was some sort of weird combat log error that was caused by latency or....something. I really don't know. The timing on the initial pull is pretty close and mages are spamming the button as they run in so maybe it's some weird anomaly having to do with range and latency.

Edit: I see you had the same thing happen with Zerevor stealing the shield back. That is just too weird.

 

Dots

Well, it says Zerevor stole it, for whatever reason.

The only issues with Spellsteal that I know of are Gathios' resistance aura and Malande's shield thing which makes Zerevor immune to Spellsteal. But I am no mage.

I assume you have your mage initiate the pull?

 

◊ Praetorian

No, that's the syntax. It's a syntax bug. If X successfully spellsteals Y's buff, it'll say Y stole X's buff in the log.

(And yes, the mage pulls.)

 

Unleash

I have seen this one, did it to me once. Im not sure what/how this happens.

As far as failed to dispel, it must be some sort of combat log bug and is the same as "resist" being dispel is generally what a spellsteal is doing is dispelling it from High nethermancer, but just gives the mage the buff. So I honestly couldnt tell you. I havent witnessed the "failed to dispell", but I have seen the one above.

 

Renlin

I remember trying to use cure disease (the lowbie priest version of abolish) to try to save mana costs back at 60, and getting the 'fail to dispel' thing a lot. My guess is that WoW has something in place to make it harder for low level players/spells to remove significantly higher level debuffs, similar to resists except you can't really resist a friendly spell so they had to call it something else. I've also had this happen on a low level shaman trying to purge high level targets, which is infernally annoying because most of the purges are getting 'resisted' to begin with so I basically have to get a lucky roll twice.

Why this mechanic is appearing when everyone is level 70 and using standard spells, I have no idea.

 

◊ Gwaihir

Tranq shot did this too. With maximum plus hit it would always hit, but the hunter got the same You fail to dispel (random two headed dod monster's) Frenzy.

 

greatapoc

I've been seeing "fails" on Spellsteal since tanking Krosh in Gruul's Lair. It's pretty much some random secondary resist. If you've ever gone against a warlock with Contagion and tried dispelling their dots you'll see a ton of fails there too, it's certainly nothing new.

 

Whitemane

This happened ages ago, but didn't they mess with whether or not the level check was switched between caster or spell level? It doesn't make any sense for spellsteal however, since the caster and spell is level 70.

 

Plea

I occasionally fail to dispel too, mostly in pvp. Mana gone, on global cooldown, debuff still there. Don't know what its combat log entry was, always thought it was about some wierd silent resolve shadow spec issue.

I never regarded cure disease a lowbie version of abolish though. You cannot hammer the abolish button to cure an incoming disease, the one from bog giants is easier with cure too; abolish sucks there.

 

Skulli

No, abolish will instantly remove the disease and then try to remove another disease every 5sec.

 

Jebraltar

I've seen "Failed to Dispel" quite a bit when trying to cleanse dots off friendly targets in PvP and occasionally in PvE as well. Perhaps the Illidari Council specs into Stoicism for PvP...

 

heel

"Failed to dispel" has been around for a long time. IIRC, when dispelling, it's like the debuff is its own entity and you're trying to cast an offensive spell against it - there's a resist check.

 

◊ Praetorian

Yep, I've seen it as well in general, just never considered the implications of the mechanic before on Council, and never seen it on Council. After learning pulls and a few weeks of kills, having it happen twice in a row on our first two pulls made me wonder whether something had changed. I guess we just got really, really unlucky.

 

◊ Quigon

Think of it as the caster form of quintuple parries.
We have seen this once on maulgar - wiped us. But instead of acknowledging it we blamed the warlock, laughed at him, and moved on. Usually the best course of action is to mock the caster.

 

Clandestine

I would say really lucky to never get it before. We got it like three pulls in a row when we learned Council. That was fun.

 

Klorox

bumping this although it wasn't as bad as Quigon mentioned:

ImageShack - Hosting :: wowscrnshot081307223123ek8.jpg

22570 damage with no real way to counter it. Although, that is our gnome DPS warrior willing to use himself as a shield next time it happens. He turned to cast parasite turned around and destroyed me. I didn't even get a chance to blink before he killed me. I did dodge one attack I guess lucky me. Only happened once tonight.

I understand why the parry mechanic is there, but some of these bosses put you in a situation where you can't survive. I suppose with better positioning we could minimize it. Hopefully someone from Blizzard will look at this and see that the parry mechanic isn't functioning correctly. I can live with killing myself, but I can't see how the mechanic is functioning correctly when bosses turn to cast some other ability and it ends up killing the tank.

 

Dots

While you are totally right about the parry mechanic, the high melee hits up to 8712 indicate that there was probably some buff or debuff missing. With Demo Shout and Ironshield, you should have (barely) survived this.

 

Sycn

A little warning to other guilds. If you are in the process of wiping and have Illidan at a low % I suggest not trying to finish him off because if your remaining members die during the little exchange between Illidan and Maiev you lose the tap and any loot rights. On top of that the Raid Specialists are not allowed to respawn him for you.

 

◊ Quigon

Surely you would get the loot for this mistake.

 

Dots

We had this happen as well and didn't get anything. I think the last thing they told us was that they will look at it once more, but that was like 3 or 4 weeks ago. The problem is that there is no killing blow and nobody is left alive when Illidan actually dies. We asked for a shaman to ankh up during the death animation, but they were all used. No idea if that would help.

Just to compare, we did get loot on Azgalor before when Thrall died to the RoF tick just a second after the kill, which made Azgalor's corpse disappear. That time we clearly had the killing blow though.

 

Sycn

We actually had a shaman ankh during the scripted event(after our last player had died), sadly you can't target Illidan once its started and healing himself to full did nothing to retap him to our raid. The problem like Dots has said is there is no killing blow from a player since the scripted event has Maiev kill him for you. The line "Illidan Stormrage has died." does indeed show up in the combat log but, the Raid Specialist stated they needed a killing blow line to distribute loot to the raid group.

 

◊ Quigon

How is this different than bugs with Vashj? I just don't see how the GM's can possibly let this one go - surely someone killed him, and it wasn't Maiev. Its kind of a shame that the "raid specialists" are so dumb as not to break protocol on something so obvious. They really need a death log to make something happen? So silly.

 

Dots

Yea, it is silly. The Vashj bug was Method being unable to reach her corpse? They surely had a killing blow. I guess it is just an issue because death events are not covered in the rules. Not sure it is possible, but the same thing could probably happen on Archimonde, if the last people in your raid die and whisps finish him off.

Either way, we can only blame ourselves. That wipe was really stupid.