deab6a0 Don't allocate bufs in 1.18/1.20 chunk types Unlike Mojang, we don't sneak a byte array of data outside of the actual packet reading, so there's no reason to not just use the original buffer. Slicing doesn't allocate anything while also setting the reader index correctly, as also used in the previous types
Lots of fixes, mostly to edge case data handling, and some more to older versions!
- Fixed items with block predicates causing disconnects for creative mode clients in 1.21->1.21.2 (by EnZaXD)
- Fixed errors from level 0 enchantments in 1.21->1.21.2
- Fixed painting entity data in 1.21->1.21.2
- Fixed opening chest boat inventories causing disconnects in 1.21->1.21.2
- Fixed boat types in 1.21->1.21.2 (by EnZaXD)
- Fixed item_name<->default name priority for items in 1.21->1.21.2 (by EnZaXD)
- Fixed some issues with item hover event displays in 1.20.5 and 1.21.2 (by EnZaXD)
- Fixed handling of empty lock codes in 1.21->1.21.2, usually sent by older servers (by valaphee, EnZaXD, kennytv)
- Fixed possible anticheat issues by dropping idle packets where only horizontal collision changed in 1.21->1.21.2 (by EnZaXD)
- Fixed empty custom data tags sometimes being removed with creative clients on 1.20.5/1.21 (by EnZaXD)
- Send enabled features packet in config phase for clients that have it in 1.19.1->1.19.3 (by EnZaXD)
- Fixed handling of block entity custom names in 1.12->1.13 (by EnZaXD)
- Fixed chunks possibly being invisible on 1.8 servers and older (by RK_01)
- Fixed some edgecase area effect cloud particle errors on older servers
- 1.21.2+ clients on 1.8 servers now get proper sword blocking animations through consumable item data (by RK_01)
If you want to get larger version updates early, consider supporting me via https://viaversion.com/donate. See the previous update notes for more info.