Also means what I said about D3planner was exactly right, it does do Raging Storm damage with the combination…it’s just that the extras don’t lol, which never was reflected in the planner anyway, only the two twister combination. I mean…this honestly isn’t the worst then, it’s better than we thought initially, but also not as good as we thought for the max 5.
So that means if all other twisters does 3½ Ragings equivalent damage, then it really only has a x2 advantage over WW - which exactly brings it back to normal.
That would actually mean bad news guys, that it’s working precisely as intended. Like I’ve said from the start, WW is not suppose to do equal damage to a moving twister, just wouldn’t make sense, especially now that the others despawn again on corner.
But yes I completely agree with Cratic that some kind of bare minimum communication should have been issued on this, they just confused everyone with this!
You seem to always claim knowing what is intended. I’m not sure how you are getting this information, unless you are talking to a Dev. There has been no communication on these issues. You claimed twisters were working as intended without any clue, and you were wrong. They have changed twisters again since the PTR ended.
I see this newest change as an attempt for fix what wasn’t intended.The problem is now this twister interaction is inconsistent. This makes it seem even more like a bug than before to me.
I gave the Wizard a test and while it seems ok the new Twister Build its definately fun to play but its far from going to be the OP way to go if you play Wizard. I do agree with Blizzard decision to remove Twister corner stack that was a clunky way to play the build and withut rose tinted glasses on i completed agree that stacking twisters against a wall or corner was never an intentional mechanic
I am just claiming that WW was never intended to do the same as the other Twisters or what would be the point in them? That was my argument with your original post is that you seemed to have expected it to just do Raging storms damage % from this change. That the only intended claim seems to have been to reduce lag, however we are seeing a damage buff from the interaction of 2 WW’s and 4 WW’s, so honestly that seems good. If their intent was for all Twisters to be 4 Ragings in one then obviously we have a problem, I never claimed I knew that, I don’t know. Communication is needed I agree and wouldn’t have a problem with that.
Sorry but I wasn’t wrong, you were not testing merged WW Twisters nor Raging Storm and I kept saying that during PTR that you were only testing one WW which didn’t make sense since you only gain the effect of Raging Storm with two, and guess what? It’s doing Raging Storm damage, so you just proved yourself initially wrong here, not me. Unless I’m misunderstanding your original video you posted In PTR, I did not see merged WW damage test, just one WW. And from that I was assuming you were assuming 835x2 = WW’s version of Raging when in fact it actually is 3200. Correct me if I’m wrong.
I’m going to get into trouble for agreeing with you, but I’m going to do it anyway. This is not the first unintended mechanic to be exploited by players. Then they discover the error and fix it, and the players misinterpret the fix as taking away something when that something should have never been there.
There is only a handful of skills in the game that have more then 1 or 2 useful runes. Things like seethe&dark heart for vengeance ect. Almost everything has a clear cut best option rune. That is more of the issue I’m getting out of the main post. It’s not that corner stacking is broken again (it was intended back in s7 to get rid of twister meta for balance)
Has anyone group tested twisters in a 4man as trash clear? Using wicked. If I’m not mistaking the ns clears that did 141(?) We’re done without twister stacking but wanted to not have full para and take into consideration they would have death wish available in season. So Im sure it can still be used as a viable option. It just won’t be #1 option.
I’m not sure about #1, but I’m optimistic. LoN Arcane Twister was one of my favorites back in the day, and now that LoD frees up two ring slots, combined with Stone Gauntlets/Ice Climbers, and a fourth slot? You bet I’m gonna try it.
You need to stop. You make no sense and are not helping.
It’s already explained in the thread, by multiple people (see Cratic and Tinne). If you follow Lexy, you’d know he has tested all of this throughout PTR and recently when the patch went live.
You are not helping, you are just adding noise to the conversation here and taking away from what the post is intending to do. If your goal is to contribute, then read, educate yourself, and most importantly test it yourself, before just blurting out things on the forums.
Or maybe you should understand what I am saying. I happen to have ‘a little’ experience with Twisters
Assumed on PTR: 835x2 = 1670% Wicked Winds “Raging Storm version” , which is basically a base single Raging or unruned when really it was 3200%. What I’m saying is that never changed from PTR and that he just didn’t test that, again he can correct me if I’m wrong that’s just what I saw him post.
Then the unknown (although I did see other poster in PTR bugs mention it) that 5 Twister combo should have been 4 Ragings but really it’s just 2 Ragings + 1 extra. I am saying that is likely working as intended as was never meant to be an extreme damage buff over what 5 Twisters previously was, literally just meant to kill the lag 5 Twisters vs 1 Big one would do. And they definitely should communicate that.
That is what I’m saying.
It’s still a decent buff over not using it at all which is 835x5 WW or 1570x5 Raging vs 3200+835x3 WW or 3200x2+1570 Raging. Should it be more? YES probably , I am not arguing that, I’d love to just see all of them be 4 Ragings worth of damage with the 5 Twister combo. I am just stating that what is happening is likely intended and no bug.
Yes, I did the testing for stacked twisters on the PTR, as did many others. If you look at the others posts in this thread by Cratic and TinneOnnMuin, they also confirmed the change.
Lets agree to disagree. For me that is no decent buff, i wanted to have the option to play Wizard in S22. I still do have that option but it is like amputating my own leg when i signed in for a ballet competition.
For me Wizard is , in the current state, downright unplayable. And i do highly doubt that the 2+1 Twistermechanic was intended.
Also the tooltip of the item is misleading then. For me the tooltip reads like this:
Pick whatever rune you want and that rune will get all the effects from the Raging Storm rune, including its dmg.
And honestly this is somehing that should have been tested on the PTR , and then maybe be tweaked down a notch. But like this its just…mäh
Typhon is still behind or now halfway en par with LoD Hydra…when a Set specifically designed for one single skill , should outperform a LoD - Variant.
DMO plays strange and still feels too weak.
Twisters is bugged
Frozen Orb is mediocre
Wizards were in desperate need for some serious buffs and viable builds and all they got were the melted leftovers of some cookie-dough ice-cream from a birthdayparty they never were invited to.
Okay I tested it too, didn’t get the exact weapon % just felt way stronger than simply 835x2 for WW > Raging WW version, so fair enough and I guess I’m referring to the first video you posted where immediately players were telling you that it wasn’t a bug just a misunderstanding, you had like 4 posters retort that yet I’m the only one here that gets the ‘are you a dev, and how you know what’s intended?!’ flack for it.
It’s fine though, we all have collectively said how disappointed we were in this change so there’s no need to argue among ourselves the semantics of this. If you want to continue to call it a WW bug to get attention on it, I won’t stop you my dude because every single one of us can agree it’s under-performing and won’t be meta.
That’s the bottom line here, for Wizards to have a S22 meta!
I’m forced to accept that for now, but I’m just saying…this is how we used to discover things in Vanilla - we didn’t need the clarifications lol. It’s a different time though, and we’re used to a standard and suddenly aren’t getting it so I’m going to let this go.
I do however want to know what gives with removing corner stacking again, we tested it during PTR and it certainly wasn’t OP!
I did similar tests and it looks like my damage got multiplied x3,6 when stacking wicked winds instead of shooting them on 5 different points of the map.
So it’s getting the Raging storm damage but it’s not getting extra damage from twisted sword affix " allows the tornado to merge with 3 additional Energy Twisters" so I’m not undesrtanding what’s the purpose of this sentence.
Please Blizzard look into this before s22 start, the wizard has still chances to be fun with this build if you remove the bug.
I’d like it if Twisted Sword granted us this: Get all Runes and make 1 giant Twister that is stationary for 5 seconds, limit of only 1 onscreen but it does massive damage. (element could roll off your gear or somehow you could select the element by Rune selection)
This would be great for zbarbs/zmonks that gather mobs into 1 cluster, then the Wizard can unload the giant twister. This would be equal in some how to the Witch Doctor Mundu build. And it could serve as additional damage on a Rift Guardian. This would also reduce the massive lag issue having too many twisters on screen at once.
As long as twisters keep moving around (at any pace… it’s not going to be as good as Mundu Build for clusters of enemies).
