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
Is your feature request related to a problem? Please describe.
We need to support the new protocol in order to support the new version
Describe the solution you'd like
Implement the new protocol specifications
Describe alternatives you've considered
N/A
Additional context
Network protocol
The client-bound player_chat packet now contains an index increasing for every message sent to the client.
The index starts at 0 when logging in (or is reset by configuration phase and the login packet).
For every message, the server should increment this value by 1.
If this value updates in an unexpected way, the client will disconnect.
As the protocol requires that every chat packet reaches the client in produced order, the goal is to enable faster detection of missed/reordered chat messages for custom server developers.
The server-bound chat and chat_command_signed packets now contain a checksum byte along with the 'last seen' update.
This is a simple hash of the 'last seen' signatures which should be reconstructed by the server, allowing quicker detection of de-synchronized state.
This can be passed as 0 to disable the check, for compatibility with protocol translation.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We need to support the new protocol in order to support the new version
Describe the solution you'd like
Implement the new protocol specifications
Describe alternatives you've considered
N/A
Additional context
Network protocol
player_chat
packet now contains an index increasing for every message sent to the client.login
packet).chat
andchat_command_signed
packets now contain a checksum byte along with the 'last seen' update.0
to disable the check, for compatibility with protocol translation.The text was updated successfully, but these errors were encountered: