feat: automatically fix 1.20 items when switching to 1.21 - #1226
Draft
Olfi01 wants to merge 22 commits into
Draft
Conversation
Contributor
Author
|
Waiting for #1220, otherwise this is ready |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes #1214
Due to the switch from NBT data to components, items carried over from 1.20 to 1.21 don't retain stored data at the moment.
This PR implements an automatic fix for that, mixing into the process that vanilla Minecraft uses to do the same to its items.
As @IridescentVoid pointed out, a sample like this would probably also be a good addition to a 1.21 addon template.