Chunk Format - Revision history

imported>Codestech at 07:45, 3 August 2024

2024-08-03T07:45:09Z

← Older revision		Revision as of 07:45, 3 August 2024
Line 131:		Line 131:
	\| Data		\| Data
	\| {{Type\|Array}} of [[#Chunk Section structure\|Chunk Section]]		\| {{Type\|Array}} of [[#Chunk Section structure\|Chunk Section]]
	\| This array is NOT length-prefixed. The number of elements in the array is calculated based on the world's height. Sections are sent bottom-to-top. Starting with 1.18, the world height changes based on the dimension. The height of each dimension is assigned by the server in its corresponding [[Registry Data#Dimension Type\|registry data]] entry. For example, the vanilla overworld is 384 blocks tall, meaning 24 ~~chunks~~ will be included in this array.		\| This array is NOT length-prefixed. The number of elements in the array is calculated based on the world's height. Sections are sent bottom-to-top. Starting with 1.18, the world height changes based on the dimension. The height of each dimension is assigned by the server in its corresponding [[Registry Data#Dimension Type\|registry data]] entry. For example, the vanilla overworld is 384 blocks tall, meaning 24 chunk sections will be included in this array.
	\|}		\|}

imported>LassiPulkkinen: /* Biome registry */ Each registry now goes in a separate packet, so update wording to reflect that.

2024-06-29T22:22:30Z

Biome registry: Each registry now goes in a separate packet, so update wording to reflect that.

← Older revision		Revision as of 22:22, 29 June 2024
Line 31:		Line 31:
	==== Biome registry ====		==== Biome registry ====

	The biome registry is defined at runtime ~~as part of the~~ [[Registry Data]] packet sent by the server during the Configuration phase.		The biome registry is defined at runtime in a [[Registry Data]] packet sent by the server during the Configuration phase.

	The Notchian server pulls these biome definitions {{Minecraft Wiki\|Custom biome\|from data packs}}.		The Notchian server pulls these biome definitions {{Minecraft Wiki\|Custom biome\|from data packs}}.

imported>LassiPulkkinen: /* Palette formats */

2024-03-23T00:43:30Z

Palette formats

← Older revision		Revision as of 00:43, 23 March 2024
Line 190:		Line 190:
	The Bits Per Entry value determines what format is used for the palette.		The Bits Per Entry value determines what format is used for the palette.

	{{Warning2\|Values not listed in the following table are rounded upwards to the next one specified, or downwards if larger than the value for Direct. ~~As such,~~ such values will lead to unexpected results, and should not be used.}}		{{Warning2\|Values not listed in the following table are rounded upwards to the next one specified, or downwards if larger than the value for Direct. Therefore such values will lead to unexpected results, and should not be used.}}

	There are currently three possible palette formats:		There are currently three possible palette formats:

imported>Norbiros: removed missinformation

2024-03-10T14:30:05Z

removed missinformation

← Older revision		Revision as of 14:30, 10 March 2024
Line 209:		Line 209:
	\|-		\|-
	\| 15**		\| 15**
	\| 7*		\| 6*
	\| [[#Direct\|Direct]]		\| [[#Direct\|Direct]]
	\|}		\|}

imported>Norbiros: Default bits per entry for biomes is 7 (1.20.4)

2024-03-10T14:16:47Z

Default bits per entry for biomes is 7 (1.20.4)

← Older revision		Revision as of 14:16, 10 March 2024
Line 209:		Line 209:
	\|-		\|-
	\| 15**		\| 15**
	\| 6*		\| 7*
	\| [[#Direct\|Direct]]		\| [[#Direct\|Direct]]
	\|}		\|}

imported>LassiPulkkinen: Add Category:Protocol Details.

2024-02-26T18:50:23Z

Add Category:Protocol Details.

← Older revision		Revision as of 18:50, 26 February 2024
Line 712:		Line 712:
	* [https://github.com/barneygale/smpmap Python, 1.4]		* [https://github.com/barneygale/smpmap Python, 1.4]


			[[Category:Protocol Details]]
	[[Category:Minecraft Modern]]		[[Category:Minecraft Modern]]

imported>LassiPulkkinen: Use Template:Type for type links.

2024-02-24T22:21:52Z

Use Template:Type for type links.

← Older revision		Revision as of 22:21, 24 February 2024
Line 65:		Line 65:
	\|rowspan="6"\| Client		\|rowspan="6"\| Client
	\| Chunk X		\| Chunk X
	\| ~~[[Data types#Definitions:int~~\|Int]]		\| {{Type\|Int}}
	\| Chunk coordinate (block coordinate divided by 16, rounded down).		\| Chunk coordinate (block coordinate divided by 16, rounded down).
	\|-		\|-
	\| Chunk Z		\| Chunk Z
	\| ~~[[Data types#Definitions:int~~\|Int]]		\| {{Type\|Int}}
	\| Chunk coordinate (block coordinate divided by 16, rounded down).		\| Chunk coordinate (block coordinate divided by 16, rounded down).
	\|-		\|-
	\| Heightmaps		\| Heightmaps
	\| ~~[[Data types#Definitions:nbt~~\|NBT ~~Tag]]~~		\| {{Type\|NBT}}
	\| See [[#Heightmaps structure]] below.		\| See [[#Heightmaps structure]] below.
	\|-		\|-
	\| Size		\| Size
	\| ~~[[Data types#Definitions:varint~~\|VarInt]]		\| {{Type\|VarInt}}
	\| Size of Data in bytes; in some cases this is larger than it needs to be (e.g. [https://bugs.mojang.com/browse/MC-131684 MC-131684], [https://bugs.mojang.com/browse/MC-247438 MC-247438]) in which case extra bytes should be skipped before reading fields after Data.		\| Size of Data in bytes; in some cases this is larger than it needs to be (e.g. [https://bugs.mojang.com/browse/MC-131684 MC-131684], [https://bugs.mojang.com/browse/MC-247438 MC-247438]) in which case extra bytes should be skipped before reading fields after Data.
	\|-		\|-
	\| Data		\| Data
	\| ~~[[Data types#Definitions:byte-array~~\|Byte Array]]		\| {{Type\|Byte Array}}
	\| See [[#Data structure]] below.		\| See [[#Data structure]] below.
	\|-		\|-
Line 130:		Line 130:
	\|-		\|-
	\| Data		\| Data
	\| ~~[[Data types#Definitions:array~~\|Array]] of [[#Chunk Section structure\|Chunk Section]]		\| {{Type\|Array}} of [[#Chunk Section structure\|Chunk Section]]
	\| This array is NOT length-prefixed. The number of elements in the array is calculated based on the world's height. Sections are sent bottom-to-top. Starting with 1.18, the world height changes based on the dimension. The height of each dimension is assigned by the server in its corresponding [[Registry Data#Dimension Type\|registry data]] entry. For example, the vanilla overworld is 384 blocks tall, meaning 24 chunks will be included in this array.		\| This array is NOT length-prefixed. The number of elements in the array is calculated based on the world's height. Sections are sent bottom-to-top. Starting with 1.18, the world height changes based on the dimension. The height of each dimension is assigned by the server in its corresponding [[Registry Data#Dimension Type\|registry data]] entry. For example, the vanilla overworld is 384 blocks tall, meaning 24 chunks will be included in this array.
	\|}		\|}
Line 147:		Line 147:
	\|-		\|-
	\| Block count		\| Block count
	\| ~~[[Data types#Definitions:short~~\|Short]]		\| {{Type\|Short}}
	\| Number of non-air blocks present in the chunk section. "Non-air" is defined as any fluid and block other than air, cave air, and void air. The client will keep count of the blocks as they are broken and placed, and, if the block count reaches 0, the whole chunk section is not rendered, even if it still has blocks.		\| Number of non-air blocks present in the chunk section. "Non-air" is defined as any fluid and block other than air, cave air, and void air. The client will keep count of the blocks as they are broken and placed, and, if the block count reaches 0, the whole chunk section is not rendered, even if it still has blocks.
	\|-		\|-
Line 170:		Line 170:
	\|-		\|-
	\| Bits Per Entry		\| Bits Per Entry
	\| ~~[[Data types#Definitions:unsigned-byte~~\|Unsigned Byte]]		\| {{Type\|Unsigned Byte}}
	\| Determines how many bits are used to encode entries. Note that not all numbers are valid here.		\| Determines how many bits are used to encode entries. Note that not all numbers are valid here.
	\|-		\|-
Line 178:		Line 178:
	\|-		\|-
	\| Data Array Length		\| Data Array Length
	\| ~~[[Data types#Definitions:varint~~\|VarInt]]		\| {{Type\|VarInt}}
	\| Number of longs in the following array. This value isn't entirely respected by the Notchian client. If it is smaller than expected, it will be overridden by the correct size calculated from Bits Per Entry. If too large, the client will read the specified number of longs, but silently discard all of them afterwards, resulting in a chunk filled with palette entry 0 (which appears to have been unintentional). Present but equal to 0 when Bits Per Entry is 0.		\| Number of longs in the following array. This value isn't entirely respected by the Notchian client. If it is smaller than expected, it will be overridden by the correct size calculated from Bits Per Entry. If too large, the client will read the specified number of longs, but silently discard all of them afterwards, resulting in a chunk filled with palette entry 0 (which appears to have been unintentional). Present but equal to 0 when Bits Per Entry is 0.
	\|-		\|-
	\| Data Array		\| Data Array
	\| ~~[[Data types#Definitions:array~~\|Array]] of ~~[[Data types#Definitions:long~~\|Long]]		\| {{Type\|Array}} of {{Type\|Long}}
	\| See [[#Data Array format]] below.		\| See [[#Data Array format]] below.
	\|}		\|}
Line 229:		Line 229:
	\|-		\|-
	\| Value		\| Value
	\| ~~[[Data types#Definitions:varint~~\|VarInt]]		\| {{Type\|VarInt}}
	\| ID of the corresponding entry in its registry.		\| ID of the corresponding entry in its registry.
	\|}		\|}
Line 244:		Line 244:
	\|-		\|-
	\| Palette Length		\| Palette Length
	\| ~~[[Data types#Definitions:varint~~\|VarInt]]		\| {{Type\|VarInt}}
	\| Number of elements in the following array.		\| Number of elements in the following array.
	\|-		\|-
	\| Palette		\| Palette
	\| ~~[[Data types#Definitions:array~~\|Array]] of ~~[[Data types#Definitions:varint~~\|VarInt]]		\| {{Type\|Array}} of {{Type\|VarInt}}
	\| Mapping of IDs in the registry to indices of this array.		\| Mapping of IDs in the registry to indices of this array.
	\|}		\|}

imported>LassiPulkkinen: Add type links.

2024-02-24T04:10:29Z

Add type links.

← Older revision		Revision as of 04:10, 24 February 2024
Line 65:		Line 65:
	\|rowspan="6"\| Client		\|rowspan="6"\| Client
	\| Chunk X		\| Chunk X
	\| Int		\| [[Data types#Definitions:int\|Int]]
	\| Chunk coordinate (block coordinate divided by 16, rounded down).		\| Chunk coordinate (block coordinate divided by 16, rounded down).
	\|-		\|-
	\| Chunk Z		\| Chunk Z
	\| Int		\| [[Data types#Definitions:int\|Int]]
	\| Chunk coordinate (block coordinate divided by 16, rounded down).		\| Chunk coordinate (block coordinate divided by 16, rounded down).
	\|-		\|-
	\| Heightmaps		\| Heightmaps
	\| [[NBT]]		\| [[Data types#Definitions:nbt\|NBT Tag]]
	\| See [[#Heightmaps structure]] below.		\| See [[#Heightmaps structure]] below.
	\|-		\|-
	\| Size		\| Size
	\| VarInt		\| [[Data types#Definitions:varint\|VarInt]]
	\| Size of Data in bytes; in some cases this is larger than it needs to be (e.g. [https://bugs.mojang.com/browse/MC-131684 MC-131684], [https://bugs.mojang.com/browse/MC-247438 MC-247438]) in which case extra bytes should be skipped before reading fields after Data.		\| Size of Data in bytes; in some cases this is larger than it needs to be (e.g. [https://bugs.mojang.com/browse/MC-131684 MC-131684], [https://bugs.mojang.com/browse/MC-247438 MC-247438]) in which case extra bytes should be skipped before reading fields after Data.
	\|-		\|-
	\| Data		\| Data
	\| Byte ~~array~~		\| [[Data types#Definitions:byte-array\|Byte Array]]
	\| See [[#Data structure]] below.		\| See [[#Data structure]] below.
	\|-		\|-
Line 130:		Line 130:
	\|-		\|-
	\| Data		\| Data
	\| Array of [[#Chunk Section structure\|Chunk Section]]		\| [[Data types#Definitions:array\|Array]] of [[#Chunk Section structure\|Chunk Section]]
	\| This array is NOT length-prefixed. The number of elements in the array is calculated based on the world's height. Sections are sent bottom-to-top. Starting with 1.18, the world height changes based on the dimension. The height of each dimension is assigned by the server in its corresponding [[Registry Data#Dimension Type\|registry data]] entry. For example, the vanilla overworld is 384 blocks tall, meaning 24 chunks will be included in this array.		\| This array is NOT length-prefixed. The number of elements in the array is calculated based on the world's height. Sections are sent bottom-to-top. Starting with 1.18, the world height changes based on the dimension. The height of each dimension is assigned by the server in its corresponding [[Registry Data#Dimension Type\|registry data]] entry. For example, the vanilla overworld is 384 blocks tall, meaning 24 chunks will be included in this array.
	\|}		\|}
Line 147:		Line 147:
	\|-		\|-
	\| Block count		\| Block count
	\| Short		\| [[Data types#Definitions:short\|Short]]
	\| Number of non-air blocks present in the chunk section. "Non-air" is defined as any fluid and block other than air, cave air, and void air. The client will keep count of the blocks as they are broken and placed, and, if the block count reaches 0, the whole chunk section is not rendered, even if it still has blocks.		\| Number of non-air blocks present in the chunk section. "Non-air" is defined as any fluid and block other than air, cave air, and void air. The client will keep count of the blocks as they are broken and placed, and, if the block count reaches 0, the whole chunk section is not rendered, even if it still has blocks.
	\|-		\|-
Line 170:		Line 170:
	\|-		\|-
	\| Bits Per Entry		\| Bits Per Entry
	\| Unsigned Byte		\| [[Data types#Definitions:unsigned-byte\|Unsigned Byte]]
	\| Determines how many bits are used to encode entries. Note that not all numbers are valid here.		\| Determines how many bits are used to encode entries. Note that not all numbers are valid here.
	\|-		\|-
Line 178:		Line 178:
	\|-		\|-
	\| Data Array Length		\| Data Array Length
	\| VarInt		\| [[Data types#Definitions:varint\|VarInt]]
	\| Number of longs in the following array. This value isn't entirely respected by the Notchian client. If it is smaller than expected, it will be overridden by the correct size calculated from Bits Per Entry. If too large, the client will read the specified number of longs, but silently discard all of them afterwards, resulting in a chunk filled with palette entry 0 (which appears to have been unintentional). Present but equal to 0 when Bits Per Entry is 0.		\| Number of longs in the following array. This value isn't entirely respected by the Notchian client. If it is smaller than expected, it will be overridden by the correct size calculated from Bits Per Entry. If too large, the client will read the specified number of longs, but silently discard all of them afterwards, resulting in a chunk filled with palette entry 0 (which appears to have been unintentional). Present but equal to 0 when Bits Per Entry is 0.
	\|-		\|-
	\| Data Array		\| Data Array
	\| Array of Long		\| [[Data types#Definitions:array\|Array]] of [[Data types#Definitions:long\|Long]]
	\| See [[#Data Array format]] below.		\| See [[#Data Array format]] below.
	\|}		\|}
Line 229:		Line 229:
	\|-		\|-
	\| Value		\| Value
	\| VarInt		\| [[Data types#Definitions:varint\|VarInt]]
	\| ID of the corresponding entry in its registry.		\| ID of the corresponding entry in its registry.
	\|}		\|}
Line 244:		Line 244:
	\|-		\|-
	\| Palette Length		\| Palette Length
	\| VarInt		\| [[Data types#Definitions:varint\|VarInt]]
	\| Number of elements in the following array.		\| Number of elements in the following array.
	\|-		\|-
	\| Palette		\| Palette
	\| Array of VarInt		\| [[Data types#Definitions:array\|Array]] of [[Data types#Definitions:varint\|VarInt]]
	\| Mapping of IDs in the registry to indices of this array.		\| Mapping of IDs in the registry to indices of this array.
	\|}		\|}

imported>Oq: fix

2023-12-23T19:22:36Z

fix

← Older revision		Revision as of 19:22, 23 December 2023
Line 1:		Line 1:
	This article describes in additional detail the format of the [[Protocol#~~Chunk_Data_And_Update_Light~~\|Chunk Data]] packet.		This article describes in additional detail the format of the [[Protocol#Chunk_Data_and_Update_Light\|Chunk Data]] packet.

	== Concepts ==		== Concepts ==

imported>LassiPulkkinen: /* Heightmaps structure */ Further clarification.

2023-11-28T22:56:59Z

Heightmaps structure: Further clarification.

← Older revision		Revision as of 22:56, 28 November 2023
Line 99:		Line 99:
	The Heightmaps structure is an NBT [[NBT#Specification:compound_tag\|Compound Tag]] containing a [[NBT#Specification:long_array_tag\|Long Array Tag]] element for each heightmap. The name of each Long Array is the name of the corresponding heightmap.		The Heightmaps structure is an NBT [[NBT#Specification:compound_tag\|Compound Tag]] containing a [[NBT#Specification:long_array_tag\|Long Array Tag]] element for each heightmap. The name of each Long Array is the name of the corresponding heightmap.

	The height values of a heightmap are packed into the long array in the same manner described in [[#Data Array format]], and ordered such that the fastest-~~changing~~ coordinate is x. (However, there are only 256 entries—one for each block column.) The Bits Per Entry value used is calculated as ceil(log2(world height + 1)). This is because the number of possible height values is one more than the world height—ranging from 0 (completely blank column; not even bedrock) to world height (highest position is occupied). Note that this means, for example, that a world with height 256 will use a Bits Per Entry of 9.		The height values of a heightmap are packed into the long array in the same manner described in [[#Data Array format]], and ordered such that the fastest-increasing coordinate is x. (However, there are only 256 entries—one for each block column.) The Bits Per Entry value used is calculated as ceil(log2(world height + 1)). This is because the number of possible height values is one more than the world height—ranging from 0 (completely blank column; not even bedrock) to world height (highest position is occupied). Note that this means, for example, that a world with height 256 will use a Bits Per Entry of 9.

	The following heightmaps are currently used by the client:		The following heightmaps are currently used by the client: