Cruel Flurry (Maelstrom DW) should apply the WD bonus to Flurry as well

Avran_Sylt · July 22

Spammables in general have kinda been powercrept by Fatecarver, so I don't think this change would be too much an issue (though... PvP tanks leveraging the extra 1.6K WD on a spammable could be).

Kaelthorn_Nightbloom · July 22

I think it worked in the past but they nerfed it because the damage was outside the bounds of what should be allowed for a spammable. It was way more than say Draugrkin + Force Pulse. Like 2-3x more damage. There were some screenshots showing someone using Flurry in PvP and each tick was hitting for 2-3k. So like 12-15k dps with crits just from a spammable.

Anyways, that's why it doesn't work and I don't see them reverting it. Personally I LOVE these types of mechanics where you can find crazy ways to scale damage. Draugrkin + tons of little DoTs w/ Force Pulse, bash, status effects, etc. is so much fun and those types of builds absolutely destroy the mag/stam of anyone trying to block heal in PvP.

Avran_Sylt · July 22

SkaraMinoc wrote: »

I think it worked in the past but they nerfed it because the damage was outside the bounds of what should be allowed for a spammable. It was way more than say Draugrkin + Force Pulse. Like 2-3x more damage. There were some screenshots showing someone using Flurry in PvP and each tick was hitting for 2-3k. So like 12-15k dps with crits just from a spammable.

Anyways, that's why it doesn't work and I don't see them reverting it. Personally I LOVE these types of mechanics where you can find crazy ways to scale damage. Draugrkin + tons of little DoTs w/ Force Pulse, bash, status effects, etc. is so much fun and those types of builds absolutely destroy the mag/stam of anyone trying to block heal in PvP.

Yeah...

Trying to create a PvE build with Flurry, but it just doesn't work out whatsoever.

Really hating how much the design of fatecarver curbstomps every other spammable in the game in PvE while preventing other spammables being brought up since in PvP it's constrained by the buildup/bash making its fullpower use not quite feasible.

virtus753 · July 22

It originally worked with Flurry because Flurry was a DoT. Then they changed Flurry to direct.

They also later put in a hidden restriction on the set that it does not work on channeled DoTs, so even if Flurry were still a DoT the set would not buff it.