05-24-2004, 10:04 PM
I don't know people if you didn't have any problems with fury, but I do and it's so terribly annoying that I would kick some Blizzard butt everytime I see that miserable combat performance of my druid!
You can notice it yet in nightmare but its totaly terrible when you start hell!
I am talking about unbelievable frequency of misses when furying.
I think that's the same bug as in amazon's fend and paladin's zeal (not tested zeal). Common situation:
I encounter 4zombies and start fury. First I hit most of them (I have chance to hit about 80%), but in the next 5hits I often hit nothing! Then I continue fury and I hit about 1 from 4 attacks! This is worst when I hold my mouse over one monster. It can be compensated a little when I target different monster each 5attacks. But its not the end of all bad! It happens when I attack only one monster too! I only hear fast swish but my druid hits nothing! The slow skeleton just leisurely recovers from first (long ago) hit and walks away, while my werewolf druid madly tries to hit him! :wacko: I depend on a life steal from feral rage and when I don't hit any monster for several seconds, I can be dead. Monsters often kill me just because program decided, that now I will not hit anything despite my 4500ar and 80%chance to hit (hell act1) and they just slowly thrust out their bony hands and kill me at ease while I can go mad furying :( I cannot imagine how bad it will (if I manage to get there) be in the 5.act when I meet those bulls with axes (blood,death,moon lords) who do not wait a second to hit.
Tha strange thing is that I didn't see this while killing nigthmare cows (chance to hit 92%)...
I am sure this is a bug because I simply would hit monsters much more often with my AR.
I have the steeldriver martel de fer (made exceptional in a horadric cube) which is very fast.
Sometimes I think a feral rage is bugged too, because sometimes I hit a monster only every second attack. Maybe a program must wait till the stun recovery ends or whatever...
I hoped Blizzard will fix this (and a similar but yet much worse amazon fend bug) in the 1.10, but it didn't happen.
I don't understand someone didn't complain about it more, but I know that some people knows about this...
You can notice it yet in nightmare but its totaly terrible when you start hell!
I am talking about unbelievable frequency of misses when furying.
I think that's the same bug as in amazon's fend and paladin's zeal (not tested zeal). Common situation:
I encounter 4zombies and start fury. First I hit most of them (I have chance to hit about 80%), but in the next 5hits I often hit nothing! Then I continue fury and I hit about 1 from 4 attacks! This is worst when I hold my mouse over one monster. It can be compensated a little when I target different monster each 5attacks. But its not the end of all bad! It happens when I attack only one monster too! I only hear fast swish but my druid hits nothing! The slow skeleton just leisurely recovers from first (long ago) hit and walks away, while my werewolf druid madly tries to hit him! :wacko: I depend on a life steal from feral rage and when I don't hit any monster for several seconds, I can be dead. Monsters often kill me just because program decided, that now I will not hit anything despite my 4500ar and 80%chance to hit (hell act1) and they just slowly thrust out their bony hands and kill me at ease while I can go mad furying :( I cannot imagine how bad it will (if I manage to get there) be in the 5.act when I meet those bulls with axes (blood,death,moon lords) who do not wait a second to hit.
Tha strange thing is that I didn't see this while killing nigthmare cows (chance to hit 92%)...
I am sure this is a bug because I simply would hit monsters much more often with my AR.
I have the steeldriver martel de fer (made exceptional in a horadric cube) which is very fast.
Sometimes I think a feral rage is bugged too, because sometimes I hit a monster only every second attack. Maybe a program must wait till the stun recovery ends or whatever...
I hoped Blizzard will fix this (and a similar but yet much worse amazon fend bug) in the 1.10, but it didn't happen.
I don't understand someone didn't complain about it more, but I know that some people knows about this...