-
-
Notifications
You must be signed in to change notification settings - Fork 222
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Fixed types for packet_player_auth_input 1.17.x Changed block_position from vec3i to BlockCoordinates in TransactionUseItem (types.yml) - The y value for block_position needs to be varint and not zigzag32 - The face value needs be zigzag32 and not varint Changed position from BlockCoordinates to vec3i in packet_player_auth_input.input_data.block_action (proto.yml) - The y value for position needs to be zigzag32 and not varint * Fixed types for packet_player_auth_input 1.18.x Changed block_position from vec3i to BlockCoordinates in TransactionUseItem (types.yml) - The y value for block_position needs to be varint and not zigzag32 - The face value needs be zigzag32 and not varint Changed position from BlockCoordinates to vec3i in packet_player_auth_input.input_data.block_action (proto.yml) - The y value for position needs to be zigzag32 and not varint * Fixed types for packet_player_auth_input 1.19.x Changed block_position from vec3i to BlockCoordinates in TransactionUseItem (types.yml) - The y value for block_position needs to be varint and not zigzag32 - The face value needs be zigzag32 and not varint Changed position from BlockCoordinates to vec3i in packet_player_auth_input.input_data.block_action (proto.yml) - The y value for position needs to be zigzag32 and not varint * Fixed types for packet_player_auth_input 1.20.x Changed block_position from vec3i to BlockCoordinates in TransactionUseItem (types.yml) - The y value for block_position needs to be varint and not zigzag32 - The face value needs be zigzag32 and not varint Changed position from BlockCoordinates to vec3i in packet_player_auth_input.input_data.block_action (proto.yml) - The y value for position needs to be zigzag32 and not varint * Fixed types for packet_player_auth_input 1.16.x
- Loading branch information
1 parent
8f1ba18
commit f00c2cc
Showing
63 changed files
with
208 additions
and
208 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.