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
When reporting an issue, please try to reproduce the issue with just Dominos and Dominos_Config running. Dominos reuses a good chunk of the stock UI, and other popular addons, like Move Anything, like to take control of those parts, too.
Addon Version
You can get this via running /dominos version in game 10.2.30-cata
World of Warcraft Version
For example, Classic, Retail, PTR, Beta. Cataclysm Classic
The Encounter Bar (shows Alt PowerBar from what I can tell? for when it shows up)
I have saved to a specific location (center bottom closer to my actionbars)
The move overlay at that location with /dominos config so it doesn't seem to be a persistence issue.
Unexpected behavior.
Regardless where it is saved it pops up at the default location when it shows up during fights.
The text was updated successfully, but these errors were encountered:
I restored a line that was commented out - in my local copy - and that seems to have fixed the issue (alt power bar showed at the saved location on Chogal with corruption mechanic)
When reporting an issue, please try to reproduce the issue with just Dominos and Dominos_Config running. Dominos reuses a good chunk of the stock UI, and other popular addons, like Move Anything, like to take control of those parts, too.
Addon Version
You can get this via running
/dominos version
in game10.2.30-cata
World of Warcraft Version
For example, Classic, Retail, PTR, Beta.
Cataclysm Classic
The Encounter Bar (shows Alt PowerBar from what I can tell? for when it shows up)
I have saved to a specific location (center bottom closer to my actionbars)
The move overlay at that location with /dominos config so it doesn't seem to be a persistence issue.
Unexpected behavior.
Regardless where it is saved it pops up at the default location when it shows up during fights.
The text was updated successfully, but these errors were encountered: