DefineOutside
DefineOutside
I prefer the following scenario for the one time to use optional over null, but it breaks convention: - Optional.empty() if not sent on a version but it exists on...
A more user proof method would be to throw an exception if the field doesn't exist on the server version like PE 1.8 did
 Potentially related to this
I did mean WrapperPlayServerPlayerInfo, updating the title
I'm saying, if 1.19.3 is released with no protocol changes, it will resolve to 1.19 instead of 1.19.3 and break things. It should resolve to 1.19.2 instead.
what exactly needs to be done here? I know this part of the minecraft codebase and have reimplemented this before.
The vanilla client writes and reads this as a byte, not an unsigned byte. The ViaRewind mappings are correct
I've designed a modern block data system in PacketEvents. It allow stuff like WrappedBlockState stairs = StateTypes.OAK_STAIRS.createDefaultState(); stairs.setFacing(BlockFace.WEST) https://github.com/retrooper/packetevents/blob/2.0/api/src/main/java/com/github/retrooper/packetevents/protocol/world/states/WrappedBlockState.java https://github.com/retrooper/packetevents/blob/2.0/api/src/main/java/com/github/retrooper/packetevents/protocol/world/states/type/StateTypes.java Unsure how relevant this is, but it works on 1.8...
https://github.com/retrooper/packetevents/issues/325
good luck getting 1.8 users to follow licenses. especially when the project uploads mojang's entire codebase onto github