Rewrite block tags 26.1 to 1.21.11 for client prediction - #1309
Open
HaHaWTH wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
https://www.minecraft.net/en-us/article/minecraft-java-edition-26-1
Mojang renamed the following block tags for consistency in 26.1, VB currently only adds empty tags for them, this breaks client-side block place prediction.
Tests showed this caused the client not to play the arm swing animation and block place sound when placing bamboo and other blocks.
Diffed the block tag json in 26.1 and 1.21.11, can be safely renamed.