[Bug fix] See issues [#238], [#239] for details. #240
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
- magnet flag can turn on, on non-container block. - magnet feature behavior is incorrect with mult container. - magnet feature behavior is incorrect with furnace-like. - droptransfer feature can bind with non-container block. - droptransfer feature cleared item when bind a non-container block. - droptransfer feature can nested shulker box.
This was referenced Sep 6, 2024
for deatils see issue [pop4959#241](pop4959#241)
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.
magnet flag can turn on, on non-container block.
magnet feature behavior is incorrect with mult container.
magnet feature behavior is incorrect with furnace-like.
droptransfer feature can bind with non-container block.
droptransfer feature cleared item when bind a non-container block.
droptransfer feature can nested shulker box.
See issues #238, #239 for details.
This update includes more bug fixes in the two functions, can we reduce the version of API so that all users of 1.20.x can receive this bug fix?
Is it technically possible to be compatible again with versions 1.20.0 through 1.20.6?
thanks!