Client Disconnect when opening Ender chest on a server
djnifos opened this issue ยท 9 comments
Client Log
https://mclo.gs/11k4dpD
Server Log with relevant line
https://mclo.gs/R3OGWwv#L7626
ATM10 modpack, the user is able to consistently reproduce if you need any other data.
Also happening to me... https://mclo.gs/50eZxOZ
Tried switching from Curseforge to Prism launcher as recommended, same issue
Happening for me too. I also opened an issue at the ATM10 Repo AllTheMods/ATM-10#1729
FWIW, the ATM team is live testing it right now and it seems like it's always reader 84 and writer 42
Caused by: java.lang.IndexOutOfBoundsException: readerIndex: 84, writerIndex: 42 (expected: 0 <= readerIndex <= writerIndex <= capacity(256)) at MC-BOOTSTRAP/[email protected]/io.netty.buffer.AbstractByteBuf.checkIndexBounds(AbstractByteBuf.java:112) ~[netty-buffer-4.1.97.Final.jar%23103!/:4.1.97.Final] at MC-BOOTSTRAP/[email protected]/io.netty.buffer.AbstractByteBuf.readerIndex(AbstractByteBuf.java:121) ~[netty-buffer-4.1.97.Final.jar%23103!/:4.1.97.Final] at TRANSFORMER/[email protected]/net.minecraft.network.FriendlyByteBuf.readerIndex(FriendlyByteBuf.java:734) ~[server-1.21.1-20240808.144430-srg.jar%23492!/:?] at TRANSFORMER/[email protected]/net.minecraft.network.FriendlyByteBuf.readerIndex(FriendlyByteBuf.java:70) ~[server-1.21.1-20240808.144430-srg.jar%23492!/:?] at MC-BOOTSTRAP/[email protected]/io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1097) ~[netty-buffer-4.1.97.Final.jar%23103!/:4.1.97.Final] at MC-BOOTSTRAP/[email protected]/io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:1087) ~[netty-buffer-4.1.97.Final.jar%23103!/:4.1.97.Final] at TRANSFORMER/[email protected]/net.minecraft.network.FriendlyByteBuf.writeBytes(FriendlyByteBuf.java:1339) ~[server-1.21.1-20240808.144430-srg.jar%23492!/:?] at TRANSFORMER/[email protected]/codechicken.lib.packet.PacketCustomChannel.lambda$onRegisterPayloadHandlerEvent$0(PacketCustomChannel.java:98) ~[CodeChickenLib-1.21.1-4.6.0.519.jar%23561!/:4.6.0.519] at TRANSFORMER/[email protected]/net.minecraft.network.codec.StreamCodec$1.encode(StreamCodec.java:25) ~[server-1.21.1-20240808.144430-srg.jar%23492!/:?] at TRANSFORMER/[email protected]/net.minecraft.network.protocol.common.custom.CustomPacketPayload$1.writeCap(CustomPacketPayload.java:40) ~[server-1.21.1-20240808.144430-srg.jar%23492!/:?] at TRANSFORMER/[email protected]/net.minecraft.network.protocol.common.custom.CustomPacketPayload$1.encode(CustomPacketPayload.java:47) ~[server-1.21.1-20240808.144430-srg.jar%23492!/:?] at TRANSFORMER/[email protected]/net.minecraft.network.protocol.common.custom.CustomPacketPayload$1.encode(CustomPacketPayload.java:29) ~[server-1.21.1-20240808.144430-srg.jar%23492!/:?] at TRANSFORMER/[email protected]/net.minecraft.network.codec.StreamCodec$4.encode(StreamCodec.java:81) ~[server-1.21.1-20240808.144430-srg.jar%23492!/:?] at TRANSFORMER/[email protected]/net.minecraft.network.codec.StreamCodec$5.encode(StreamCodec.java:97) ~[server-1.21.1-20240808.144430-srg.jar%23492!/:?] at TRANSFORMER/[email protected]/net.minecraft.network.codec.StreamCodec$5.encode(StreamCodec.java:87) ~[server-1.21.1-20240808.144430-srg.jar%23492!/:?] at TRANSFORMER/[email protected]/net.minecraft.network.codec.IdDispatchCodec.encode(IdDispatchCodec.java:53) ~[server-1.21.1-20240808.144430-srg.jar%23492!/:?]
I have been unable to reproduce this issue, I suspect It's something to do with multiple players being connected, perhaps?
I think I know the root cause though, can you please try this build of CCL and see if the issue is still present? https://maven.covers1624.net/io/codechicken/CodeChickenLib/1.21.1-4.6.0.520/CodeChickenLib-1.21.1-4.6.0.520.jar
We're finding it to be very much roulette, and definitely involving more than one player. We will put this on our test server and see what we can find, given the index is always doubled we're guessing it's failing to reset at some point.
The team is testing now if you want to join our discord we have a very active mod dev channel. https://discord.gg/allthemods if not they will respond here very soon
I don't want to dissuade you from joining the discord, we'd love to have you around, but it looks like the test build fixes this issue.