Can't hit certian monsters

[Taem]

Heiho,

there's somewhere a *.gif around with a table of NextHitDelay skills.

I once copied these player related skills out aof that:

Code:

f    Skill
4      ama/MultipleShot
4      ama/Strafe
4      ama/LightningStrike
25      asn/ShockField
4      asn/ShockWave
25      asn/BladeSentinel
4      asn/WakeofFire
4      asn/ClawsofThunder
4      asn/PhoenixStrike
6      barb/WarCry
4      barb/BattleCry
25      druid/Twister
25      druid/Tornado
10      druid/Volcano
4      nec/PoisonNova*
4      sorc/ChainLightning
4      sorc/Nova
4      sorc/Frostnova

* PN sets the NHD every 4frames, with 4frames pause

a) Maybe you use something with PN triggers?

B) Or do you use a long range weapon, so you're maybe victim of monsters too near for your weapon range.

c) Or you are victim of the recoded graphics output. If you get hit, the server sometimes knows you are, but the graphics output doesn't

c) is much for sure true along with the D/A/E skills of the Amazon along with Fend and other Skills (but most disturbing with Fend), I'm not sure, if the blocking animation with a shield or the gethit animation cause similar effects.
[right][snapback]57946[/snapback][/right]

Very interesting! My paladin uses two Carrion Wind rings giving him 20% Poison Nova and 16% Twister. I see those two spells going off all the time because I have a 5 FPS zeal. Perhaps this is what the problem is?

That seems most logical, however the bug I noticed was when a Valk attacked a target and did some action (missed, hit, sent the monster into a stun-recovery, I really don't know what she did), that I could no longer hit that monster for a couple seconds. I was not the only one who could not hit that monster. No other melee characters or archers could hit the monster, but any spell could hit the monster. This happened so to me so many times in small games of three people (total), that I figured it was a bug everyone say. I guess if you play in large groups or use skills that act like spells, you will never see this bug.