Vito Gamberini

> I'm using Windows 8.1 and prebuilt binaries are not supplied, neither is it using GNU toolchains. Point is we need a solution to force a compiler. First off this...

1.8 data is all hand entered, and suffers from copy-paste mistakes Just a matter of someone caring enough to bang out corrections

Is this burger or something inherent to the updater? My spidey sense says Burger

The protocol is correct. This is likely a bug in the `TopBitSetArray` implementation of NMP. Keeping this open in case I'm wrong, but right now there is no indication of...

For reference, this is the relevant encoding function from MC: ```java public void write(FriendlyByteBuf friendlyByteBuf) { friendlyByteBuf.writeVarInt(this.entity); int n = this.slots.size(); for (int i = 0; i < n; ++i)...

Excellent work on this and congrats on test passing, I'm going to take a minute to review before giving my :heavy_check_mark:

Give me two seconds, I'll update mcd and we can just do the right thing in one fell swoop

As extremeheat already said, protocol needs to be updated before anything else can happen. It's not hard or complicated, it's just labor. Typically 1-2 hours of transcribing the protocol and...

What's the status on this? ProtoDef says that ProtoDef-native varints shouldn't be longer than 5 bytes but Minecraft Varlongs can be up to 10 bytes. Right now minecraft-data is incorrectly...

Because if minecraft passes a negative number as a 32-bit varint and it's decoded as a 64-bit varlong you'll have a positive number. If you just assume everything is a...