ww discussion ww doesn't work the way it used to. right now, it appears that a lot of people are either a) thinking it is the same as .09 and thus is bugged now, b) are not sure how it works, thus think it's bugged now, or c) just think it's bugged, period. In .09, ww worked like this: for x amount of ias on your weapon, you would get y amount of hits on a single target, based on formula that included range. It appears that there was a hard cap on hits at 6 regardless of range for a single wep, and 7 for using two weapons. Now, it is clearly different. From lurkerlounge, they state (and i feel that their assessment matches the game) that ww has changed to frame-type damage. the way i understand it is that over say 32 frames: aaabaaacaaabaaacaaabaaacaaabaaac each letter represents a frame. c's are chances to get hits. if you have enough ias, you get the b's. (very simplified, i know.) So, it appears that the range of the wep, the size of the monster, and the travel velocity of the ww all affect how many hits you can get. there is no guaranteed # of hits anymore. So, looking at it like this, it would reflect the results many people have been reporting about the "2 hit ww bug." i think it is very possible to consistently get only 2 hits on a mob if it is immoble, small, and with a short weapon. after some testing on my own, i have found that i can get 3 or more hits only if the monster is large, 4 or so on very large act bosses. So, this leads me to believe that further testing or mpq examination needs to be done. First, wep range needs to be tested. Perhaps it is possible to get 6 hits on a single mob with range 5 weps. Second, there may be further "breakpoints" instead of what we think we know. I have a -60 ias ribcracker, and a -65 ias ik maul, and the maul outperforms the ribcracker. Because ww is frame based now, perhaps the bps have changed as well. Third, I may have found a bug with ww travel velocity as well. it randomly speeds up, missing many mobs that are obviously in its range, with no change in my frw. this is a huge disadvantge for frame-based ww, and might be a true bug.