We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
FTB Quests
ftb-quests-neoforge-2102.1.7
NeoForge - 21.1.93
FTB Evolution
When editing text using string formatting [ ], setting the color on the first string using {"color": "#HEX"} changes the default string color.
Having an empty string "" at the start of the [ ] retains the default string color (white).
No response
Create a new quest and edit its description with the following examples:
[{"text": "This is", "color": "#55ffff"}, " example one."] ["", {"text": "This is", "color": "#55ffff"}, " example two."] [{"text": "This is", "color": "#55ffff"}, {"text": " example", "color": "#ffffff"}, " three."]
This could be a default minecraft feature with how they handle string manipulation but would require more testing in an unmodded client.
The text was updated successfully, but these errors were encountered:
desht
No branches or pull requests
Mod
FTB Quests
Mod version
ftb-quests-neoforge-2102.1.7
NeoForge / Forge / Fabric version
NeoForge - 21.1.93
Modpack & version
FTB Evolution
What issue are you having?
When editing text using string formatting [ ], setting the color on the first string using {"color": "#HEX"} changes the default string color.
Having an empty string "" at the start of the [ ] retains the default string color (white).
Crashlogs
No response
Steps to reproduce
Create a new quest and edit its description with the following examples:
[{"text": "This is", "color": "#55ffff"}, " example one."]
["", {"text": "This is", "color": "#55ffff"}, " example two."]
[{"text": "This is", "color": "#55ffff"}, {"text": " example", "color": "#ffffff"}, " three."]
Anything else to note?
This could be a default minecraft feature with how they handle string manipulation but would require more testing in an unmodded client.
The text was updated successfully, but these errors were encountered: