0.1.11: Packet 0/41 was larger than expected
sir-vancelot opened this issue ยท 5 comments
Description
After upgrading 0.1.9 to 0.1.11 I can no longer connect to my server. I get this connection lost error:
[19:16:40] [User Authenticator #5/INFO] [minecraft/ServerLoginPacketListenerImpl]: UUID of player Sir_Vancelot is ef64bb68-9ef1-49d4-905f-2c48778fac6f
[19:16:52] [Server thread/INFO] [minecraft/PlayerList]: Sir_Vancelot[/192.168.86.230:56932] logged in with entity id 19994 at (-286.03113457952014, 64.0, 356.581795681503)
[19:16:52] [Server thread/INFO] [ModdingLegacy/blue_skies/]: Sending ToolHandleTypeManager to Sir_Vancelot
[19:16:52] [Server thread/INFO] [ModdingLegacy/blue_skies/]: Sending SnowcapOvenFreezingManager to Sir_Vancelot
[19:16:52] [Server thread/INFO] [ModdingLegacy/blue_skies/]: Sending HorizoniteForgeFuelManager to Sir_Vancelot
[19:16:52] [Server thread/INFO] [ModdingLegacy/blue_skies/]: Sending AlchemyRecipeManager to Sir_Vancelot
[19:16:52] [Server thread/INFO] [ModdingLegacy/blue_skies/]: Sending JournalEntryManager to Sir_Vancelot
[19:16:52] [Server thread/INFO] [ModdingLegacy/blue_skies/]: Sending JournalSectionManager to Sir_Vancelot
[19:16:52] [Server thread/INFO] [ModdingLegacy/blue_skies/]: Sending JournalRequirementManager to Sir_Vancelot
[19:16:52] [Server thread/INFO] [minecraft/MinecraftServer]: Sir_Vancelot joined the game
[19:16:52] [Server thread/INFO] [Jade/]: Syncing config to Sir_Vancelot (ef64bb68-9ef1-49d4-905f-2c48778fac6f)
[19:16:56] [Server thread/INFO] [minecraft/ServerGamePacketListenerImpl]: Sir_Vancelot lost connection: Disconnected
[19:16:56] [Server thread/INFO] [minecraft/MinecraftServer]: Sir_Vancelot left the game
Other Notes:
- I can still connect to my 0.1.9 server
- Others can connect to my 0.1.11 server
- I have tried:
--ipconfig /flushdns
-- Restarting my machine
-- Reinstalling ATM9 versions 0.1.11 and 0.1.9
I am able to rejoin if I remove my player data from the server. Likely some item in my player inventory that ended up corrupted I'm guessing.
I tried logging in as a fresh player who has never been on the server before, still had the same issue. But a fresh world had no problems.