Fix bodypart_color_text.json clause priority #62191
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
[JSON]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Bugfixes "Fixes bodypart status text color for very injured characters"
Purpose of change
I noticed while my latest TCL challenge run was being eaten alive that the color of the text on the sidebar was wrong and behaving badly. This was caused by the fact that lower intensity clauses came before higher intensity ones, and therefore took priority.
Describe the solution
Re-order the clauses in the file with the most injured state being first and the least injured state being last.
Describe alternatives you've considered
Ignoring it.
Testing
This is with the current JSON file...
And this is with the fixed one:
Additional context