Geyser is giving invalid data to server, causing players to lose their entire inventory about geyser HOT 6 CLOSED

Player is using a Samsung Note 9 if that helps.

from geyser.

The errors you've sent in the log are irrelevant debug errors, and not related to this issue. Generally speaking, Geyser does not modify the inventory. As for server versions: 1.20.80 Bedrock is not "newer" than 1.20.4 Java. Geyser currently emulates a 1.20.4 java client, while supporting Bedrock client versions 1.20.40-1.20.80. Regardless of which Bedrock client version is used to connect to the server, Geyser will emulate a 1.20.4 Java client, and that's what the Java server then sees.

You should turn off the debug mode in Geysers config, and check your logs for actual errors/that crash you mentioned

from geyser.

Debug is off. The websocket closing is being treated like a proxy-side crash by the server (it temporarily disconnects Geyser). While it may be emulating a 1.20.4 client, it is still a Bedrock connection.

This still does not explain why when the update first dropped, it caused chunk version errors that prevented the server from starting. That's not the point of this bug, though.

There are no other errors associated with these events. The server host dev team has not heard of this issue before, so I was hoping this might be something that the Geyser team may have run across in the past. I guess I'll have to keep cheating him his loot again and again.

from geyser.

https://github.com/GeyserMC/Geyser/blob/master/core%2Fsrc%2Fmain%2Fjava%2Forg%2Fgeysermc%2Fgeyser%2Fskin%2FFloodgateSkinUploader.java
That error is related to skin uploading, nothing else. If something is crashing your server, you should check your crash logs or similar, because this certainly isn't it..

As for chunk version errors: That's entirely server-side, and could be caused by a newer world (e.g. 1.20.4) being loaded on an older server (e.g. 1.20.2). Those are not related to Geyser at all.

What would help narrow the issue down would be a full server log - the snippet you've provided aren't errors that could crash the server

from geyser.

There are no other errors in the logs. The server runs perfectly fine otherwise. The logs have been overwritten by now anyway since the server is fairly busy.

from geyser.

In that case, please open a new issue once you have any error in the log related to that/proper reproduction steps. Geyser does not modify Java server behavior, so this is likely an issue with a different plugin.

from geyser.