Some missing tooltips and checking for errors across all tooltips #20
Conversation
This file contains hidden or 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
… errors etc across all tooltips Quick pass through all tooltips to check for errors. Also added a few missing tooltips, but this is far from complete.
HaroldCindy
approved these changes
Sep 8, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Was getting annoyed seeing the typo on
DAMAGE_TYPE_IMPACT, so decided to fix this.Quick pass through all tooltips to check for errors such as with typos, punctuation, grammar, etc.
Also added a few missing tooltips, but this is far from complete.
Used Claude to give me a list of errors it was able to spot for me after I was already half-way through the definitions. I did the edits myself to confirm/review. As this is a larger edit have also popped it through a YAML validator as well just in case.
Interestingly Claude was able to deduce a logical error for
llSetLinkSitFlagswhich I probably would not have caught which was fun to see given I only asked for typos.