Twisted Sword Raging Storm + Wicked Wind Rune Bug

It is additive based on the base selected rune damage. This works as you would expect for all runes except Raging storm. A 5 stack with no rune is doing 7625% (1525 * 5), and a 5 stack with Wicked Wind is doing 4175% (835 * 5).

With Raging Storm rune selected, you instead get the 3200% for the first two merged, but then it adds 1525% for each additional merged twister, such that a 5 stack with Raging Storm gives 7775% (3200 + 1525 * 3), rather than the expected 8000%.

The base damage of a Raging Storm twister remains at 1525%, as a single twister would be 1525%. The bonus damage comes from merging, but that bonus is only applied once (for a 2 stacks), then the base damage is additively added from there. Just to be exhaustive, I had tested every combination of every rune (except the useless lightning rune). For Raging Storm, 1 twister was 1525%, 2 merged was 3200%, 3 merged was 4725%, 4 merged was 6250%, 5 merged was 7775%. Thus, peak dps is obtained if you can manage to only create 2 stack twisters.

Yes the damage increase stops after the 2nd tornado is cast / collided

You mean this damage increase of 150% per each twister?
So no matter how much twisters you casted the damage increase is always 150% x 2 = 300% and never reaches max damage increase of 750% when 5 twisters were cast?

Hmm, another thing to investigate:

Does area damage still proc based on if the last Twister cast was manual?

Or is the first Twister join the decider, and thereafter additional twister combines do not affect?

Either way the rotation for benefitting from Area damage is going to suck.

1 Like

Well the last way I knew Ragings worked was any combination of channeled ones into the originally cast one then procced AD and visa versa, so I’d assume more channeled ones would still, however the only thing that makes me hesitant about saying that’s a fact is that it merges into another new tornado.

So yes this has to be tested to verify before I say it’s a huge AD stacking benefit. From what I tested it only ‘feels’ like its working that way, but hard to say it absolutely does as it could be just the dps boost from the larger twister radius, which in turn amplifies more AD.

1 Like

MasterJay please refrain from creating such topics as Wizard Energy Twister much better!
before everything is tested. This way you show Blizzard everything is ok when it is not. Can you edit this post, because “Absolutely perfect, Thank you x1000, DON’T CHANGE A THING!” is completely wrong and is misleading for Blizzard.

3 Likes

What’s actually ‘wrong’ is that Wicked Wind rune is bugged. Me saying it’s ‘perfect’ is my opinion. Me editing my opinion would be irrelevant.

No disrespect to Lexy, awesome streamer and amazing wizard - but his OP is actually incorrect. If players want WW to be improved to do the full damage of Raging, well then that’s an entirely different thing, but you’d basically be making WW without question the best choice for all situations which I’m sure something would be better than nothing when it comes to being meta.

EDIT: Turns out there actually is something wrong, but it’s not with Wicked Wind. Apparently the Raging storm the actual rune is bugged, it’s losing damage via combining past the natural 2 combination (3,4,5) .okay now that’s actually a bug and pretty bad. Very well, taking down my post then, I’d ask Lexy to submit that bug instead to get more attention on it.

I’m wondering to myself here but do you work for Bliz? are you a dev? How do you know what was intended.

No not this, see below

This is what I was talking about all along. I tried to explain it to Lex last night on his stream, but he wasn’t understanding it.

1 Like

Of course WW will be the best choice, but we all Wizards wanted an affix making twisters spin in place (or giving Wicked Wind rune).
Blizzard didn’t listen, they made this change to Twisted Sword giving Raging Storm rune only to reduce lag.
Luckily for us it enables us to pick Wicked Wind, thus having stationary Raging Storm (only viable rune), but as it occurs it is bugged.

Blizzard ignored all our Wizard feedback, we are trying to make this one change to work as it should be.

Ah! Thank you for explaining. Yes we need to check.

1 Like

Well this is what I’m saying though, we’d be running back down that path again with WW in vanilla just taking over everything. The way it is now at least the other runes are more useful for speeds. When we slow it down and push the max GR , especially in 4 man’s then it deserves to shine, but buffing WW’s damage would just make it best for everything (not to mention likely overtake anything else). Not sure I’d support that.

I am very disappointed they ignored everything else, but it was clear Twisters were super disappointing and needed priority.

