Protocol 2193 clients never render system chat (all Floodgate-origin chat invisible) on b1243

[zsciallo]

Describe the bug

On Geyser 2.11.3-b1243, Bedrock clients connected with protocol 2193 never render chat
delivered as ClientboundSystemChatPacket. Signed Java player chat
(ClientboundPlayerChatPacket) renders correctly on the same client, in the same session.

Because Floodgate players cannot sign chat, 100% of Bedrock-origin chat reaches other clients
as system chat. The practical result is that a player on 2193 never sees a single message from
any other Bedrock player, while Java players' messages appear normally.

Bedrock clients on 2168, 2169 and 1001 connected to the same server at the same time render
both kinds correctly, so this is specific to 2193.

Observed over one session (chat messages sent per Bedrock player, by protocol):

player	protocol	messages sent
A	2168	9
B	2169	5
C	2169	1
D	2193	1 ("test")
E	2193	0
F	2193	0
G	2193	0

Every Bedrock player who held a conversation was on 2168/2169. Every 2193 player was silent.
The 2168 player visibly answered questions that were only asked in chat, confirming they were
receiving system chat fine.

Across a larger sample the signature split is exact — Bedrock senders 933 unsigned / 0 signed,
un-nicknamed Java senders 741 signed / 0 unsigned — so sender platform, not any chat plugin,
is what determines which path a message takes.

This is not fixed by the v2193 codec update in 4c345fb / d12a0ef. Those did resolve the
`SetPlayerFurnaceOptionsPacket was sent to SERVER inss on the
same clients — that error is now gone, and this chat

Possible starting point: JavaSystemChatTranslator / TextPacket.Type.SYSTEM.

To Reproduce

1. Run Geyser-Spigot 2.11.3-b1243 with Floodgate on a Paper 26.2 server.
2. Join with Bedrock client A on protocol 2193 (26.50 / 26.51).
3. Join with Bedrock client B on any earlier version (e.g. 2169).
4. Send a chat message from B — A does not see it. (B and all Java players do.)
5. Send a chat message from a Java client — A does see it.
6. Reconnect A on 2169 instead and repeat — A now sees everything.

Expected behaviour

A Bedrock client on protocol 2193 should render system chat the same way clients on 2168/2169
do. Chat from other Bedrock players should appear, rather than being silently dropped.

Screenshots / Videos

No response

Server Version and Plugins

This server is running Paper version 26.2-87-main@a95ae8d (2026-07-28T22:11:27Z) (Implementing API version 26.2.build.87-stable)

Geyser Dump

No response

Geyser Version

Build #1243 · 9/16/2026

Minecraft: Bedrock Edition Device/Version

No response

Additional Context

No response

[zsciallo]

Update, think I was able to find some useful information.
MessageTranslator.handleChatPacket sets setXuid(sender's xuid) for Bedrock-origin (Floodgate) senders and "" for Java senders
Maybe this is fine for older versions but is causing the newer version to silently drop? Basically it's setting the uuid to the recievers uuid not the senders if I am understanding correctly.