Instant Attacks

Aggression · 10/13/06, 6:15 PM

I've noticed, a long time ago, that whenever my MS/Overpower/Hamstring follow up on a white/heroic strike miss/parry/dodge that the MS/ect. copy it exactly. I used to just chalk it up to low hit %, but now sitting at 4% and the margin beeing 5% for 2h, I'm highly doubtful when I charge and my white hit misses and my Hamstring does as well that it's low hit%, or even when a mage gets a lucky dodge on my white hit and my MS (that hit at the exact same time as the white hit) gets dodged as well.
I haven't done any theory craft or parsing on the subject (becuase I don't know the nuances or exactness of it). But more or less just wanted to know if any other warrior/rogue has noticed this at all.

Antiarc · 10/13/06, 6:20 PM

I've noticed it, but only anecdotally. I suspect I tend to notice it more when my stuff doesn't land, so I'd be tempted to say that it's just a string of bad luck, and we don't notice when it doesn't perform as you just described.

Malan · 10/13/06, 7:35 PM

Ask any warlock how often their fear gets broken early - "oh damn man, all the time". A rogue on how often sap breaks early - "jeez it NEVER lasts full time", a shaman on how often earthshock gets resisted - "dammit I can never land it when i need it".
Just like Antiarc said... we just notice stuff like that more often when it doesn't go our way. Humans look for patterns in everything.

Tzeni · 10/13/06, 7:42 PM

Originally Posted by Aggression

I've noticed, a long time ago, that whenever my MS/Overpower/Hamstring follow up on a white/heroic strike miss/parry/dodge that the MS/ect. copy it exactly. I used to just chalk it up to low hit %, but now sitting at 4% and the margin beeing 5% for 2h, I'm highly doubtful when I charge and my white hit misses and my Hamstring does as well that it's low hit%, or even when a mage gets a lucky dodge on my white hit and my MS (that hit at the exact same time as the white hit) gets dodged as well.
I haven't done any theory craft or parsing on the subject (becuase I don't know the nuances or exactness of it). But more or less just wanted to know if any other warrior/rogue has noticed this at all.

Well, for one thing, no matter how much +hit you get, you'll still get dodged 5% and parried by classes that can parry.

Cryect · 10/13/06, 7:47 PM

Originally Posted by Tzeni

Well, for one thing, no matter how much +hit you get, you'll still get dodged 5% and parried by classes that can parry.

Parry is easy to fix, stand behind whatever.

Antiarc · 10/13/06, 7:48 PM

Originally Posted by Cryect

Originally Posted by Tzeni

Well, for one thing, no matter how much +hit you get, you'll still get dodged 5% and parried by classes that can parry.

Parry is easy to fix, stand behind whatever.

Joenoob parried your Backstab.

:/

(I know it doesn't happen most of the time, but I'm being a smart ass.)

Cryect · 10/13/06, 7:54 PM

Hehe yeah I've seen those things happen before but supposedly its not supposed to. Prolly some borderline case between what it calls front & back. Prolly only checks client side are you behind them or something then later checks for the parry so positioning could change.

Aggression · 10/13/06, 11:16 PM

I suppose it's something you really try to notice, but it does seem odd that they follow the same pattern with the miss/parry/dodge sooooo often.

Vosk · 10/14/06, 7:23 AM

I always want to leap off a bridge when ravage (druid ambush) is parried. Mind boggling!

Teza · 10/14/06, 10:28 AM

Mutilate seems interesting, but need a bit more testing before giving a final opinion.

TheCutlery · 10/14/06, 11:45 AM

Originally Posted by Cryect

Hehe yeah I've seen those things happen before but supposedly its not supposed to. Prolly some borderline case between what it calls front & back. Prolly only checks client side are you behind them or something then later checks for the parry so positioning could change.

I believe I saw this actually answered awhile back on the WoW forums, a CM said that it doesn't check position when you're within 0.5 yards or somesuch to make the game more playable in lag. The side effect of course is parried backstabs and such.

Richiewolk · 10/14/06, 4:15 PM

Originally Posted by TheCutlery

Originally Posted by Cryect

Hehe yeah I've seen those things happen before but supposedly its not supposed to. Prolly some borderline case between what it calls front & back. Prolly only checks client side are you behind them or something then later checks for the parry so positioning could change.

I believe I saw this actually answered awhile back on the WoW forums, a CM said that it doesn't check position when you're within 0.5 yards or somesuch to make the game more playable in lag. The side effect of course is parried backstabs and such.

Now, is there a way to force the client to ignore direction checks, or increase the radius of checking?

Cryect · 10/14/06, 5:09 PM

Originally Posted by Richiewolk

Originally Posted by TheCutlery

Originally Posted by Cryect

Hehe yeah I've seen those things happen before but supposedly its not supposed to. Prolly some borderline case between what it calls front & back. Prolly only checks client side are you behind them or something then later checks for the parry so positioning could change.

I believe I saw this actually answered awhile back on the WoW forums, a CM said that it doesn't check position when you're within 0.5 yards or somesuch to make the game more playable in lag. The side effect of course is parried backstabs and such.

Now, is there a way to force the client to ignore direction checks, or increase the radius of checking?

Not without 3rd party programs changing stuff or doing packet replacement. Which is interesting from how does WoW actually work but not much in the way of usefulness for real legit gameplay.

Edit: Also pretty sure the 0.5 yds he is talking about is done server side so it doesn't seem like you are behind the mob on your screen but according to the server in front of.