Talk:Chunk Format

Actually the 0x33 Map chunk is still used by vanilla 1.4.6 server to send individual chunks; I'm seeing this packet in the protocol disassembly when the player is moving across chunk boundaries. I personally think the server sends 0x38 only when entering a world (start of session or transition to / from the Nether / End) and otherwise it sends 0x33 for each individual chunk that's coming into player's viewdistance. Xoft (talk) 09:51, 27 December 2012 (MST)

Fixed! Barneygale (talk) 08:03, 8 January 2013 (MST)

1.8 Chunk Format

The section describing how the chunk data is stored is... either completely wrong or very misleading. By reading it I got the idea that the data was stored like this:

   BVVLSbBVVLSbBVVLSb...
     (3 sections)
     where B: block and metadata array
           V: varint (1st one for # of bits, 2nd one for # of elements)
           L: light data
           S: skylight data (may or may not be there)
           b: biome data (for each section? wat?)

when in reality it's stored like this:

   BBBBBLLLLLSSSSSb
     (5 sections)
     where B: block and metadata array
           L: light data
           S: skylight data
           b: biome data (only one this time)

and there are no varints.

--Xenotoad (talk) 22:46, 30 December 2015 (UTC)

Block count field

Yesterday User:Mubelotix seems to have removed the short field for Block Count from the chunk data packet definition. What's the reason for this? Relevant edit: https://wiki.vg/index.php?title=Chunk_Format&oldid=18485

A: I did that by mistake, I removed the wrong field