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
Create a Component with a HoverEvent.showEntity().
send it to a player connected to the proxy by player.sendMessage().
The client of the player show the component in the chat correctly with the hover event.
Actual Behavior
Immediately after the message is sent. The client unexpectedly disconnected with a reason of internal exception occurred: JsonSyntaxException: Missing type, expected to find a string
The client minecraft version is 1.20.1. Possible reason of this bug may be the PR #1564 that introduces support for new hover event schema in 1.21.5 controlled by JSONOptions.EMIT_HOVER_SHOW_ENTITY_KEY_AS_TYPE_AND_UUID_AS_ID. This option is FALSE by default which means it has to be explicitly set to true in the OptionSchema. However in the com.velocitypowered.proxy.protocol.ProtocolUtils only MODERN_SERIALIZERset that option to false explicitly , leaving all other serializers use the default value false, which may cause all versions prior to 1.21.5 to encounter same problem because the type key is missing.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Expected Behavior
HoverEvent.showEntity()
.player.sendMessage()
.Actual Behavior
Immediately after the message is sent. The client unexpectedly disconnected with a reason of internal exception occurred:
JsonSyntaxException: Missing type, expected to find a string
Steps to Reproduce
Plugin List
Only my plugin on the velocity and no plugins on the backend server.
Velocity Version
Additional Information
The client minecraft version is
1.20.1
. Possible reason of this bug may be the PR #1564 that introduces support for new hover event schema in 1.21.5 controlled byJSONOptions.EMIT_HOVER_SHOW_ENTITY_KEY_AS_TYPE_AND_UUID_AS_ID
. This option is FALSE by default which means it has to be explicitly set to true in theOptionSchema
. However in thecom.velocitypowered.proxy.protocol.ProtocolUtils
onlyMODERN_SERIALIZER
set that option to false explicitly , leaving all other serializers use the default value false, which may cause all versions prior to 1.21.5 to encounter same problem because thetype
key is missing.The text was updated successfully, but these errors were encountered: