Skip to content
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

Hide recharge number. #49

Merged
merged 1 commit into from
Mar 29, 2017
Merged

Hide recharge number. #49

merged 1 commit into from
Mar 29, 2017

Conversation

Cluuey
Copy link
Contributor

@Cluuey Cluuey commented Mar 29, 2017

Having worked on quite a few class configs this option makes a mess of other options.
There are a few bars which are tracking a stacking buff and have a recharge underneath them.
Survival Hunter's Mongoose Bite is a singular example, other configs I've got tracking a buff while having the recharge of a different ability underneath the bar.

The display gets VERY confusing if the recharge is displayed numerically as well as graphically, even for setups I'm familiar with I lose track. I'm not sure how it works out which number it displays either, it didn't seem consistent.

I remember this was a requested feature, it seemed a reasonable request but in practice it doesn't work. At the time of the request it wasn't implemented yet, that was just based off the video feedback.

Having worked on quite a few class configs this option makes a mess of other options.
There are a few bars which are tracking a stacking buff and have a recharge underneath them.
Survival Hunter's Mongoose Bite is a singular example, other configs I've got tracking a buff while having the recharge of a different ability underneath the bar.

The display gets VERY confusing if the recharge is displayed numerically as well as graphically, even for setups I'm familiar with I lose track. I'm not sure how it works out which number it displays either, it didn't seem consistent.

I remember this was a requested feature, it seemed a reasonable request but in practice it doesn't work. At the time of the request it wasn't implemented yet, that was just based off the video feedback.
@Brusalk
Copy link
Owner

Brusalk commented Mar 29, 2017

At the moment it's a last-write-wins approach, so if there's multiple things setting the stack number it'll be whichever happened most recently.

I can definitely see this being confusing. I'll merge this in and then think of a better way to approach this so that it's less confusing!

Thanks for the feedback!

@Brusalk Brusalk merged commit c4fae09 into Brusalk:master Mar 29, 2017
@Cluuey Cluuey deleted the patch-19 branch March 29, 2017 14:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants