Closed adalmo closed 3 months ago
Are you using Geyser with some sort of Bedrock proxy infront of it, such as e.g. WarerdogPE?
That's the only way I could explain why a Bedrock client is sending packets that it shouldn't send - the PlayerAuthInput packet should only be sent with server authoritative movement, which Geyser does not currently use. Alternatively, this could in theory also be sent by a modified client - in which case the player should be kicked for sending that.
If you're not using the former, when does this occur? In some specific cases such as some interaction? Please provide replication steps.
i am only using velocity-geyser and its just randomly happen sometimes it doesn't sometimes it does
Please send a full log via mclo.gs, not just a snippet
Okay, there are two occurrences of the error here, notably:
[09:23:42] [epollEventLoopGroup-4-9/INFO] [org.cloudburstmc.protocol.bedrock.netty.codec.packet.BedrockPacketCodec]: Failed to decode packet
org.cloudburstmc.protocol.bedrock.codec.PacketSerializeException: Error whilst deserializing SubClientLoginPacket(chain=[], extra=null)
[09:23:42] [epollEventLoopGroup-4-9/WARN] [geyser]: Client tried to send unused packet SubClientLoginPacket!
[09:23:42] [localSession-6-22/INFO] [geyser]: Dream36327 has disconnected from the Java server because of Invalid packet received!
This indicated that a console player tried to initiate a split-screen connection, which is currently not supported. The player did get kicked for that, as expected.
The second is the reported issue here:
This looks like a hacked client; since a vanilla client would not send PlayerAuthInputPackets when connected to a Geyser server as we currently use the client-auth movement system. The player is also kicked here for sending a packet that a vanilla client would not send.
The stacktraces are unfortunate, but we're waiting on https://github.com/CloudburstMC/Protocol/pull/229/ to get merged to resolve that - then the player will get kicked for sending an invalid packet, but it wont spam the console anymore.
https://github.com/GeyserMC/Geyser/commit/b7931f8d704f638273bb13215df0077fd144e049 resolves the giant stacktraces - kicking the players is generally intended, as noted in the comment above. Thanks for reporting though!
Describe the bug
To Reproduce
launch velocity with geyser and wait peoples to join on server and randomly show the error
Expected behaviour
i am not sure what's going on
Screenshots / Videos
Server Version and Plugins
git-Purpur-2176 (MC: 1.20.4)*
Geyser Dump
https://dump.geysermc.org/ooGBVbOtAWlGXp8PaVidHMXBgTU9xFnW
Geyser Version
Geyser version 2.3.1-SNAPSHOT (git-master-66f30a2)
Minecraft: Bedrock Edition Device/Version
No response
Additional Context
No response