MC-111BlockChange(0x3E), crash client if unknown block id is used.
Sending a Block Change packet with any blockid other than the currently implemented ones cause the client to crash.
Example: block id 146
Environment
java version "1.7.0_07"
OpenJDK Runtime Environment (IcedTea7 2.3.2) (7u7-2.3.2a-1ubuntu1)
OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode)
Attachments1
Created Issue:
BlockChange(0x3E), crash client if unknown block id is used.
Sending a Block Change packet with any blockid other than the currently implemented ones cause the client to crash.
Example: block id 146Environment
java version "1.7.0_07"
OpenJDK Runtime Environment (IcedTea7 2.3.2) (7u7-2.3.2a-1ubuntu1)
OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode)
Attachments1
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
I don't understand why this is an issue? Surely in a vanilla server, it will only send changes about blocks both it and the client has? Or have you managed to reproduce this via entirely vanilla means?
The bug is about the client crashing, many times one can send bad packets to a vanilla client that makes it disconnect from the server with an error message, that is OK.
However the vanilla client should never crash caused by correctly structured data but unknown values.
Also since the extra 4 bits were added to the map format that will in the future allow for a lot more blocks than build into the vanilla client I assume it must be able to handle unknown types.
I have only done testing towards the client, but the nature of the bugs makes indicates that similar bugs could be found server side. So finding the core issue here would probable help.
The core issue is that the server and client are extremely naive. If this problem exists in the server please let us know, this right now on the client matters little.
As I said in your other, similar bug report - "While I appreciate the vigor, unless it happens in vanilla and can be caused in vanilla, it isn't really a bug. The client side doesn't need to be robust enough to handle these issues, as they will never happen. If a client could trigger this behaviour on the server side though, then I would be worried." I'll leave it to Mojang to decide what to do with this report, however.