Fix more custom ingredient implementation issues #4287
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
- Fix Ingredient.OPTIONAL_PACKET_CODEC not being modified to work with custom ingredients - Fix ShapelessRecipeMixin sometimes not collecting all non-empty item stacks - If client does not support certain custom ingredient, send CustomIngredientImpl#getCustomMatchingItems instead of dummy default (stone)
PepperCode1
added
bug
modmuss50
approved these changes
Dec 9, 2024
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.
Ingredient.OPTIONAL_PACKET_CODECnot being modified to work with custom ingredientsShapelessRecipeMixinsometimes not collecting all non-empty item stacksCustomIngredientImpl#getCustomMatchingItemsinstead of dummy default (stone)Likely fixes #4225.