That’s not what I saw. Damage was multiplied by each Twisted sword multiplier stack, even if Twister was combined past 2 stacks.
Even a single combined Twister (5 stack) appears to benefit from the full Twisted sword multiplier of 8.5x.
Mhh well but that is what Cloud wrote, or did i get sth wrong there?
Anyhow…ill stick to Necro for S22. Not placing anything in corners, not worriying about getting oneshotted, just run around and pew pew xD
Or lagging out the group, or dealing half-damage as other classes, or not having a speed build…
1 Like
Raging Storm and Wicked Wind both have different damage values on the runes. There is a conflict when they are combined. I don’t think the lower number from Wicked Wind should override the higher number from Raging Storm. That sounds like a bug to me.
Even if you don’t think its a bug, there are also other reasons why we should have the Raging Storm damage. The build is underpowered with the Wicked Wind rune, even with Deathwish in the 4th cube slot. This forces us to play without stationary twisters, which means stacking on corners. It’s not a fun way to play IMO.
I have added a video showing the build playstyle and my thoughts in my first post.
1 Like
I had a long discussion with Northwar, he had a simpler calculations that shows the same values, even more accurate. I was following what blizzard tooltip mentioned precisly on Twisted Sword , and on the runes tooltip.
The Twisted Sword: The Twisted Sword: Energy Twister damage is increased by 125-150% for each Energy Twister you have out up to a maximum of 5. The Raging Storm rune is automatically applied to Energy Twister and allows the tornado to merge with 3 additional Energy Twisters.
Raging storm: When two Energy Twisters collide, they merge into a tornado with increased area of effect that causes 3200% weapon damage as Arcane over 6 seconds.
I am not sure if it matters when they refer two twisters as Tornado , and whether that means you got twister sword buff applied to the Tornado, or not. This is the descripency multiplier between my calculations and Northwar:
Northwar multiplier
1: 2.5
2: 8
3: 16.5
4: 28
5: 42.5
Cloud:
1: 2.5
2: 8
3: 16.25
4: 28.5
5: 42.25
This is the formula that northwar discovered
it’s 835% x 5 for WW
1525% x 5 for other runes
1525% x 5 + 150% for Raging storm
in Northwar calculations, there is no RS dmg multiplier envolved, so it’s a proof that you only get the two twisters merge into a tornado without any dmg benefit from RS rune, only twisted sword.
In my calculations, it shows that you get the dmg multiplier from RS rune. Northwar thinks it’s wrong. I am not trying to defend my equation, so what i am trying to find is a consistant equation that confirms that we are benefitting from RS rune dmg multiplier. how to proove it, is something i am not sure of
what really confuses me is the following:
- is there a difference between twister and tornado ? I mean, when i hear Tornado, is it two twisters calculated as 2(1+2(1.5)) without RS multiplier ?
- The Raging Storm rune is automatically applied to Energy Twister ==> so this is a case for two twisters , do we get the total dmg of RS dmg + 1 twister dmg ?
- and allows the tornado to merge with 3 additional Energy Twisters. ==> again, is this tornado represented as RS dmg + first twister dmg buffed by TS + second twister dmg buffed by TS + third twister dmg buffed by TS ?
- for each Energy Twister you have out up to a maximum of 5 ==> If Tornado dmg is calculated using RS rune+1 twister, have blizzard forgot to correct the icon on the bar that shows 5 twisters stacks ?
Also, having 5 twister formed out there + casting two more won’t help, they are not colliding as they are limited to 5. So i am still unable to find a way to prove my findings. Thought to share what i think with you guys, so if any theocrafter can think of a way to prove whether we get RS dmg or not, that would be great
1 Like
I think you may have missed it, but it’s already been proven. It was proven in the first 12 hours, man.
I have just went through a very thorogh testing, Northwar numbers are 99% close to what i was getting, my numbers were 4-5% off. I guess this is a confirmation that we are not getting RS rune dmg multiplier. RIP
cdn.discordapp.com/attachments/762453206814031872/769931252388069386/unknown.png
1 Like
Tested stacking Twister up to 5, looking for area damage. Twisted sword + Etched Sigil Cubed.
Here’s what I saw. If the first Twister that starts a Twister stack is:
- a manual cast, then that combined Twister can proc area damage.
- an auto cast (from ES), then the combined Twister will not proc area damage.
Can I get help confirming this?
If this indeed the case it would explain why I performed better when dropping AD as compared to using it in push. My cast rotation thus far has been to typically start building Twister stacks with an auto-cast ES proc.
Even if I were to adjust my behavior, there would still be some twister auto cast stack starts that ‘get through’ so to speak, and combined without being eligible for Area Damage.
Devalues AD in solo in my mind. On top of Twister stacking and resource management for Aquila, we’d now have to worry about our cast rotation when starting new Twisters? Too much. I might stick with 50% AD pushes for easymode if this is the case.
2 Likes
Thank you and Northwar for your investigations. This item design makes sense to me. It’s easier to understand for a stacking mechanic.
However, I think they should at a bare minimum, change the tooltip on Raging Storm to make it more clear, if indeed the intent is for scaling with:
- Number of Twisters stacked * Base rune damage of selected rune on skillbar.
I am still worried about Valthek’s ruining the gameplay (straight lines are terrible for Twister). However, now that we can combine Twisters up to 5, and Twisters redirect in the direction you were casting when combined, you can sort of ping pong combine Twisters into an area if need be.
Basically, the implementation of the higher stacking gave us slightly more control.
Agreed that corner stacking is still the better method if positioning allows.
I’m fairly conflicted on this one; On one hand, I want more rune diversity. I’ve been enjoying Mistral Breeze, for example.
However, corner stacking is more challenging. It definitely alters how you play the build, maps. Decision making is more varied. Most players may not enjoy it. I suppose I am odd in that I enjoy this type of gameplay.
As far as increasing the base rune damage of Wicked wind (and therefore the scaling value for stacking via Twisted Sword’s Raging Storm stacking mechanic), I am in support of this.
However, I think increasing the base rune damage of Wicked Wind to the same level as other runes makes it too advantageous.
I’d place it somewhere in between, at about 1150%. An increase, but not equivalent.
To be clear, I’d prefer balance between a Wicked Wind playstyle and a non Wicked Wind / corner stacking playstyle.
This way, players could choose which style they want, rather than be seemingly forced into one playstyle or the other.
Yeah, wondering about the intent here too. The build can’t fit in all of the designated multpliers without it.
All twisters that are casted from channeling (off hand) does not proc AD, i think that’s been the case long time ago as per Achilles. You need to manually cast twister to proc area dmg.
3rd scenario - If you have twisters casted in place and then you start channeling, the combined twister will proc Area dmg as per sVr.
If they fix the Twisted sword where the dmg of RS is considered , we still won’t be playing ww (as high end players with max dps intent). simply coz ww dmg + RS dmg < any rune dmg+ Rs dmg.
If you want to play a controlled build, you will need WW dmg to be buffed. If you want a 150 TK , you will need not only to buff WW, but also to get the dmg from RS rune.
Play by the wall is hard, and inconsistant. Wizard already DR everything so the barb can’t move things as flexible as it can. not to mention the tight spot. So far we can’t really test the max dmg we can get with the current build and bugs coz it’s hard to apply the rules , where u stack trash and ensure ur twisters are not off…etc