I died trying to get back through our nether-portal to our base after getting caught on fire by some lava and I think I almost got through but now when-ever I try to login it gives me this error code. When I died in-game, I could not click the respawn button or the title menu button. They would just keep flashing and not be receptive to input.
I don't know why this is happening and I fear I may not be able to play on this realm anymore. I have a lot of fun on it.
You can indeed try deleting your character file, something is corrupted with that or with the location you spawn in the world. So you can try both deleting you player file and checking your specific location in the world with a program like MCEdit.
I'm getting an error of
"Internal Exception: io.netty.handler.codec.DecoderException:java.lang.IndexxOutOfBounds Exception: readerIndex(35) + length (8) exceeds writerIndex(36): UnpooledHeapByteBug(ridx: 35, widx: 36, cap: 36)"
I died trying to get back through our nether-portal to our base after getting caught on fire by some lava and I think I almost got through but now when-ever I try to login it gives me this error code. When I died in-game, I could not click the respawn button or the title menu button. They would just keep flashing and not be receptive to input.
I don't know why this is happening and I fear I may not be able to play on this realm anymore. I have a lot of fun on it.
Please help.
Sharker
Update: I tried getting my friend to kick me but that didn't work. I left the realm and got re-invited but that didn't work.
If your friend temporarily changes the world on his realm to something else, can you join it then?
It worked, so yeah, I'm pretty sure it's a problem with the map. Any way to fix? I'm thinking maybe get the server file and delete my char file.
You can indeed try deleting your character file, something is corrupted with that or with the location you spawn in the world. So you can try both deleting you player file and checking your specific location in the world with a program like MCEdit.
it worked, but it still seems like a weird bug.
Glad to hear it's fixed.