Robin Lambertz

So after some talking with @rom1504 here's one possible idea : abstract away all the things. `protocol.json` would only contain unbiased data extracted from `protocol.json` : packetId, and types. Packet...

The only datatype that needs naming is containers (the top-level "fields" being a container as well). Switch fields don't need to be named. So I guess we could do something...

I really, really don't like the idea of using wiki.vg packet names. They aren't meant to be set in stone, and can be changed by anyone anyday. The packet names...

This is an open ticket for a reason. I agree this needs discussion with the community at large. Do you think we should handle this kind of discussion differently ?...

@nickelpro the problem with this is, take a look at what happened in 1.9 : every packet changed ID, because someone at mojang thought it'd be a fun idea to...

Making another file for this is overkill. But clearly that info deserves to be in the protocol definition. I think just making that field into a mapper might be a...

ProtoDef aims to be a generic binary protocol description. You feed it a Json and it will give you a simple way to serialize/deserialize those packets. ProtoDef implementations are able...

The original idea was for sand and gravel, but all those data would be useful to have too :D

instead of minecraft-assets, maybe we should just have a texture pack loader ? It would avoid the legal problems, give the possibility of using free alternatives, and avoid the whole...

Lol. This was the way I originally wanted to handle the protocol data, and after a long argument with... erm, either myself or you " ? I opted to go...