Remove Advanced Tooltips Check (Fixes #81) #94
Merged
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
Fixes #81. in-mixin check was removed, but not the vanilla one. This also makes lodestones show up without advanced (we're assuming this was intended)
|
Here's a screenshot from our modpack to give reference - |
NebelNidas
pushed a commit
to ReviversMC/advanced-tooltips
that referenced
this pull request
Jul 29, 2022
Fixes Queerbric#81. in-mixin check was removed, but not the vanilla one. This also makes lodestones show up without advanced (we're assuming this was intended)
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.
Fixes #81 again. in-mixin check was removed, but not the vanilla one.
Side effects:
This also makes lodestones show up without advanced (we're assuming this was intended)
repair cost and lodestone location show up below advanced tooltips, if they are enabled.
Could use
INVOKEoncontext.isAdvanced()orthis.hasTag()with an ordinal to resolve this, but that's less stable as far as we know. Feel free to edit.