This article describes the Chunk Section format used in the Chunk Data packet (Play, 0x20, clientbound).
- Chunk Section: a 16×16×16 area, sometimes also called chunk.
- Chunk Column: 16 chunks aligned vertically (totalling 16×256×16).
A Chunk Section is defined in terms of other data types. A Chunk Section consists of the following fields:
|Field Name||Field Type||Notes|
|Bits Per Block||Unsigned Byte||Determines how many bits are used to encode a block. Note that not all numbers are valid here. This also changes whether the palette is present.|
|Palette Length||VarInt||Length of the following array. May be 0, in which case the following palette is not sent.|
|Palette||Optional Array of VarInt||Mapping of block state IDs in the global palette to indices of this array|
|Data Array Length||VarInt||Number of longs in the following array|
|Data Array||Array of Long||Compacted list of 4096 indices pointing to state IDs in the Palette|
|Block Light||Byte Array||Half byte per block|
|Sky Light||Optional Byte Array||Only if in the Overworld; half byte per block|
In half-byte arrays, two values are packed into each byte. Even-indexed items are packed into the low bits, odd-indexed into the high bits.
Data Array, Block Light, and Sky Light are given for each block with increasing x coordinates, within rows of increasing z coordinates, within layers of increasing y coordinates.
The Data Array, although varying in length, will never be padded due to the number of blocks being evenly divisible by 64, which is the number of bits in a long.
There are several values that can be used for the bits per block value. In most cases, invalid values will be interpreted as a different value when parsed by the Notchian client, meaning that chunk data will be parsed incorrectly if you use an invalid bits per block. Servers must make sure that the bits per block value is correct.
- up to 4: Blocks are encoded as 4 bits. The palette is used and sent.
- 5 to 8: Blocks are encoded with the given number of bits. The palette is used and sent.
- 9 and above: The palette is not sent. Blocks are encoded by their whole ID in the global palette, with bits per block being set as the base 2 logarithm of the number of block states, rounded up. For the current vanilla release, this is 13 bits per block.
The global palette encodes a block as 13 bits. It uses the block ID for the first 9 bits, and the block damage value for the last 4 bits. For example, Diorite (block ID
minecraft:stone with damage
3) would be encoded as
000000001 0011. If a block is not found in the global palette (either due to not having a valid damage value or due to not being a valid ID), it will be treated as air.
If Minecraft Forge is installed and a sufficiently large number of blocks are added, the bits per block value for the global palette will be increased to compensate for the increased ID count. This increase can go up to 16 bits per block (for a total of 4096 block IDs; when combined with the 16 damage values, there are 65536 total states). You can get the number of blocks with the "Number of ids" field found in the RegistryData packet in the Forge Handshake.
The data array stores several entries within a single long, and sometimes overlaps one entry between multiple longs. For a bits per block value of 13, the data is stored such that bits 1 through 13 are the first entry, 14 through 26 are the second, and so on. Note that bit 1 is the least significant bit in this case, not the most significant bit. The same behavior applies when a value stretches between two longs: for instance, block 5 would be bits 53 through 64 of the first long and then bit 65 of the second long.
13 bits per block, using the global palette.
The following two longs would represent...
9 blocks, with the start of a 10th (that would be finished in the next long).
- Grass, 2:0
- Dirt, 3:0
- Dirt, 3:0
- Coarse dirt, 3:1
- Stone, 1:0
- Stone, 1:0
- Diorite, 1:3
- Gravel, 13:0
- Gravel, 13:0
- Stone, 1:0 (or potentially emerald ore, 129:0)
The following implement the previous (before 1.9) format: