-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Action bar 4/5 seems mixed up #164
Comments
Hey, I wrote about that in a comment on curseforge yesterday I think, theres a problem in the blizzard code that the extra actionbars 4/5 are linked together in the options, like you need to activate 4 before you can activate 5. I already have an idea to override that completely, and use my own logic like in the custom bars 6/7/8. Greate report btw ❤ |
Should be fixed with 0e07fc2 |
Do you publish main as an alpha build? If so i could test this now and validate for you. |
Noticed you actually just made a release, which is even better. |
Only sometimes, because the automatic update pipeline is only for releases right now. But everything should work fine now, because I'm reusing the logic from Actionbar 6/7/8 to show/hide the bar; I just force the blizzard CVars and activate every actionbar, and then handle the visiblity from the config state. |
Toggling bar 4 does still seem to hide bar 5, but thats acceptable. |
You mean toggleing them in the blizzard options, right? |
But ofc if you change the Blizzard options, they will be hidden again, but after /reload etc they will be set to true again. So you would ignore the blizzard options now. |
Unfortunately not. 2024-07-28.12-08-44.mp4 |
Unrelated but its also hiding the stancebar after some updates, but it returns on a reload. |
Ah, you dont have the newest Version v0.13.2. |
Apologies i swore i had updated :| |
Working great thank you! |
Haha, classic! |
Describe the bug
Action bar 4/5 seems mixed up in settings
AlwaysShow seems to be flipped.
Error Log
No log, but see attached video
2024-07-27.13-12-16.mp4
Versions (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: