Invalid packet ID 118 due to large packets?

[Kinniken]

Hi guys,

 

Does anyone know what could cause a "bad packet ID 118" error on the client? I'm getting that in a new dev release of Millénaire. It seems to be triggered by a new packet type I've added (in my usual channel), that can include up to 30-40k of data (it's a packet sending missing content to the client if need be on login, i.e. for most players it will never get sent and when it is it will be once only, so the size shouldn't be an issue). Any ideas?

 

Thanks

 

K.

[atrain99]

118 for a packet id may be something you don't want?

No ideas other than that.

[calclavia]

Try a smaller packet ID?

[LexManos]

To quote: http://dinnerbone.com/blog/2012/01/13/minecraft-plugin-channels-messaging/

On a packet scale, this is pretty simple. The packet ID is 250 (0xFA), and the format is as follows:

 

String,        // Plugin Channel - something unique to the mod and this type of message. 16 chars max.

int,            // Message Length - length of the message, must be below short.MAX_LENGTH (32,767).

byte[]          // Plugin Message - the message itself, whatever it may be.

.... It has a pretty strict max length.

Don't go over it. If you do, split it into multiple packets and recombine it on the other side.

 

[Kinniken]

Thanks Lex, I was almost sure it was a length issue but hadn't been able to find the actual limit or even if it was a a "hard" limit.

 

It's a bit annoying, restructuring my packet around that limit will be tricky, but at least I know what I have to do now.