Jump to content

[1.7.10][SOLVED] IMessage DecoderException


Recommended Posts

I am trying to send a packet from server to player using an IMessage and SimpleNetworkWrapper, however, whenever it tries to send the packet it gives me this exception:


`io.netty.handler.codec.DecoderException: java.lang.IndexOutOfBoundsException: readerIndex(8 ) + length(4) exceeds writerIndex(8 ): SlicedByteBuf(ridx: 8, widx: 8, cap: 8/8, unwrapped: UnpooledHeapByteBuf(ridx: 1, widx: 9, cap: 9/9))`


Does anybody know how would this exception raise for a simple packet send to player?

Link to comment
Share on other sites

Ok, I first should note that the message itself is supposed to do nothing but reply another message from client containing requested data, thus why it is called EmptyMessage, but I wrote an integer to the buffer to prevent IndexOutOfRangeException.


The class:

public class EmptyMessage implements IMessage {

public EmptyMessage() {	}

public void fromBytes(ByteBuf buf) {

public void toBytes(ByteBuf buf) {


It is handled by this handler but I know it doesn't reach this code since I tried writing to output to no avail.


The handler:

public class EmptyMessagePlayerDataHandler implements IMessageHandler<EmptyMessage, PlayerDataMessage> {

public PlayerDataMessage onMessage(EmptyMessage message,
		MessageContext ctx) {
	return PlayerDataMessage.fromMinecraft(Minecraft.getMinecraft()); // This is in client


This is the way it is sent:

EmptyMessage message = new EmptyMessage();
Magematica.network.sendTo(message, (EntityPlayerMP) player); // On server side


This is the line in preInit:

network.registerMessage(EmptyMessagePlayerDataHandler .class, EmptyMessage.class, 2, Side.CLIENT);

Link to comment
Share on other sites

I'm guessing this is a bug, because whenever I send an empty message (with no value in them) then reply an exception is thrown at the reply message.

The exception, which is IndexOutOfRangeException, is thrown when it wants to read the reply message, so I'm guessing it is not resetting the reading index at the reply and it goes out of range when trying to read the data.

Link to comment
Share on other sites

I found out that the only solution for the time being is to send the reply packet as another packet, for anyone who wants to do this, remember to register the discriminator of the reply message to a different value than the request message.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...

Important Information

By using this site, you agree to our Terms of Use.