WeakAuras

WeakAuras

206M Downloads

Range finding for spell seems to be broken after Blizzard Update in Classic HC

johnblackjr opened this issue ยท 2 comments

commented

Is there an existing issue for this?

  • I have searched the existing open and closed issues.

Description

I have been using a WeakAura for years that changes the color of an icon based on a condition for spell in range. It no longer works in Classic Hardcore after a Blizzard update in the past week or so. Based on Frostbolt. Running a macro IsSpellInRange(GetSpellInfo(116), 'target') still properly returns 0 or 1 corresponding to the range of the target relative to the Frostbolt spell, so the underlying function that (I assume) WA uses still works. It must be that something else was broken. I have updated WA to 5.17.1 for WoW version 1.15.3. I deeply apologize if this is not a bug and it's something I am doing wrong, or if it's something Blizzard is doing wrong and they will fix it.

WeakAuras Version

WeakAuras 5.17.1

World of Warcraft Flavor

Classic Era

World of Warcraft Region

US/NA

Tested with only WeakAuras

I got this issue with only WeakAuras enabled

Lua Error

No response

Reproduction Steps

Install Frostbolt WA below and target a hostile mob on a mage with frostbolt (or change to fireball so you don't need to level a mage to 4). Then go into range and out and icon on the screen doesn't respond

Last Good Version

No response

Screenshots

No response

Export String

!WA:2!Dr1tVTrru8Kyjk4uqe3qaIIQcfjRwkkQfOPqaAJTJttATtSw72YHi5D2DF2ZqwpZQzM12Ph9HQE2h4sV5dCIt(cxrv8byKfFcYnUHYbUwEZU2P0ShM9nZ8(7V3V5n)U56KlixWlU1iMVGxxel9H1Mt2)WwTuGEV)4BE(VF)x)6xpMe8ZXkneuLXxqEY0B3w9(5V6CZn3yc3NkK1emU2Ru5dAu2zIVqegi6XR3JfbUVA22YbTbArBSChOLS2TbPAJ8YPI)Br9jrGJkccdhMSEaPd83NQI9GUaxxpUvlw)XnlvOEJM1BuWPHdhvqLnAPyf0SnWbjZVov07qU7K3A7if(RqypYjQORyvg6t81nppi0jsGewF22H7kfkTNiupXQ85Q5oirC)av2ZZQAsaZkN61kxPsXyot7ffsobKoj3g9PLMw7RxtkAlbLA9RNeNBm06ATK4FS7OaWdlUgy5l3RCLA7(4kdJ5tHLS5nl(Rj5HTAT5zhQ5YM1gzpIIB1u3Zs)3uGoGOfYvZDpZv92l5Wbw9SjMBse9djkf1l1GvZDlZAEAISnOnFM5AMp3gTxS0PZSHPSR0KWtrmHfY0N4AY5AUYPQeODw9zUUBIhWmZC1OLFmA26LOeS(0yFaT0xH3CZepRPyzOTQ4A(e3KcrPj6yfD45brMkbMvMF0B03CtZ6UMpyEmrJwcDnRl0ifMQkcGFBUZqsii5KWNGulMG)YtJMc7PS7VyT5wyiHZ6q04TB6GHvQ31C5ICbhEfquqDTe4T10lnjiwMOvtlTuQaK2gOgy1X2OmBvSdHXrBnBz((lz(bZpAUNzlVwmotrV4XyhwHfi6qGoqk0joE(rijYbAJIQvxXC5j4wpKp0wkI5bylI1MIVZ27L)Pl(oZlXmWTyOGe8CZnCp9CU5XCSbK2EjHiK4IT0qK9TItN4qnlB0YxGZNAqru2FfZJY6KqkY7Py82HqXQfEqz80Ik2Za71rFiAEHPZaWPaK(0Z0qFSCGNkjrwKpA5svkuTwJdlwPqPhvyND2VX(pPSNkb09yDIesTJViuiFyg8ZRdtkfs6f9mJthjtaKei(9gmBYbDOhwqb2q5uSs5d2XYRS42MMVlBreY1znBN9ndQi9xiAPaMYxcAO55aUh2dBXANvon9J2CFlFPfXhoQqqa6VJEkqoUa2Ouhvt0dKjIvHag5O0tTRFDXNjeDMpA5zPxd0D7WuemjdOo9ybA6EB)G7)lBJ9TrAHF3u247(L)Z1ybMp2HegrjzIYHv)S3pyP5yBVNLooDxj(y3ccE1l5uU8bJBzpajNenjZxfZcg3JVtHhxU6nQw6Usg3gbGoubHTsMeBENjKyn6OdJsWPSJS0xwI8w5D8PG)XB60Legdzg0Liz2Cp6JyCLDkRpdzpoqA7tzwmJ0Ns4Tb1Q5nXpSwMBTXDswYKza((cFDOpX808g9MM4mMUJeVzQWIzm9VGrPwA()w8Q05QChBqEBB(w7YTtwsSzmJ3sitF)UYyu0hkBN0QCp7yaIky50Ah710CkV7SXTV7g3ox3)6N(V)

Bisector Report

No response

commented

As of this evening, it appears it was fixed (likely on Blizzard's end). Thanks!

commented

Closing