Can’t see chat messages on Bedrock 1.19
Describe the bug
Hi, I was wondering if I could troubleshoot here:
I am experiencing an issue wherein I can’t see any chat messages or announcements (someone died or joined the server) from other players, even while the chat is open.
I can still send commands, but this appears to be only a problem for me as one of the Bedrock players on the server.
My theory is the reason either might be 1.19 or GeyserMC.
My Specs:
- OS: iPadOS
- iOS Version: 15
- Server Hosting: Aternos
- Geyser and Server Version: 1.19
- Minecraft Launcher Version and Edition: 1.19 & Bedrock
To Reproduce
-
Create an Aternos Java Edition Server with the following plugins (All Latest Versions) A. Chunky B. SkinsRestorer C. GeyserMC D. HuskHomes E. SleepFixer F. LightPerms
-
Open the server with an iPad iOS version 15 with Bedrock edition.
-
See if the chat works with other players.
Expected behaviour
When joining the server, I am still able to run commands, but I am unable to see any kind of messages from any other players.
Whether it’s them chatting or server announcements such as a death message if they get killed by any mob.
Screenshots / Videos
No response
Server Version and Plugins
No response
Geyser Dump
No response
Geyser Version
1.19
Minecraft: Bedrock Edition Device/Version
1.19, iPadOS
Additional Context
No response
Try without LightPerms? This sounds like something permissions-wise is getting in the way.
Any info on this issue? :)
Maybe same problem?
iOS 15.6, Minecraft BE 1.19.11, Minecraft JE Server 1.18.2 (Purpur).
All messages from chat and Toast announcements were displayed in key name like chat.player.txt
Maybe localization file corrupted? But other information like authenticate screen are normal.
Same issue on my server. I run GeyserMC on the proxy while floodgate on the backend servers. One of my backend server's chats is working fine, however. But, after moving all plugins from the server with working chat to the server with broken chat, the issue persists.
It seems like every time a chat message is recieved/sent, this error occurs:
Packet Error
[11:30:14 WARN] [geyser]: Downstream packet error! invalid click action: [11:30:14 ERROR]: com.google.gson.JsonParseException: invalid click action: [11:30:14 ERROR]: at net.kyori.adventure.text.serializer.gson.IndexedSerializer.read(IndexedSerializer.java:58) [11:30:14 ERROR]: at com.google.gson.TypeAdapter$1.read(TypeAdapter.java:199) [11:30:14 ERROR]: at com.google.gson.Gson.fromJson(Gson.java:991) [11:30:14 ERROR]: at net.kyori.adventure.text.serializer.gson.StyleSerializer.read(StyleSerializer.java:124) [11:30:14 ERROR]: at net.kyori.adventure.text.serializer.gson.StyleSerializer.read(StyleSerializer.java:49) [11:30:14 ERROR]: at com.google.gson.TypeAdapter$1.read(TypeAdapter.java:199) [11:30:14 ERROR]: at com.google.gson.Gson.fromJson(Gson.java:991) [11:30:14 ERROR]: at com.google.gson.Gson.fromJson(Gson.java:1062) [11:30:14 ERROR]: at com.google.gson.Gson.fromJson(Gson.java:1034) [11:30:14 ERROR]: at net.kyori.adventure.text.serializer.gson.ComponentSerializerImpl.read(ComponentSerializerImpl.java:214) [11:30:14 ERROR]: at net.kyori.adventure.text.serializer.gson.ComponentSerializerImpl.read(ComponentSerializerImpl.java:56) [11:30:14 ERROR]: at com.google.gson.TypeAdapter$1.read(TypeAdapter.java:199) [11:30:14 ERROR]: at com.google.gson.internal.bind.TypeAdapterRuntimeTypeWrapper.read(TypeAdapterRuntimeTypeWrapper.java:41) [11:30:14 ERROR]: at com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.read(CollectionTypeAdapterFactory.java:82) [11:30:14 ERROR]: at com.google.gson.internal.bind.CollectionTypeAdapterFactory$Adapter.read(CollectionTypeAdapterFactory.java:61) [11:30:14 ERROR]: at com.google.gson.Gson.fromJson(Gson.java:991) [11:30:14 ERROR]: at net.kyori.adventure.text.serializer.gson.ComponentSerializerImpl.read(ComponentSerializerImpl.java:173) [11:30:14 ERROR]: at net.kyori.adventure.text.serializer.gson.ComponentSerializerImpl.read(ComponentSerializerImpl.java:95) [11:30:14 ERROR]: at net.kyori.adventure.text.serializer.gson.ComponentSerializerImpl.read(ComponentSerializerImpl.java:56) [11:30:14 ERROR]: at com.google.gson.TypeAdapter$1.read(TypeAdapter.java:199) [11:30:14 ERROR]: at com.google.gson.Gson.fromJson(Gson.java:991) [11:30:14 ERROR]: at com.google.gson.Gson.fromJson(Gson.java:956) [11:30:14 ERROR]: at com.google.gson.Gson.fromJson(Gson.java:905) [11:30:14 ERROR]: at com.google.gson.Gson.fromJson(Gson.java:876) [11:30:14 ERROR]: at org.geysermc.geyser.text.GsonComponentSerializerWrapper.deserialize(GsonComponentSerializerWrapper.java:66) [11:30:14 ERROR]: at org.geysermc.geyser.text.GsonComponentSerializerWrapper.deserialize(GsonComponentSerializerWrapper.java:40) [11:30:14 ERROR]: at com.github.steveice10.mc.protocol.codec.MinecraftCodecHelper.readComponent(MinecraftCodecHelper.java:271) [11:30:14 ERROR]: at com.github.steveice10.mc.protocol.packet.ingame.clientbound.ClientboundSystemChatPacket.
I don't think there's anything we can do about that - that's a bug we fixed in Adventure, but it hasn't been pulled into a release yet, so Velocity is still bugged. You can change back to standalone for now, or I believe VentureChat is the offending plugin here.
I don't think there's anything we can do about that - that's a bug we fixed in Adventure, but it hasn't been pulled into a release yet, so Velocity is still bugged. You can change back to standalone for now, or I believe VentureChat is the offending plugin here.
I see. I doubt it's VentureChat, though, as it works fine for one of the backend servers I mentioned.
I don't think there's anything we can do about that - that's a bug we fixed in Adventure, but it hasn't been pulled into a release yet, so Velocity is still bugged. You can change back to standalone for now, or I believe VentureChat is the offending plugin here.
I see. I doubt it's VentureChat, though, as it works fine for one of the backend servers I mentioned.
Haha, I was wrong. It was VentureChat. I forgot to check if the config files were exactly the same. And there was a difference. Updating VentureChat to 1.19 resulted in the config's jsonformatting section (the part that handled hover and click actions) to change.
The error was, literally, an invalid click action caused by misconfiguration. 😅
Ill close this issue since its patched.