-
-
Notifications
You must be signed in to change notification settings - Fork 223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add bedrock 1.21.60 data #980
Conversation
@@ -3523,7 +3535,7 @@ packet_item_registry: | |||
!id: 0xa2 | |||
!bound: client | |||
# `items` holds a list of all items. | |||
items: ItemData[]varint | |||
itemstates: Itemstates |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this correct? The official docs say there are additional fields (version
and nbt
)
Hence why I made the new type, though I see now I could've just added the new fields to the ItemStates type
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the overall structure did not change minus inserting some new fields. Keeping the same name and structure is good for compatibility and simplifying implementation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean the two fields, version and nbt (gophertunnel and official docs)
These fields aren't present in the Itemstates
type in mcdata
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
192.168.197.195/25176 Deserialization failure for packet 0x91. Packet buffer saved in ./1739315504847_packetReadError.txt as buffer was too large (45570 bytes). |
Yes, any changes that are applicable to old versions, even to doc, should be applied to the old versions. So we don't have problems like in #948 from tech debt (I fixed the issues here). You can apply changes to old versions by using the "replace all" feature in your editor after putting in a subsection of the old data and then the new data under the replacement. |
LGTM |
when will it be gtg? After checks? |
The bedrock tests are going to fail here for now because there is a circular dep on PrismarineJS/bedrock-protocol#570. @CreeperG16 Ideally if there's a change that requires a bedrock-protocol update before supporting a version it's done in a PR there that doesn't bump the CURRENT_VERSION. Bumping CURRENT_VERSION means that it's a supported version so it can't be merged until mcdata PR is done (which also blocks this) |
/makerelease |
Thanks for letting me know, I'll make sure to keep that in mind in the future |
This PR is still a WIP, and Bedrock version 1.21.60 has not been released yet.
This PR adds packet and language data for Bedrock version 1.21.60
Protocol changes
Source for protocol changes: Official Protocol Documentation
Some notable packet changes:
itemstates
field ofStartGamePacket
has been replaced by a dedicated packet - the formerItemComponentPacket
has been renamed toItemRegistryPacket
and repurposed for this.itemRegistryPacket
, to help with implementing this new behaviour in packages such as bedrock-protocol and prismarine-registry.CreativeContentPacket
got a major restructure to allow organising custom items into their own groups in the creative inventory (like wool, logs, decorative stone in vanilla)Additionally, some enums got new members, but as the official documentation doesn't document entire enums, only new members, they are most likely placed at wrong values in this PR. I'll fix or revert them once I have more information.
Additional documentation of packet fields
Many new documentation comments were added to mojang's official protocol docs in this update, so I have copied some of them to their places in minecraft-data. However, I assume these comments need to be added to all versions of the protocol yaml files, which I will do (or revert if it proves too much work) once I get confirmation of this fact.
Language data
Language data was extracted from the preview BDS vanilla resource pack files.