You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of version 764 (Minecraft 1.20.2) of the protocol, top-level compound tags sent to clients from the server will omit the "name" field altogether, including the two-byte prefix for the string length, which was typically present, even when empty.
Though untested, I don't see how this won't break things, and an additional option will need added to determine if the name should even attempt to be read when decoding tags from a network stream. It seems Microsoft feels-compelled to add another level of complexity and variation to a simplistic format to save two-bytes of network traffic.
The text was updated successfully, but these errors were encountered:
As of version 764 (Minecraft 1.20.2) of the protocol, top-level compound tags sent to clients from the server will omit the "name" field altogether, including the two-byte prefix for the string length, which was typically present, even when empty.
Though untested, I don't see how this won't break things, and an additional option will need added to determine if the name should even attempt to be read when decoding tags from a network stream. It seems Microsoft feels-compelled to add another level of complexity and variation to a simplistic format to save two-bytes of network traffic.
The text was updated successfully, but these errors were encountered: