Yeah I noticed this when there was supposed to be a fire storm in Thaldraszus and it wasn't up. Hopefully it gets fixed.
ppl getting the mount too fast LOL
I don't care anymore yesterday I gave the last one I've been waiting for so long muhahahaotherwise yes it's totally broken since 10.2.6 and not just storm a lot of other things tooif only Bliizard would focus their efforts on fixing retail and not fixing plunderstorm
Also, thank you Wowhead for posting about this problem!Hopefully Blizz sees it first thing Monday morning and can get a permanent hotfix deployed on Tuesday. Or maybe they'll just do another Tuesday to Friday evening hotfix. Even then, that's a few more chances for double storms to help people out.
is no one proof reading these before posting? So many errors
Everyone farmed them too hard. They no longer have the forces to maintain assaults in two different locations /s
Looks like they did something to make the storms not appear in Azure as much, and that ended up breaking the storm spawns and made it so they didn't spawn in Azure sometimes or at all if they were both suppose to be in Azure.
Just saying, but doing this achi with 1 storm at once was fine, lots of people complained they spawned too rarely, blizzard increased them to 2, broke something and now you sometimes get no storm, shouldn't have complained since that achi is nowhere near the most time consuming or hardest of the meta.
Raise your hand if you knew the next storm was gonna be in Azure Span... /raisehand lolThis is an embarrassing meme at this point. They just need to block the storms from happening in Azure SpanORDo a weekly rotation, where the storms spawn in 1 zone for the whole week and then swap zones on the weekly reset. (or even mid week swap)