-
-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All Range checks are failing and causing the addon to stop functioning with the latest game release: 10.2.52188 #4713
Comments
Yeah Blizzard did that |
Because Blizzard decided to mess with the range checking in an hotfix. Fixes: WeakAuras#4713
Because Blizzard decided to mess with the range checking in an hotfix. Fixes: WeakAuras#4713
WeakAuras.CheckRange is it based only on items? will it be completely disabled in combat, or redesigned under IsSpellInRange? |
I tested that latest fix([Prototypes.lua. For example, I set a prompt within 20 yards of the Sword of Justice. The distance determined by the plug-in is significantly smaller than the actual distance of skill casting in the game. This distance determination is seriously inaccurate. |
I tested the modified version commented above. Not only is distance detection grossly inaccurate. Some small range distance detection is still invalid. I haven't tested them all, but some distances such as 10, 20, and 30 work. As for the accuracy of distance detection, it should not be as good as the previous version |
it is clear that the functionality of IsSpellInRange is severely limited by your spells. For someone it will work well, but for someone it's just disgusting. |
Is there an existing issue for this?
Description
Just noticed this about 10 minutes ago.
WeakAuras Version
5.8.5
World of Warcraft Flavor
Retail (Default)
World of Warcraft Region
US/NA
Tested with only WeakAuras
Lua Error
No response
Reproduction Steps
Create item using the Range action.
Last Good Version
No response
Screenshots
No response
Export String
No response
The text was updated successfully, but these errors were encountered: