WA-Group not loaded properly until WA Configuration is opened
Breakerzeus opened this issue ยท 7 comments
Describe the bug
I created a WA-Group for Orgozoa benthic Gear and made the requirement for it to load by the ZoneID (ZoneIDs are set in the according WAs itself). It consists of two WAs, therefore the Group. When you enter the raid and get to the first time it should be loaded, the Orgozoa Boss Room, it won't load the WA-Group. You have to open the configuration of WA so the Addon 'checks' it and from then on it works fine. It's just the initial Load for it that seems not to happen correctly. Without the Group it works perfectly fine without having to open the configuration, so I'm guessing it seems to be the group that causes the issue here.
WA for code review purposes:
https://wago.io/2_n91MwPA
Do you have an error log of what happened?
no Error log, since the is no lua error or smth. like that
To Reproduce
- Enter Raid
- get to Orgozoa Room -> won't load the WA
- open WA Configuration
- close WA Configuration
- WA works fine
Did you try having WeakAuras as the only enabled addon and everything else (especially something like ElvUI) disabled?
yes
Which version of WeakAuras are you using?
latest Release Version; 2.14.6
Was it working in a previous version? If yes, which was the last good one?
n/a
I have new Information that it works for a Guildmate. He rarely updates his addons and has some old version 2.13.4 installed. So that is also a strong indicator that it has to be something with the addon itself, the WA seems not to be the issue here.
The group consists of two auras, I'm not sure which of the auras is the one that is problematic.
I've tried reproducing, but can't access Orogonzas room anymore, just the pool below, which has the zone id 1517. There the aura works correctly for me, thus I'd be suprised if the zone I could reproduce it.
Putting auras in a group does not affect the loading/unloading at all, so that has nothing to do with it.
I tried to ungroup them and then noticed that they indeed have the same issue without the grouping.
But the Problem remains the same. The WA are set like this:
In a normal state the WA has visibility 0% and one condition, that if you do not have the belt equipped, the visibility goes 100%. maybe there is some issue by loading the conditions? IDK
I haven't forgotten about this bug report, but to reproduce it, I would need to at least to a LFR wing. And that consistently puts it behind pratically any other bug report, that takes less time to figure out.
Yeah well I tried it in the last few days with my mythic ID. We killed Orogoza so I got into the boss room as I entered the raid. That way, the WA is loaded instantly and displayed correctly. So it seems the only way to reproduce it is to get through the other "raid zones" with the bosses I guess. It's getting more mysterious...
EDIT: Ok just tried it with LFR again. WA did not popup until I opened the configuration (like mentioned before).
EDIT2: Alright so I tried it once more (due to wipe on LFR...). We pulled the boss and after the fight has ended, the WA was displayed. So I think that WA only checks the encounter ID or the Zone ID by entering a raid (loading the UI), loading the configuration (where you create WAs) and when entering/leaving combat. Maybe that's the reason why it worked a while ago when I entered the raid and started in the boss room where it should pop up. that also explains why it does not work when going the "normal" way through ashvane and the way down there to orogoza.