I remember a post somewhere in some thread that said when a mob is casting (or a player for that matter), they lose the ability to dodge, parry and block.

Lately this has been called in to question and I honestly can't find any support (or the post I read) other than personal undocumented observation for this aspect of casting a spell.

Anyone able to direct me to some empirical evidence to this being true or false?

I generally chalk any dodges/parries/misses up to lag causing my kick to land after the spell is completed, and thus I try to land my kicks earlier rather than later, but this isn't going to prove my point very well in a discussion.

The only time I've seen this is when a paladin puts his shield on his back to cast spells. He then loses his ability to block. That is being fixed next patch however.

We lose Parry / Block, but we can still dodge. Even when casting a non instant spell, you can still dodge or be missed, but it rules out Block and parry.

In reguard to a mob, i don't recall a mob blocking me. So i can't comment.

Mobs block fairly frequently... even magelike mobs will throw a block message from time to time.

http://elitistjerks.com/showthread.p...179#post331062

--

Finally found the post I was thinking of... how true is this?

I apologize in advance for bumping a very old topic - but the original poster had the same question a few of us did on IRC.

Can a shield bash/pummel/kick be dodged on a mob that is casting? I was convinced before he spoke up that I had plenty of dodged/parried shield bashes on casting mobs - but this guy seemed quite adamant despite people claiming otherwise. The above answers seem ambiguous in regards to mobs.

I just had a kick parried by a Fel Spark a few hours ago. Cast still got off and killed me. No SS, though ... had I known this topic existed I would have taken one. Actually I didn't even know such mechanics were in question.

Since the question came up earlier, I've been following it very closely. Every time I see a dodge/parry on Kick I've been late on the interrupt.

Unfortunately, "late on the interrupt" quite often means it should have been in time. But given my experience, it's about at the same time left on spells (.4 seconds left or less) that I will also get an "Interrupt - X" message while the spell still casts.

It seems latency+ui lag+human delay really makes a difference in that last half a second.

Happens for me all the time as well with approximately the same (or frequently lower) latency, I just know by now that if I haven't interrupted the spell before it's 0.5 seconds before it's completed I might as well not bother interrupting it at all because it'll still cast despite either getting an interrupt message, or seeing the stun land, or seeing my Arcane Torrent land, etc.