The way the patch note is written is unclear and causing some confusion. When it says “the Raging Storm rune is automatically applied” what exactly does that mean? Some are assuming it will inherit everything from the rune tooltip including the increased weapon damage, while others are interpreting it as only gaining the effect of the rune (merging mechanic and increased AoE).

I’m afraid they’ve done this backwards. The effect that we wanted was stationary twisters. Instead the effect granted was twister merging.

In another thread I asked a related question about whether Arcane Attunement and Arcane Dynamo can even be used with twister now since it seems like any snapshotted damage buffs could be overwritten once twisters merge.

But you are viewing it wrong, it is not buffing WW damage. We were given Raging Storm rune from Twisted Sword for free, the best rune with highest damage and area, which even before that change to Twisted Sword everyone would be still using.
But random nature of moving twisters make this build very bad, it only shined when Raging Storm twisters were stuck on objects thus making it spin in place.
Thanks to this change and possibility to chose Wicked Wind rune we can at least make this build viable again. And I will take it gladly when our oher builds were simply destroyed in this patch.

Exactly and remember how strong that was back then?? We were like 20 tiers ahead of any other meta build!

So here we are, with that dream again…with everything buffed to the teeth compared to almost 20 seasons ago and are we really going to say ‘well wicked wind only does ½ the damage in Raging form vs other runes that fly all around, and btw I only have about 3x5 stacked WW’s here with my PE’ :stuck_out_tongue: I mean lowkey that’s why I was saying it was so good, perfect was the wrong choice sorry, I’ve edited that now.

But be reasonable guys…

Exactly. But as I wrote earlier their intention was not to give us stationary twisters, but to reduce lag. Luckily for us merging twisters comes with the best rune with highest damage which everyone was going to use anyway, giving us the possibilty to make this rune stationary by also choosing Wicked Wind rune.

For me wording “The Raging Storm rune is automatically applied” means only one thing, as you wrote “it will inherit everything from the rune tooltip including the increased weapon damage”. There is no word “effect”.

Imagine there was an item applying all runes to the skill with 5 runes all dealing different damages plus some other effect (100% + some effect 1, 120% + some effect 2, 130% + some effect 3, 150% + some effect 4, 160% + some effect 5).
Logical outcome would be skill dealing 160% damage (highest one from all runes) plus combined effects of all runes.

Only in groups, not solo. Now this build is unplayable in groups because is still severely lagging. What is more there are already two meta group builds clearing 150 GR easily, so what is wrong with third build also clearing 150 GR in party?

But more important is solo clear potential, Wizard is the weakest class regarding solo pushing high GR’s!

Idk when the game wasn’t constantly trying to boot me and unplayable the lag was a lot better…I even had PE on and thats with this bad PTR server that obviously having issues since we cannot even play.

So I’d be very hesitant to say this didn’t fix twister lag with all other things working against it. Not like there’s a thousand twister wizards out there pulling 4 man meta group twisters right off the bat here on day one testing, I’m going to guess when it goes live it will perform much better. We’ll see.

And yeah obviously that was back then and this is now and we do need a big bump up, but I’d rather see it in a more balanced way then WW Twisters or leave, I feel like hydras could have used another bump up, obviously the other sets but they’re less concerned about that right now it seems.

Hi Frank. I agree, I also expected this outcome.

Again, I agree this would have also been my expected outcome. However, in this case I don’t think we can look at items that grant “all runes” for precedent, since that could be different than when an item only grants one extra rune. Items that grant “all runes” commonly applies to super forms like Archon, Shadow Power, and Wrath of the Berserker, or to utility skills like Blood Rush, Furious Charge, and Slow Time. Many of these don’t have updated weapon damage per se, but certainly give all the effects.

That said, I’m sure there must be some precedent for the behavior of items that grant one or more additional (but not all) runes. Gazing Demise, for example, says “Spirit Barrage gains the Phantasm rune.” Does this item grant both the effect and the increased damage? It’s been long since I’ve played WD.

Here is a link to a topic that lists items that grant additional runes or all runes. Something in this list should provide precedent for expected behavior of the updated Twisted Sword. Many of these specifically state “gains the effect of x rune,” whereas Twisted Sword is worded differently.
https://www.reddit.com/r/diablo3/comments/d57u34/gear_that_gives_all_runes/

Raging Storm is an unusual rune in the game where multiple casts actually cause it to essentially cast a new skill with a new weapon damage percent. Is there any other precedent in the game for that behavior?

This is the case for Raekors Set for example , thats why i also thought that it will incluse the dmg of RS.