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
All testing is using only ElvUI, ElvUI Config, AddOnSkins, and QuestHelper.
When I enable AddonSkins and have QuestHelper ticked, very soon afterwards my power bar reverts to the default "Blizzard" texture and will not change back to my chosen texture. This bug affects the power bars of every unit frame. It's also not fixed by attempting to force a power bar texture with the Custom Tweaks plugin.
It does not occur with AddOnSkins being used without QuestHelper, as long as I haven't enabled QuestHelper and AddOnSkins at the same time. When I disable AddOnSkins and QuestHelper (either or both), the visual bug persists. It also persists between profiles and characters. If I click over and over again, sometimes the frames (or one frame) will briefly change back, but this only lasts until I click another frame. The only way to reset it is to delete my WTF folder.
The text was updated successfully, but these errors were encountered:
All testing is using only ElvUI, ElvUI Config, AddOnSkins, and QuestHelper.
When I enable AddonSkins and have QuestHelper ticked, very soon afterwards my power bar reverts to the default "Blizzard" texture and will not change back to my chosen texture. This bug affects the power bars of every unit frame. It's also not fixed by attempting to force a power bar texture with the Custom Tweaks plugin.
It does not occur with AddOnSkins being used without QuestHelper, as long as I haven't enabled QuestHelper and AddOnSkins at the same time. When I disable AddOnSkins and QuestHelper (either or both), the visual bug persists. It also persists between profiles and characters. If I click over and over again, sometimes the frames (or one frame) will briefly change back, but this only lasts until I click another frame. The only way to reset it is to delete my WTF folder.
The text was updated successfully, but these errors were encountered: