You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing open and closed issues.
Description
This weakaura has some code in on init that hides the default casting bar.
I would expect that this code would not run if the aura is set to loaded never (or just in general, not to load on this character) - but I don't have any casting bar when logging on if this weakaura is installed.
This also happens if it's the only aura installed at all.
EDIT: A bit further debugging - it seems that the trigger runs an OPTIONS event when entering world which then causes it to happen? I wouldn't expect a trigger to run on entering world when it's set to load never.
I have taken a look at why exactly in this case we run the init function, that is what custom code does get executed on adding. Most of them are due to creating the conditions function, which requires knowing what the state will contain. Which is done by either examining the custom variables, or by running the trigger function.
Is there an existing issue for this?
Description
This weakaura has some code in on init that hides the default casting bar.
I would expect that this code would not run if the aura is set to loaded never (or just in general, not to load on this character) - but I don't have any casting bar when logging on if this weakaura is installed.
This also happens if it's the only aura installed at all.
EDIT: A bit further debugging - it seems that the trigger runs an OPTIONS event when entering world which then causes it to happen? I wouldn't expect a trigger to run on entering world when it's set to load never.
WeakAuras Version
5.13.2
World of Warcraft Flavor
Retail (Default)
World of Warcraft Region
EU
Tested with only WeakAuras
I got this issue with only WeakAuras enabled
Lua Error
No response
Reproduction Steps
Last Good Version
No response
Screenshots
No response
Export String
Bisector Report
No response
The text was updated successfully, but these errors were encountered: