BUG | Unknown metadata type -4

[Ranzdo]

After testing BungeeCord I got this error that shut the client connection down. I know that a negative metadata type is impossible and after som debugging I found out.

• This happens when the server try to send a 0x18 packet to spawn a wolf (type 95)
• The problem occurs on the first byte when it starts to read the metadata. The full byte is -111
• It happens everytime i try to login to the server, so i think there is some wolf that the server want the client to spawn but the metadata is read incorrectly.

The strange thing is that the packet works for all the other entities and I looked at http://www.wiki.vg/Protocol#Spawn_Mob_.280x18.29 and the instructions seems in order.

There is somthing special about this packet and I think I will dive into NMS to find out, but I thought I let you know too.

[md-5]

Hmm the metadata parsing is probably wrong I shall cross reference with my previous implementation.

[md-5]

Attempted fix in latest MinecraftProtocolLib

[Ranzdo]

I spawned a wolf ingame before the last commit in MinecraftProtocolLib. It crashed the stream with the same error message so I was able to replicate the bug.

With the new commit it works however, so this bug is now fixed :).

The question is, why are mojang using an unsigned byte and at the same time use 127 as the "closeing" number? Shouldn't it be 255?

[md-5]

I'm not mojang, no clue.