: Client> at io.channelRead(MessageToMessageCodec.java:111) ~ : Client> at io.channelRead(MessageToMessageDecoder.java:99) ~ : Client> io.: : readerIndex(76) + length(1) exceeds writerIndex(76): SlicedByteBuf(ridx: 76, widx: 76, cap: 76/76, unwrapped: UnpooledHeapByteBuf(ridx: 1, widx: 77, cap: 77/77)) : Client> : FMLIndexedMessageCodec exception caught There is the report from the development console: This is not an unknown bug, I saw other people having the exact same issue. Completly removed ".minecraft"-folder and recreate everything
Used the JVM Argument "-Dforge.forceNoStencil=true" Reinstalled forge (also tried different versions from 1180 to 1189) I searched the forum for my error but I couldn't find a solution. As I already said, the Pixelmon support-team said, it's a forge issue. I searched for hours, what could cause this to happen. This bug appeared in all versions of pixelmon since 3.1 (since the mod support 1.7) and only when trying to send out a pokemon. I am using the orginal Minecraft Launcher (no cracked shit) and have a legal copy of the game. It just randomly give me this error and closes my world. It doesn't matter which pokemon I am sending out, which biome I am standing in, or which pokemon I want to battle.
This happens in Single Player and not always but frequently. Sometimes, when I am sending out a pokemon (throwing the pokeball), the game terminate my connection an give me the following message: "Connection Lost: A fatal Error has occured, this connection is terminated. So I hope you can help me (appologize for my bad grammatic, english is not my native language) I already tried to get help by the Pixelmon support-team, but they just said, it's a forge issue. I am using the Pixelmon Mod 3.2 and Forge 1180.
0 kommentar(er)
