@superjoe30 I don't see how how they are misleading ? The protocol now indexes packets using state and ID. I wanted to avoid using a string directly because they felt awkward (client.on("play,0x02") felt eaky) and settled to create a states enumlike so if you are to "mistype", you'd get a runtime error rather than no error at all (e.g. listening to a non-existant event).

Sure, creating special events for the few (5 ?) packets that aren't part of the PLAY state would work, but for one it feels like a lot of boilerplate for not much gain in the end ?

I wanted to have a system that is future proof. If we go for special event names, potential future changes to minecraft protocol might force us to crop up more "special events". Besides, the states enum is here in case mojang decides to add more states to the current protocol (unlikely, but not impossible either).

Of course, if you still prefer to have specially named packets, I'll just go ahead and do it. It just doesn't feel right to me.