packet id shorthands about node-minecraft-protocol HOT 6 CLOSED

That's a good idea. BTW, that site is just a mirror of the actual wiki, which is at http://wiki.vg.

from node-minecraft-protocol.

Wow, that was unexpectedly fast!

You're right there, thanks.

from node-minecraft-protocol.

We did this in a previous version of this project, and surprisingly it's actually easier to use the hex codes instead of enum values, for 2 reasons:

• over time and minecraft updates, packet names change or become less descriptive, and you have to change the enum names, breaking backwards incompatibility. in other words, the numbers are more stable than the names
• for a lot of packets, the names are misnomers anyway because the minecraft protocol is so fucked up. numbers remind you that you never know what a packet might be used for...

I'll keep my mind open, but I actually did think about this and decided that it's easier for everybody not to provide an enum.

from node-minecraft-protocol.

Hm, haven't been actively watching the protocol. Are the changes really that drastical? And I thought Minecraft was matureing. Haha.

Their protocol is fucked up indeed.

from node-minecraft-protocol.

It wouldn't be too hard to implement this on the script-side instead of library-side anyway, with only the relevant packets. I believe it's better this way.

from node-minecraft-protocol.

Yeah, convinced. Protocol is low level and acts as a bridge from the raw protocol to an abstraction layer. Abstracting scripts need to be modified on protocol updates anyways.

from node-minecraft-protocol.