Fix nbtedit using the wrong datatypes. #164
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
Lyfts
approved these changes
Dec 19, 2024
Dream-Master
pushed a commit
that referenced
this pull request
Dec 19, 2024
(cherry picked from commit 148665e)
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.
Numeric NBT types aren't implicitly converted at runtime, so if you have something that looks for a byte like a bool, it gets annoying as it won't be able to read the int you just stored there; I use this a lot for testing the crop rework.
java_7LMlSJqTkw.mp4
This PR fixes this problematic behaviour.
java_V2Ani48II3.mp4