Muting chat on Bedrock no longer works.

[RealTriassic]

Hello, I'm currently using Geyser to allow Bedrock Edition players to connect to my Java Edition server.

Bedrock Edition has a feature for chat called chat muting that is supposed to hide all player messages.

With this plugin, Bedrock thinks that all messages are system messages (technically intentional behaviour).

My suggestion is maybe using the Floodgate API to allow normal player messages to be sent to Bedrock players instead of system messages like it is for Java? Make it a configuration option if possible?

Thanks.

[e-im]

I'll see about this for bedrock players, but it is only by chance that the same system on Java edition works. For Java edition, Mojang left in a legacy check that will classify messages as if they are from a player when they match the default chat format.

It is impossible to, while achieving the goal of this plugin, fully support all the chat options.

[MagmaSlime123]

I'll see about this for bedrock players, but it is only by chance that the same system on Java edition works. For Java edition, Mojang left in a legacy check that will classify messages as if they are from a player when they match the default chat format.

It is impossible to, while achieving the goal of this plugin, fully support all the chat options.

So is Geyser and Floodgate incompatible then?

[e-im]

No. It will work, you just won't be able to mute chat on Bedrock edition. Chat will always be shown.

This is a fixable issue, I just haven't gotten to it yet.

[MagmaSlime123]

Ah, alright.

[e-im]

I've attempted to fix this, but I'm not able to test if it actually works. I've attached a jar (in a zip file because GH does not let me upload a jar); if anyone can test it and let me know if it works, I'd appreciate it.

I haven't used the floodgate API for this, but instead looked for geyser in the netty channel pipeline. This is because I do not have a player/UUID yet at the time of injection and don't really want to check later/add a potentially unnecessary dependency.

FreedomChat-1.3.1-geyser-SNAPSHOT.zip

[MagmaSlime123]

@RealTriassic ^

[RealTriassic]

Really sorry that it's been a week, I'll try to get some time to test this tomorrow.

[e-im]

No worries. took me more than a month. whenever you get a chance

[RealTriassic]

Okay I did some testing by throwing it straight into the main server, it doesn't seem to be working unfortunately, I had my java account send messages in chat and my bedrock account receiving them still whilst having chat muted.

[RealTriassic]

Adding onto my previous message, there were no error logs or anything on console.

[JosTheDude]

Weird, generally, most chat plugins usually when having a mute chat feature just cancel the chatting event / packet and check for permissions, FreedomChat affecting it on Geyser and Floodgate is interesting.

[e-im]

The issue is not referring to any chat plugin, but instead (at least as far as I understand) disabling chat within the client on bedrock edition.

Java edition has a similar thing, but does not rely exclusively on different message types.
Bedrock, I assume, relies on the type of the message being Chat. Although, I'm a lot less familiar with bedrock and just derived that from wiki.vg. I haven't looked at the code, and tbh am not even sure how I could–– I don't know much about bedrock at all.

[pop4959]

@Tim203 If you don't mind, any idea if this could be possible? Perhaps we could manually send a Bedrock-compatible chat packet to other bedrock players while still re-writing as system chat for Java users?

I recently also made a change in 85496ab to help alleviate an issue where enabling secure chat for Java was pretty much impossible if you ran Geyser without breaking chat for Bedrock users.

[Tim203]

You've already gathered some input from another member of the team. The only thing I'd like to add to that is that you're currently only checking if the most significant bits are 0. This works for a big chunk of Bedrock players, but not the ones who are linked to Java. Those will use the UUID of the Java account. I recommend using the Floodgate API instead for full compatibility.