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 title says, protocolize is not compatible with Velocity proxy and MC 1.20.3+ clients due a new implementation in the client protocol that requires inventory titles to be serialized as NBT.
Protocolize is aware of this issue (see Exceptionflug/protocolize#211), but unfortunately, Protocolize is unable to fix this issue as of now because there is not way to serialize a component (adventure) to NBT, anyway, adventure is aware of this feature lack (see KyoriPowered/adventure#995).
As of now, I cannot do anything to fix this issue, until adventure introduces a way to serialize a component to NBT and Protocolize brings an update to handle this change.
NOTE: This issue does not affect BungeeCord proxy, only Velocity.
Temporal workaround:
Disable the GUI feature from enhanced-glist configuration if you are affected by this issue.
The text was updated successfully, but these errors were encountered:
Description of the problem:
As title says, protocolize is not compatible with Velocity proxy and MC 1.20.3+ clients due a new implementation in the client protocol that requires inventory titles to be serialized as NBT.
Protocolize is aware of this issue (see Exceptionflug/protocolize#211), but unfortunately, Protocolize is unable to fix this issue as of now because there is not way to serialize a component (adventure) to NBT, anyway, adventure is aware of this feature lack (see KyoriPowered/adventure#995).
As of now, I cannot do anything to fix this issue, until adventure introduces a way to serialize a component to NBT and Protocolize brings an update to handle this change.
NOTE: This issue does not affect BungeeCord proxy, only Velocity.
Temporal workaround:
Disable the GUI feature from enhanced-glist configuration if you are affected by this issue.
The text was updated successfully, but these errors were encountered: