Closed
Conversation
Update to 1.21.3
- Added ".orElse(false)" to fix error with Optional<Boolean>, now defaults to false
Owner
|
Thank you! Made these changes in a new PR (#44) to adhere to new workflow. Also made it easier with the merge conflicts :) |
Contributor
|
🎉 This PR is included in version 0.6.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Contributor
|
🎉 This PR is included in version 0.6.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Updated the mod to work with 1.21.5
Made a separate branch and pr for this again.
I updated versions of Minecraft, Fabric and Loom to work on 1.21.5
And added a false default to the nbt.getBoolean since it came up as an error. Now seems to be working.
Repeated all test from 1.21.4:
everything worked in my tests...