Network Protocol Error - Fabric 1.21.1
ErinaSugino opened this issue ยท 5 comments
I cannot say with 100% certainty that it is this mod which caused it, however considering the issue started after a player died, affected their death chunk only and seemingly went away after restoring, deleting their grave with moderator command menu AND restarting the server, I feel like it's a safe guess to ask here anyway.
Fabric 1.21.1 (with an expanded Cobblemon 1.6 modpack, full modlist available if needed).
Player died, chunk became a crash trap as any player rendering it client sided would immediately disconnect with a "Network Protocol Error" kick message (nothing more than that). Debug log states Lithium complains about "Missing Palette entry for index 10", probably pointing towards chunk data block palette.
After updating Lithium (and the FabricAPI), error changed to "No value with id 45775".
After restoring and deleting the source player's latest grave, then restarting the entire server, issue seems to have gone away.
First disconnect debug log - Older version of Lithium & FabricAPI
Second disconnect debug log - Newer version of Lithium & FabricAPI
Main log file - No crash, just a forced disconnect from the server; but the same error as in the above detailed debug logs is found here at line 863. Newer Lithium & FabricAPI version.
Can you send me a copy of the logs during which the player is kicked/crashed?
If a crash log is generated, it'd be great if you could send that too
Update: Another occurence.
The common denominator between both instances is that the person apparently died underwater. (Scrap that, third occurence was not in the water)
EDIT:
Current state of the affected world sector from the server.
Grave chunk is [18, 3] at Y: 3.
Older Lithium/FabricAPI log states "Missing palette entry for index 40"
r.-1.0.zip
EDIT 2:
After restoring the grave contents to the user, even when trying to force load the affected chunk to trigger grave block deletion/reversion, a full server restart is required to fix the issue.