This has gotten me killed when self-healing versus mobs with spell interrupts a couple times. At first I thought it was some sort of lag. Then I asked around and everyone looked at me funny, so I just kept my mouth shut. I'm glad to find out it's a real issue other people are having. It's annoying as all hell, that's for sure.

Here's hoping today's patch fixed it.

On that note, damage that is reflected should NOT delay casting.

Should not by your standards or should not as in game rule? I certainly think it should be a game rule, since its pretty frustrating not being able to cast if people have reflective shield on as a lock.

Game rule. At the very least, the damage reflected should have a similar affect as when it is not reflected. Thus, DoTs do not cause spell interruption and should not do so when reflected.

The shield lasts for like 5 seconds, give us a break.

It doesn't matter... DoT damage doesn't cause spell interruption normally, so why should reflected DoT damage cause interruption? Especially if you have triple-Dotted someone... you'll eat 6-7 interruptions in those five seconds, so your next spell will effectively take 3 seconds longer to cast regardless of cast time.

I'm going to side with the warlocks on this one, getting delayed by chain reflects on dot damage sounds like it wasn't intended. Obviously you can work around it, but if you consider it as an unintended behaviour, you shouldn't have to deal with it, it should just be fixed. Say someone finds a way to cast Curse of Recklessness on friendlies. Now you have people immune to fear running around, would you be ok with that because ultimately, nothing forces you to use fears to beat people? Now, to find out if it's actually intended is another story.

As for the whole castbar issue, anyone noticed it after the patch? Was it fixed?

/duel

Except it doesn't stay when the duel ends, don't think it stays if you run out of the area either.

It's not the DoT that's reflected, it's the damage the DoT does that's refelcted. That the DoT happens not to cause interruption doesn't mean that the reflected damage shouldn't. It's a damage reflect, not a spell reflect.

But this is all speculation, we have no insights whatsoever into the minds of those who make up these abilities, and will have to trust that its current mechanics are as they're supposed to be... for what that's worth. Damage reflects have always been abit iffy. I remember back in the days you could crit somebody with a reflector on and it would reflect the spell damage to me, but burn them for ignite, or reflect back to me, but procc impact on them without doing damage. Stuff like that.

Hmm, really ? It's been a while, but i remember hunters using that trick so kill Silithus demon.

Yea, the hunters would keep the duel active for the duration of the kill, and if CoR wore off during the duel, the warlock would recast (and since it's a debuff, it wouldn't count as gaining a new buff and make the demon angry).

With CoR I meant casting it in BGs or arenas tho, where duels are not available. And it was just a random idea. What I don't like with reflect shield is it looks like Smite(or at least I think it does, there's not that many disc spec priests in pickup bgs ^^) so I always think I'm under heavy combined fire, or facing a holy priest with the instant smite talent, when in fact I'm taking -70dmg or whatever. They should'nt have bothered showing a special effect, or only on the person with the reflective shield(maybe make a different kind of shield if it's reflective).

I guess the bug is fixed tho, no one reported it since 2.0.3?

Like how? You DoT up a bunch of people. They get shielded. Now, every 0.2 seconds or so, you're getting interrupted. As an Affliction 'lock, you have two instant spells unless Nightfall procs... both are situational and have moderate to long cooldowns. I find it hard to believe you haven't noticed your inability to get a 1.5s cast Fear off due to this issue.

Perfect example, a crew of 6-7 guys is running the flag in WSG. Warlocks dot up everyone and then cast Unstable Affliction on them. Now my one and only goal is to dispel my teammates and keep them alive, EXCEPT I CAN'T EVEN GET OFF A DISPEL because of unstable affliction on every single player.

Completely off-topic, but I've been wondering, Unstable Affliction is magic, and Felhunters can Devour Magic every 8s or so. Is it feasible to have a warlock's felhunter running around removing Unstable Affliction? At 8s each it's not good against a lot of targets, but on a couple it avoids silencing/hurting any players, and the Felhunter even gets a small heal off each devour.

I'll let people in on a pseudo-secret. I'm not sure if this is due to resists (don't see anything in the combat log at least) but the 10 or so times that I've had my felhunter devour UA it has not done ANYTHING to the felhunter. No silence, no damage.

If reflect shield will stop causing spell interruption, I'll let you guys have a felhunter that takes damage from UA :P

Yeah, I didn't notice it at all last night. Very happy :)

Don't do that, then. In any case, we have CoA (though I prefer CoT), Corruption and Siphon life, though you really should open with UA. Just UA 'till you get cast interruptions then spam all your three instant cast DoTs on eveything else within range till you run out of mana, then go take a leaf from one of the huts.

Anyway, on the topic at hand, cast bar issues seem gone now. Did a bunch og AoE all over stratholme and didn't notice it once.

What I did, however, notice was the targeted AoE bug. That has to be some of the worst, most annoying shit ever encountered in this game, and combined with the water elemental lockups means that my 41p talent doesn't do anything like 25% of the time. Aaaaaagh!