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
Is your feature request related to a problem? Please describe.
The default Blizzard UI spell charges font is really small and not well readable, especially at smaller actionbar sizes and/or with an active recharge happening.
Describe the solution you'd like
I would like to have an additional text display that replaces the charges text and is customizable like the cooldown text e.g. font, font size, color, position.
Describe alternatives you've considered
I tried many different actionbar addons and UI solutions, but most don't have such an option or are far too bloated for this use case alone, and I already use OmniCC which replaces the cooldown text which in my opinion is directly linked to charges for a spell which has them.
Additional context
Add any other context or screenshots about the feature request here.
Greetings and thanks for consideration!
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The default Blizzard UI spell charges font is really small and not well readable, especially at smaller actionbar sizes and/or with an active recharge happening.
Describe the solution you'd like
I would like to have an additional text display that replaces the charges text and is customizable like the cooldown text e.g. font, font size, color, position.
Describe alternatives you've considered
I tried many different actionbar addons and UI solutions, but most don't have such an option or are far too bloated for this use case alone, and I already use OmniCC which replaces the cooldown text which in my opinion is directly linked to charges for a spell which has them.
Additional context
Add any other context or screenshots about the feature request here.
Greetings and thanks for consideration!
The text was updated successfully, but these errors were encountered: