WhirlWind - Why no Procs? Why still AS?

“% chance to cast X on strike”
WhirlWinds 50X times
DiddlySquat Happens
Uhhhhh, pretty sure were striking the monsters…

Also why is whirlwind dependent on weapon swing speed.
We’re not swinging it…
It should be dependent on run speed, as it makes sense thematically, but would also allow the skill to be useful for once with the ability to use 80% of the other weapons we never do.

1 Like

The real problem is that Whirlwind is actualy bugged.

In D2R, Whirlwind does not seems to register the first few frame attacks.
That means most hits dont hit. For example a short whirlwind does nothing to an ennemy.

Bug report : [2.4 Patch] WW Barbarian is still Bugged & Unplayable

1 Like

That too, but no ability to use your item procs when hitting with melee weapon, or swing speed is even more ridiculous than an old bug.

1 Like

Maybe if Whilrwind did not take into account attack speed at all, all those Two-handed weapons can get a use - since they are too slow for current WW function.

Having a new mechanic - depending on run (or stamina maybe?) speed - seems like a fun idea to build upon.

I never thought about this… if multishot, zeal, etc are casting, why isn’t WW?

I support ww casting spells.

1 Like

I think it’s a hold over from when WW always attacked at crazy high frame rates and hadn’t had its damage gutted yet to balance it since the amount of procs made it too strong.

Then they fixed the bug where 1 point in mastery gave you 100% Deadly Strike, fixed the eth bug that made you basically ignore target defense, made WW start with negative damage and use only weapon speed to determine hit checks and nerfed it into the ground and stopped development on D2 before it could get another pass.

The bug has referring to is new to D2R afaik.