Color Manager

[DrMaxNix]

Pre-suggestion checklist

• [X] I have searched existing issues and didn't find any previous issues with the same suggestion.
• [X] This is only one suggestion. I understand that GitHub issues don't work well with lists.
• [X] This feature doesn't already exist in the latest version of Wurst. I've made sure my installation is up to date.
• [X] 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:

[github-actions[bot]]

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]

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

[github-actions[bot]]

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]

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

[github-actions[bot]]

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]

Still important to me.

On 22 July 2024 04:24:42 CEST, "github-actions[bot]" @.***> wrote:

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

-- Reply to this email directly or view it on GitHub: https://github.com/Wurst-Imperium/Wurst7/issues/927#issuecomment-2241923440 You are receiving this because you authored the thread.

Message ID: @.***>

[github-actions[bot]]

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]

Still relevant

On 23 September 2024 04:35:46 CEST, "github-actions[bot]" @.***> wrote:

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

-- Reply to this email directly or view it on GitHub: https://github.com/Wurst-Imperium/Wurst7/issues/927#issuecomment-2367135142 You are receiving this because you authored the thread.

Message ID: @.***>