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've spent a bit of time trying to figure this out, as I have an army of alts that were mostly 70 prior to the release of TWW. Yet when I log into some of them and take them to Dornogal to start their TWW adventure, the Expansion Button on the minimap stays the one from DF. After a bit of digging, I tracked this down.
The button is tied to a CVarBitField named "unlockedExpansionLandingPages" which the DF and TWW buttons use. This bitfield gets set in the Blizzard_ExpansionLandingPage AddOn. Specifically when there is an event on the ExpansionLandingPageMixin (Blizzard_ExpansionLandingPage.lua line 37) it calls RefreshExpansionOverlay() which checks if the current overlay is the latest, and ultimately calls TryCelebrateUnlock() which would set the unlockedExpansionLandingPages CVarBitField.
For some reason, with your addon loaded, this doesn't trigger. I can disable your addon on a toon this is happening to, let Blizzard's set the bitfield, and than turn it back on and all is well.
However, realistically you shouldn't be blocking this.
The text was updated successfully, but these errors were encountered:
I've spent a bit of time trying to figure this out, as I have an army of alts that were mostly 70 prior to the release of TWW. Yet when I log into some of them and take them to Dornogal to start their TWW adventure, the Expansion Button on the minimap stays the one from DF. After a bit of digging, I tracked this down.
The button is tied to a CVarBitField named "unlockedExpansionLandingPages" which the DF and TWW buttons use. This bitfield gets set in the Blizzard_ExpansionLandingPage AddOn. Specifically when there is an event on the ExpansionLandingPageMixin (Blizzard_ExpansionLandingPage.lua line 37) it calls RefreshExpansionOverlay() which checks if the current overlay is the latest, and ultimately calls TryCelebrateUnlock() which would set the unlockedExpansionLandingPages CVarBitField.
For some reason, with your addon loaded, this doesn't trigger. I can disable your addon on a toon this is happening to, let Blizzard's set the bitfield, and than turn it back on and all is well.
However, realistically you shouldn't be blocking this.
The text was updated successfully, but these errors were encountered: