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

Color Manager #927

Open
4 tasks done
DrMaxNix opened this issue Jan 18, 2024 · 4 comments
Open
4 tasks done

Color Manager #927

DrMaxNix opened this issue Jan 18, 2024 · 4 comments
Labels
status:unconfirmed New issue. Needs triage. type:enhancement New feature or request

Comments

@DrMaxNix
Copy link
Contributor

Pre-suggestion checklist

  • I have searched existing issues and didn't find any previous issues with the same suggestion.
  • This is only one suggestion. I understand that GitHub issues don't work well with lists.
  • This feature doesn't already exist in the latest version of Wurst. I've made sure my installation is up to date.
  • I have looked at the code and am reasonably confident that this suggestion is possible to implement.

What type of improvement are you suggesting?

Adding a different kind of feature.

What type of player would find this improvement useful?

Builders, Miners, Griefers, PVPers, Redstoners, Anarchy/faction players

Description

These days, Wurst has a lot of hacks which highlight certain features with colors. There is no quick way to see all different colors on one screen; Instead you would have to open all hack settings one by one.

When changing color settings, it's nice to see whether multiple hacks use the same color, so you can be sure the color is unique.
For this reason I suggest adding a Color Manager to the Wurst settings menu under Managers, which lists all ColorSettings in a clean way.

Examples

This is how MiniHUD does it:
Screenshot from 2024-01-18 12-53-12

@DrMaxNix DrMaxNix added status:unconfirmed New issue. Needs triage. type:enhancement New feature or request labels Jan 18, 2024
Copy link

This issue has been open for a while with no recent activity. If this issue is still important to you, please add a comment within the next 7 days to keep it open. Otherwise, the issue will be automatically closed to free up time for other tasks.

Issues should be closed if:

  • They are duplicates of other issues
  • There is not enough demand
  • They are no longer relevant
  • There are not enough details

@DrMaxNix
Copy link
Contributor Author

Still relevant, didn't have time yet, will do at some time.

Copy link

This issue has been open for a while with no recent activity. If this issue is still important to you, please add a comment within the next 7 days to keep it open. Otherwise, the issue will be automatically closed to free up time for other tasks.

Issues should be closed if:

  • They are duplicates of other issues
  • There is not enough demand
  • They are no longer relevant
  • There are not enough details

@DrMaxNix
Copy link
Contributor Author

Still relevant, didn't have time yet, will do at some time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:unconfirmed New issue. Needs triage. type:enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant