feature(minimessage): Rainbow tag saturation argument #1210
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a saturation argument (optional) to
rainbow
tag. It simply sets the saturation value of eachHSVLike
to the argument value or 1 if omited.Why? Max saturation can be unpleasant for eyes, especially on longer texts.
The syntax would follow
<rainbow:[!][phase]:[saturation]>
.Since the current algortihm has default values if argument is of lenght 0 this allows for such syntax:
<rainbow:0:0.65>
<rainbow::0.65>
It also uses
Float#parseFloat
method meaning any legal Java float representation is allowed:.65
,0.65f
,1
etc.This PR also partially closes #1038