Describe the bug
Calling player.tell("") at any time causes the Bedrock client to disconnect. This is not limited to the onJoin event: the same behavior occurs from commands, timers, form callbacks, and other script callbacks.
The client displays Block and ClientDisconnection-90. The server process remains running and no server-side exception is reported.
Minimal reproduction
mc.listen("onJoin", (player) => {
player.tell("");
});The same result occurs when the call is moved to a command or timer.
Environment
- Minecraft Bedrock Client: 1.26.51 Windows GDK
- BDS: 1.26.51.1
- Protocol: 2193
- LeviLamina: 26.51.5
- LegacyScriptEngine: 0.22.2
- Script engine: QuickJS
- Connection: local LAN game
Actual behavior
Every player is disconnected shortly after the empty message is sent. The server log only shows the player connecting and disconnecting.
Expected behavior
An empty string should be ignored or rejected without sending a packet. It should not disconnect the client.
Comparison
player.tell("hello") works normally. Guarding the call with if (text.length > 0) fixes the issue.
Describe the bug
Calling
player.tell("")at any time causes the Bedrock client to disconnect. This is not limited to theonJoinevent: the same behavior occurs from commands, timers, form callbacks, and other script callbacks.The client displays
BlockandClientDisconnection-90. The server process remains running and no server-side exception is reported.Minimal reproduction
The same result occurs when the call is moved to a command or timer.
Environment
Actual behavior
Every player is disconnected shortly after the empty message is sent. The server log only shows the player connecting and disconnecting.
Expected behavior
An empty string should be ignored or rejected without sending a packet. It should not disconnect the client.
Comparison
player.tell("hello")works normally. Guarding the call withif (text.length > 0)fixes the issue.