Minecraft:Java Edition protocol/Registries - Revision history

SyncBot: Sync: updated from Minecraft

2026-07-11T11:08:14Z

Sync: updated from Minecraft

SyncBot: Sync: updated from Minecraft

2026-07-07T11:09:38Z

Sync: updated from Minecraft

Show changes

SyncBot: Sync: updated from Minecraft

2026-07-05T11:07:43Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:07, 5 July 2026
Line 288:		Line 288:
	The following damage types must be defined for the vanilla client to accept a [[Minecraft:Java Edition protocol/Packets#Login (play)\|Login (play)]] packet:		The following damage types must be defined for the vanilla client to accept a [[Minecraft:Java Edition protocol/Packets#Login (play)\|Login (play)]] packet:

	~~{\| class="wikitable"~~		* <code>minecraft:cactus</code>
	~~! Name~~		* <code>minecraft:campfire</code>
	\|-		* <code>minecraft:cramming</code>
	\| <code>minecraft:cactus</code>		* <code>minecraft:dragon_breath</code>
	\|-		* <code>minecraft:drown</code>
	\| <code>minecraft:campfire</code>		* <code>minecraft:dry_out</code>
	\|-		* <code>minecraft:ender_pearl</code>
	\| <code>minecraft:cramming</code>		* <code>minecraft:fall</code>
	\|-		* <code>minecraft:fly_into_wall</code>
	\| <code>minecraft:dragon_breath</code>		* <code>minecraft:freeze</code>
	\|-		* <code>minecraft:generic</code>
	\| <code>minecraft:drown</code>		* <code>minecraft:generic_kill</code>
	\|-		* <code>minecraft:hot_floor</code>
	\| <code>minecraft:dry_out</code>		* <code>minecraft:in_fire</code>
	\|-		* <code>minecraft:in_wall</code>
	\| <code>minecraft:ender_pearl</code>		* <code>minecraft:lava</code>
	\|-		* <code>minecraft:lightning_bolt</code>
	\| <code>minecraft:fall</code>		* <code>minecraft:magic</code>
	\|-		* <code>minecraft:on_fire</code>
	\| <code>minecraft:fly_into_wall</code>		* <code>minecraft:out_of_world</code>
	\|-		* <code>minecraft:outside_border</code>
	\| <code>minecraft:freeze</code>		* <code>minecraft:stalagmite</code>
	\|-		* <code>minecraft:starve</code>
	\| <code>minecraft:generic</code>		* <code>minecraft:sweet_berry_bush</code>
	\|-		* <code>minecraft:wither</code>
	\| <code>minecraft:generic_kill</code>
	\|-
	\| <code>minecraft:hot_floor</code>
	\|-
	\| <code>minecraft:in_fire</code>
	\|-
	\| <code>minecraft:in_wall</code>
	\|-
	\| <code>minecraft:lava</code>
	\|-
	\| <code>minecraft:lightning_bolt</code>
	\|-
	\| <code>minecraft:magic</code>
	\|-
	\| <code>minecraft:on_fire</code>
	\|-
	\| <code>minecraft:out_of_world</code>
	\|-
	\| <code>minecraft:outside_border</code>
	\|-
	\| <code>minecraft:stalagmite</code>
	\|-
	\| <code>minecraft:starve</code>
	\|-
	\| <code>minecraft:sweet_berry_bush</code>
	\|-
	\| <code>minecraft:wither</code>
	\|}

	==== Dimension type requirements ====		==== Dimension type requirements ====

SyncBot: Sync: new page from Minecraft

2026-06-26T11:12:20Z

Sync: new page from Minecraft

New page

{{See also|Identifier#Registries and registry objects}}

'''Registries''' are repositories of data that contain entries pertaining to certain aspects of the game, such as the world, the player, among others. Each registry enumerates entries of a certain type, such as <code>minecraft:block</code> or <code>minecraft:enchantment</code>, assigning each entry a [[Minecraft:namespaced identifier]], a numeric ID, and [[Minecraft:Tag (Java Edition)|tags]].

The contents of '''built-in registries''' are fixed for a given protocol version. These registries can only be changed through [[Minecraft:modding]]. '''Data-driven registries''' on the other hand can be modified through [[Minecraft:data packs]]. Some data-driven registries are only used by the server, while other '''synchronized registries''' are sent over the network when a player connects, and used by both the client and the server. This ability for the server to send customized registries to the client was introduced in 1.16.3, and allows for a great deal of customization over certain features of the game.

Of these, synchronized registries demand the most consideration from a protocol implementer. Supporting built-in registries properly is also important, as their contents, and consequently IDs, are liable to change between versions.

== Built-in registries ==

These registries are defined directly in Minecraft's code, and can only be changed though modding. The client and server implicitly agree on which numeric IDs correspond to which entries. Unlike [[Minecraft:Java Edition pre-flattening data values|pre-flattening block and item IDs]], these IDs can and often do change between versions.

For versions 1.14 and above the mapping from names to IDs can be obtained from the built-in [[Minecraft:Minecraft Wiki:Projects/wiki.vg merge/Data Generators#Registries report|data generators]].

=== List of built-in registries ===

This list only includes built-in registries that are used directly in the protocol, including ones that are only referenced in [[Minecraft:Java Edition protocol/Packets#Update Tags (configuration)|Update Tags]], but excluding those that are only referenced in registry data NBT.

{| class="wikitable"
! Name
! Entries
! Description
|-
| <code>minecraft:attribute</code>
| [[Minecraft:Attribute#Attributes|Entries]]
| Entity [[Minecraft:attribute]]s.
|-
| <code>minecraft:block</code>
| [[Minecraft:Java Edition data values/Blocks|Entries]]
| Types of [[Minecraft:block]]s. Note that the IDs in this registry are separate from (but related to) block state IDs.
|-
| <code>minecraft:block_entity_type</code>
| [[Minecraft:Block entity format#Types|Entries]]
| Types of [[Minecraft:block entities]].
|-
| <code>minecraft:consume_effect_type</code>
| [[Minecraft:Java Edition protocol/Slot Data#Consume Effect|Entries]]
|
|-
| <code>minecraft:custom_stat</code>
| [[Minecraft:Java Edition protocol/Packets#Award Statistics|Entries]]
| [[Minecraft:Statistics]] which do not fit into any of the other categories.
|-
| <code>minecraft:data_component_type</code>
| [[Minecraft:Java Edition protocol/Slot Data#Structured components|Entries]]
| [[Minecraft:Data component]]s.
|-
| <code>minecraft:entity_type</code>
| [[Minecraft:Java Edition protocol/Entity metadata#Entities|Entries]]
| Types of [[Minecraft:entities]].
|-
| <code>minecraft:fluid</code>
| [[Minecraft:Java Edition data values#Fluids|Entries]]
| Types of [[Minecraft:fluid]]s. Currently only used in the protocol in tag definitions.
|-
| <code>minecraft:game_event</code>
| [[Minecraft:Skulk Sensor#Vibration frequencies|Entries]]
| Sources of [[Minecraft:vibrations]] detected by [[Minecraft:sculk]] components and [[Minecraft:warden]]s.
|-
| <code>minecraft:item</code>
| [[Minecraft:Java Edition data values/Items|Entries]]
| Types of [[Minecraft:item]]s.
|-
| <code>minecraft:menu</code>
| [[Minecraft:Java Edition protocol/Inventory#Types|Entries]]
| Types of [[Minecraft:container]] windows.
|-
| <code>minecraft:mob_effect</code>
| [[Minecraft:Effect#Descriptions|Entries]]
| Types of [[Minecraft:status effects]].
|-
| <code>minecraft:particle_type</code>
| [[Minecraft:Java Edition protocol/Particles|Entries]]
| Types of [[Minecraft:Particles (Java Edition)|particle]] effects.
|-
| <code>minecraft:potion</code>
| [[Minecraft:Potion#Item data|Entries]]
| Built-in [[Minecraft:potion]] types. Note that these have "long" and "strong" variants, as would be seen on brewing.
|-
| <code>minecraft:recipe_book_category</code>
|
| [[Minecraft:Recipe book]] tabs.
|-
| <code>minecraft:recipe_display</code>
| [[Minecraft:Java Edition protocol/Recipes#Recipe Display types|Entries]]
|
|-
| <code>minecraft:slot_display</code>
| [[Minecraft:Java Edition protocol/Recipes#Slot Display types|Entries]]
|
|-
| <code>minecraft:sound_event</code>
| [[Minecraft:Sounds.json#Sound events|Entries]]
| Built-in [[Minecraft:sound event]]s.
|-
| <code>minecraft:stat_type</code>
| [[Minecraft:Java Edition protocol/Packets#Award Statistics|Entries]]
| [[Minecraft:Statistic]] categories.
|-
| <code>minecraft:villager_type</code>
| [[Minecraft:Villager#Type data values|Entries]]
| [[Minecraft:Villager]] biome types.
|}

== Synchronized registries ==

The server sends these registries to the client via [[Minecraft:Java Edition protocol/Packets#Registry_Data|Registry Data]] packets during the configuration phase, one packet for each registry.

{| class="wikitable"
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="3"| [[Minecraft:Minecraft Wiki:Projects/wiki.vg merge/Protocol#Registry_Data_2|Varies]]
| rowspan="3"| Configuration
| rowspan="3"| Client
| colspan="2"| Registry ID
| colspan="2"| {{Type|Identifier}}
| Name of the registry, such as <code>minecraft:dimension_type</code>.
|-
| rowspan="2"| Entries
| Entry ID
| rowspan="2"| {{Type|Prefixed Array}}
| {{Type|Identifier}}
| Name of the entry, such as <code>minecraft:overworld</code>.
|-
| Data
| {{Type|Prefixed Optional}} {{Type|NBT}}
| Entry data. If omitted, sourced from the selected [[#Known packs negotiation|known packs]].
|}

The ordering of the entries in the Entries array defines the numeric IDs that they will be assigned to, starting from 0 and counting upwards. It is essential to maintain consistency between server and client, since many parts of the protocol reference these entries by their ID. The client will disconnect upon receiving a reference to a non-existing entry.

The NBT data of registry entries has the same structure as their definitions in [[Minecraft:data packs]], but [[Minecraft:NBT_format#Conversion_from_JSON|represented in NBT instead of JSON]]. The format for each registry is defined in the [[#List of synchronized registries|list of registries below]].

=== Obtaining vanilla registry data ===

The default contents of data-driven registries are defined as JSON in the default [[Minecraft:data pack]], which is located inside both [[Minecraft:client.jar]] and [[Minecraft:server.jar]] under data/. These files can be extracted using any ZIP extraction utility. Note however that since 1.18 the server.jar (but not client.jar) distributed by Mojang is wrapped inside a [[Minecraft:Server.jar#Bundler options|bundler]], and extracting the data pack requires first extracting the inner server.jar located at META-INF/versions/*/server-*.jar from the outer server.jar.

Alternatively, the data is available as a single JSON file for the following versions:
* [https://gist.github.com/Mansitoh/e6c5cf8bbf17e9faf4e4e75bb3f4789d 1.21]
* [https://gist.github.com/WinX64/ab8c7a8df797c273b32d3a3b66522906 1.20.6]
* [https://gist.github.com/WinX64/3675ffee90360e9fc1e45074e49f6ede 1.20.2]
* [https://gist.github.com/WinX64/2d257d3df3c7ab9c4b02dc90be881ab2 1.20.1]
* [https://gist.github.com/nikes/aff59b758a807858da131a1881525b14 1.19.2]
* [https://gist.github.com/rj00a/f2970a8ce4d09477ec8f16003b9dce86 1.19]

=== Known packs negotiation ===

In order to save bandwidth, the client and server can negotiate which data packs are known by both peers, and avoid sending NBT sourced from those packs over the network. In practice the vanilla client and server as of 1.21.8 only recognize one data pack, <code>minecraft:core</code>, which contains the default definitions. Data from custom data packs is always sent over the network.

# '''S'''→'''C''': [[Minecraft:Java Edition protocol/Packets#Clientbound Known Packs|Clientbound Known Packs]] (with all data packs known by the server)
# '''C'''→'''S''': [[Minecraft:Java Edition protocol/Packets#Serverbound Known Packs|Serverbound Known Packs]] (with the subset of data packs also known by the client)
# ''Server computes the mutually supported data packs''
# '''S'''→'''C''': Multiple [[Minecraft:Java Edition protocol/Packets#Registry Data|Registry Data]] (for each registry, containing all entries, but excluding mutually known NBT)
# '''S'''→'''C''': [[Minecraft:Java Edition protocol/Packets#Update Tags (configuration)|Update Tags]]
# ''Client accumulates registry and tag data for later resolution''
# '''S'''→'''C''': [[Minecraft:Java Edition protocol/Packets#Finish Configuration|Finish Configuration]]
# ''Client resolves registry and tag data, loading data from packs when requested, and detecting unbound references to entries and tags''

When resolving an entry from a Registry Data packet, the client will always use the NBT data specified in the packet if it is present. Otherwise it will look for the data in the selected known packs. Tag data is never sourced from known packs, and must always be sent by the server in full.

'''If an entry is not mentioned in a Registry Data packet, it will not exist in the game session, even if it exists in one of the known packs. All entries that will be used in the session must be listed in Registry Data packets; only the NBT part can be omitted.'''

When multiple known packs are selected, the client will combine them the same way resource and data packs are normally combined. The packs are listed in Clientbound Known Packs from the bottom of the stack to the top, so earlier packs are overridden by later ones.

A custom server implementation may choose to skip sending Clientbound Known Packs, in which case all NBT data must be present in the Registry Data packets, or to require that the client knows about <code>minecraft:core</code>, in which case no NBT needs to be sent. Similarly a custom client may respond with an empty Serverbound Known Packs packet, and require the server to send all registry NBT. All of these incomplete implementations are compatible with the vanilla implementation, but interoperability between them will be limited.

=== List of synchronized registries ===

{| class="wikitable"
! Name
! NBT format
! Requirements
! Description
|-
| <code>minecraft:banner_pattern</code>
| [[Minecraft:Banner pattern definition#JSON Format|NBT format]]
| Optional
| Types of [[Minecraft:Banner#Patterns|banner patterns]], specifying their textures.
|-
| <code>minecraft:chat_type</code>
| [[Minecraft:Chat type#JSON format|NBT format]]
| Optional
| [[Minecraft:Chat type]]s, specifying how [[Minecraft:chat]] messages are formatted. Referenced in the [[Minecraft:Java Edition protocol/Packets#Disguised Chat Message|Disguised Chat Message]] and [[Minecraft:Java Edition protocol/Packets#Player Chat Message|Player Chat Message]] packets.
|-
| <code>minecraft:damage_type</code>
| [[Minecraft:Damage type#JSON format|NBT format]]
| [[#Damage type requirements|See below]]
| [[Minecraft:Damage type]]s, specifying audiovisual effects generated by damage events. Referenced in the [[Minecraft:Java Edition protocol/Packets#Damage Event|Damage Event]] packet.
|-
| <code>minecraft:dialog</code>
| [[Minecraft:Dialog#Dialog format|NBT format]]
| Optional
| Types of [[Minecraft:dialog]]s.
|-
| <code>minecraft:dimension_type</code>
| [[Minecraft:Dimension type#JSON format|NBT format]]
| [[#Dimension type requirements|See below]]
| Types of [[Minecraft:dimension]]s, specifying characteristics such as the [[Minecraft:build height limit]]. Referenced in the [[Minecraft:Java Edition protocol/Packets#Login (play)|Login (play)]] and [[Minecraft:Java Edition protocol/Packets#Respawn|Respawn]] packets.
|-
| <code>minecraft:enchantment</code>
| [[Minecraft:Enchantment definition#JSON format|NBT format]]
| Optional
| Types of [[Minecraft:enchantment]]s.
|-
| <code>minecraft:instrument</code>
| [[Minecraft:Instrument definition#JSON Format|NBT format]]
| Optional
| [[Minecraft:Goat horn]] instruments, specifying their tooltip description and the sound event used when the local player uses a goat horn.
|-
| <code>minecraft:jukebox_song</code>
| [[Minecraft:Jukebox song definition#JSON format|NBT format]]
| Optional
| Types of [[Minecraft:music disc]]s.
|-
| <code>minecraft:painting_variant</code>
| [[Minecraft:Painting variant definition#JSON Format|NBT format]]
| Non-empty
| [[Minecraft:Painting variant]]s.
|-
| <code>minecraft:test_environment</code>
| [[Minecraft:Test environment definition#JSON Format|NBT format]]
| Optional
| [[Minecraft:GameTest]] environments.
|-
| <code>minecraft:test_instance</code>
| [[Minecraft:Test instance definition#JSON Format|NBT format]]
| Optional
| [[Minecraft:GameTest]] instances.
|-
| <code>minecraft:trim_material</code>
| [[Minecraft:Armor trim definition#Trim material|NBT format]]
| Optional
| [[Minecraft:Smithing#Trimming|Armor trim]] materials.
|-
| <code>minecraft:trim_pattern</code>
| [[Minecraft:Armor trim definition#Trim pattern|NBT format]]
| Optional
| [[Minecraft:Smithing#Trimming|Armor trim]] patterns.
|-
| <code>minecraft:worldgen/biome</code>
| [[Minecraft:Biome definition#JSON format|NBT format]]
| [[#Biome requirements|See below]]
| [[Minecraft:Biome]]s. The name is an artifact of the directory structure used in data packs; the uses of biome information on the client are unrelated to world generation. Referenced in the [[Minecraft:Java Edition protocol/Packets#Chunk Biomes|Chunk Biomes]] and [[Minecraft:Java Edition protocol/Packets#Chunk Data and Update Light|Chunk Data and Update Light]] packets.
|-
| <code>minecraft:cat_variant</code>
| [[Minecraft:Mob variant definitions#Cat|NBT format]]
| Non-empty
| [[Minecraft:Cat variant]]s.
|-
| <code>minecraft:chicken_variant</code>
| [[Minecraft:Mob variant definitions#Chicken|NBT format]]
| Non-empty
| [[Minecraft:Chicken variant]]s.
|-
| <code>minecraft:cow_variant</code>
| [[Minecraft:Mob variant definitions#Cow|NBT format]]
| Non-empty
| [[Minecraft:Cow variant]]s.
|-
| <code>minecraft:frog_variant</code>
| [[Minecraft:Mob variant definitions#Frog|NBT format]]
| Non-empty
| [[Minecraft:Frog variant]]s.
|-
| <code>minecraft:pig_variant</code>
| [[Minecraft:Mob variant definitions#Pig|NBT format]]
| Non-empty
| [[Minecraft:Pig variant]]s.
|-
| <code>minecraft:wolf_variant</code>
| [[Minecraft:Mob variant definitions#Wolf|NBT format]]
| Non-empty
| [[Minecraft:Wolf variant]]s.
|-
| <code>minecraft:wolf_sound_variant</code>
| [[Minecraft:Mob variant definitions#Wolf sounds|NBT format]]
| Non-empty
| [[Minecraft:Wolf sound variant]]s.
|}

==== Damage type requirements ====

The following damage types must be defined for the vanilla client to accept a [[Minecraft:Java Edition protocol/Packets#Login (play)|Login (play)]] packet:

{| class="wikitable"
! Name
|-
| <code>minecraft:cactus</code>
|-
| <code>minecraft:campfire</code>
|-
| <code>minecraft:cramming</code>
|-
| <code>minecraft:dragon_breath</code>
|-
| <code>minecraft:drown</code>
|-
| <code>minecraft:dry_out</code>
|-
| <code>minecraft:ender_pearl</code>
|-
| <code>minecraft:fall</code>
|-
| <code>minecraft:fly_into_wall</code>
|-
| <code>minecraft:freeze</code>
|-
| <code>minecraft:generic</code>
|-
| <code>minecraft:generic_kill</code>
|-
| <code>minecraft:hot_floor</code>
|-
| <code>minecraft:in_fire</code>
|-
| <code>minecraft:in_wall</code>
|-
| <code>minecraft:lava</code>
|-
| <code>minecraft:lightning_bolt</code>
|-
| <code>minecraft:magic</code>
|-
| <code>minecraft:on_fire</code>
|-
| <code>minecraft:out_of_world</code>
|-
| <code>minecraft:outside_border</code>
|-
| <code>minecraft:stalagmite</code>
|-
| <code>minecraft:starve</code>
|-
| <code>minecraft:sweet_berry_bush</code>
|-
| <code>minecraft:wither</code>
|}

==== Dimension type requirements ====

The <code>minecraft:dimension_type</code> registry is technically optional, but due to the required Dimension Type field, it is impossible to send a valid [[Minecraft:Java Edition protocol/Packets#Login (play)|Login (play)]] packet unless the registry has at least one entry.

==== Biome requirements ====

A biome named <code>minecraft:plains</code> must be defined for the vanilla client to accept a [[Minecraft:Java Edition protocol/Packets#Login (play)|Login (play)]] packet. It is used as the default for unloaded chunks.

[[Category:Protocol Details]]
[[Category:Java Edition protocol]]

{{license wiki.vg}}

← Older revision		Revision as of 11:08, 11 July 2026
Line 15:		Line 15:
	=== List of built-in registries ===		=== List of built-in registries ===

	This list only includes built-in registries that are used directly in the protocol, including ones that are only referenced in ~~[[Minecraft:Java Edition protocol/Packets#Update Tags (configuration)~~\|Update Tags~~]],~~ but excluding those that are only referenced in registry data NBT.		This list only includes built-in registries that are used directly in the protocol, including ones that are only referenced in {{packet\|Update Tags}} but excluding those that are only referenced in registry data NBT.

	{\| class="wikitable"		{\| class="wikitable"
Line 105:		Line 105:
	== Synchronized registries ==		== Synchronized registries ==

	The server sends these registries to the client via ~~[[Minecraft:Java Edition protocol/Packets#Registry_Data~~\|Registry Data]] packets during the configuration phase, one packet for each registry.		The server sends these registries to the client via {{packet\|Registry Data}} packets during the configuration phase, one packet for each registry.

	{\| class="wikitable"		{\| class="wikitable"
Line 115:		Line 115:
	! Notes		! Notes
	\|-		\|-
	\| rowspan="3"\| [[Minecraft:Minecraft Wiki:Projects/wiki.vg merge/Protocol#~~Registry_Data_2~~\|Varies]]		\| rowspan="3"\| [[Minecraft:Minecraft Wiki:Projects/wiki.vg merge/Protocol#Registry Data\|Varies]]
	\| rowspan="3"\| Configuration		\| rowspan="3"\| Configuration
	\| rowspan="3"\| Client		\| rowspan="3"\| Client
Line 153:		Line 153:
	In order to save bandwidth, the client and server can negotiate which data packs are known by both peers, and avoid sending NBT sourced from those packs over the network. In practice the vanilla client and server as of 1.21.8 only recognize one data pack, <code>minecraft:core</code>, which contains the default definitions. Data from custom data packs is always sent over the network.		In order to save bandwidth, the client and server can negotiate which data packs are known by both peers, and avoid sending NBT sourced from those packs over the network. In practice the vanilla client and server as of 1.21.8 only recognize one data pack, <code>minecraft:core</code>, which contains the default definitions. Data from custom data packs is always sent over the network.

	# '''S'''→'''C''': ~~[[Minecraft:Java Edition protocol/Packets#Clientbound Known Packs~~\|~~Clientbound~~ Known Packs]] (with all data packs known by the server)		# '''S'''→'''C''': {{packet\|Known Packs (clientbound)}} (with all data packs known by the server)
	# '''C'''→'''S''': ~~[[Minecraft:Java Edition protocol/Packets#Serverbound Known Packs~~\|~~Serverbound~~ Known Packs]] (with the subset of data packs also known by the client)		# '''C'''→'''S''': {{packet\|Known Packs (serverbound)}} (with the subset of data packs also known by the client)
	# ''Server computes the mutually supported data packs''		# ''Server computes the mutually supported data packs''
	# '''S'''→'''C''': Multiple ~~[[Minecraft:Java Edition protocol/Packets#Registry Data~~\|Registry Data]] (for each registry, containing all entries, but excluding mutually known NBT)		# '''S'''→'''C''': Multiple {{packet\|Registry Data}} (for each registry, containing all entries, but excluding mutually known NBT)
	# '''S'''→'''C''': ~~[[Minecraft:Java Edition protocol/Packets#Update Tags (configuration)~~\|Update Tags]]		# '''S'''→'''C''': {{packet\|Update Tags}}
	# ''Client accumulates registry and tag data for later resolution''		# ''Client accumulates registry and tag data for later resolution''
	# '''S'''→'''C''': ~~[[Minecraft:Java Edition protocol/Packets#Finish Configuration~~\|Finish Configuration]]		# '''S'''→'''C''': {{packet\|Finish Configuration}}
	# ''Client resolves registry and tag data, loading data from packs when requested, and detecting unbound references to entries and tags''		# ''Client resolves registry and tag data, loading data from packs when requested, and detecting unbound references to entries and tags''

Line 186:		Line 186:
	\| [[Minecraft:Chat type#JSON format\|NBT format]]		\| [[Minecraft:Chat type#JSON format\|NBT format]]
	\| Optional		\| Optional
	\| [[Minecraft:Chat type]]s, specifying how [[Minecraft:chat]] messages are formatted. Referenced in the ~~[[Minecraft:Java Edition protocol/Packets#Disguised Chat Message~~\|Disguised Chat Message]] and ~~[[Minecraft:Java Edition protocol/Packets#Player Chat Message~~\|Player Chat Message]] packets.		\| [[Minecraft:Chat type]]s, specifying how [[Minecraft:chat]] messages are formatted. Referenced in the {{packet\|Disguised Chat Message}} and {{packet\|Player Chat Message}} packets.
	\|-		\|-
	\| <code>minecraft:damage_type</code>		\| <code>minecraft:damage_type</code>
	\| [[Minecraft:Damage type#JSON format\|NBT format]]		\| [[Minecraft:Damage type#JSON format\|NBT format]]
	\| [[#Damage type requirements\|See below]]		\| [[#Damage type requirements\|See below]]
	\| [[Minecraft:Damage type]]s, specifying audiovisual effects generated by damage events. Referenced in the ~~[[Minecraft:Java Edition protocol/Packets#Damage Event~~\|Damage Event]] packet.		\| [[Minecraft:Damage type]]s, specifying audiovisual effects generated by damage events. Referenced in the {{packet\|Damage Event}} packet.
	\|-		\|-
	\| <code>minecraft:dialog</code>		\| <code>minecraft:dialog</code>
Line 201:		Line 201:
	\| [[Minecraft:Dimension type#JSON format\|NBT format]]		\| [[Minecraft:Dimension type#JSON format\|NBT format]]
	\| [[#Dimension type requirements\|See below]]		\| [[#Dimension type requirements\|See below]]
	\| Types of [[Minecraft:dimension]]s, specifying characteristics such as the [[Minecraft:build height limit]]. Referenced in the ~~[[Minecraft:Java Edition protocol/Packets#Login (play)~~\|Login (play)]] and ~~[[Minecraft:Java Edition protocol/Packets#Respawn~~\|Respawn]] packets.		\| Types of [[Minecraft:dimension]]s, specifying characteristics such as the [[Minecraft:build height limit]]. Referenced in the {{packet\|Login (play)}} and {{packet\|Respawn}} packets.
	\|-		\|-
	\| <code>minecraft:enchantment</code>		\| <code>minecraft:enchantment</code>
Line 261:		Line 261:
	\| [[Minecraft:Biome definition#JSON format\|NBT format]]		\| [[Minecraft:Biome definition#JSON format\|NBT format]]
	\| [[#Biome requirements\|See below]]		\| [[#Biome requirements\|See below]]
	\| [[Minecraft:Biome]]s. The name is an artifact of the directory structure used in data packs; the uses of biome information on the client are unrelated to world generation. Referenced in the ~~[[Minecraft:Java Edition protocol/Packets#Chunk Biomes~~\|Chunk Biomes]] and ~~[[Minecraft:Java Edition protocol/Packets#Chunk Data and Update Light~~\|Chunk Data and Update Light]] packets.		\| [[Minecraft:Biome]]s. The name is an artifact of the directory structure used in data packs; the uses of biome information on the client are unrelated to world generation. Referenced in the {{packet\|Chunk Biomes}} and {{packet\|Chunk Data and Update Light}} packets.
	\|-		\|-
	\| <code>minecraft:cat_variant</code>		\| <code>minecraft:cat_variant</code>
Line 324:		Line 324:
	\|}		\|}

	=== Banner pattern requirements ===		==== Banner pattern requirements ====

	Due to their use in the default values of [[Minecraft:item component]]s, the following banner pattern tags must be defined (in {{packet\|Update Tags}}) for the vanilla client to accept a {{packet\|Finish Configuration}} packet:		Due to their use in the default values of [[Minecraft:item component]]s, the following banner pattern tags must be defined (in {{packet\|Update Tags}}) for the vanilla client to accept a {{packet\|Finish Configuration}} packet:
Line 341:		Line 341:
	==== Damage type requirements ====		==== Damage type requirements ====

	The following damage types must be defined for the vanilla client to accept a ~~[[Minecraft:Java Edition protocol/Packets#Login (play)~~\|Login (play)]] packet:		The following damage types must be defined for the vanilla client to accept a {{packet\|Login (play)}} packet:

	* <code>minecraft:cactus</code>		* <code>minecraft:cactus</code>
Line 375:		Line 375:
	* <code>minecraft:is_fire</code>		* <code>minecraft:is_fire</code>

	=== Instrument requirements ===		==== Instrument requirements ====

	Due to its use as the default value of the <code>minecraft:instrument</code> data component for goat horns, an instrument named <code>minecraft:ponder_goat_horn</code> must be defined for the vanilla client to accept a {{packet\|Finish Configuration}} packet.		Due to its use as the default value of the <code>minecraft:instrument</code> data component for goat horns, an instrument named <code>minecraft:ponder_goat_horn</code> must be defined for the vanilla client to accept a {{packet\|Finish Configuration}} packet.

	=== Jukebox song requirements ===		==== Jukebox song requirements ====

	Due to their use in the default values of [[Minecraft:item component]]s, the following jukebox songs must be defined for the vanilla client to accept a {{packet\|Finish Configuration}} packet:		Due to their use in the default values of [[Minecraft:item component]]s, the following jukebox songs must be defined for the vanilla client to accept a {{packet\|Finish Configuration}} packet:
Line 406:		Line 406:
	* <code>minecraft:ward</code>		* <code>minecraft:ward</code>

	=== Trim material requirements ===		==== Trim material requirements ====

	Due to their use in the default values of [[Minecraft:item component]]s, the following trim materials must be defined for the vanilla client to accept a {{packet\|Finish Configuration}} packet:		Due to their use in the default values of [[Minecraft:item component]]s, the following trim materials must be defined for the vanilla client to accept a {{packet\|Finish Configuration}} packet:
Line 424:		Line 424:
	==== Dimension type requirements ====		==== Dimension type requirements ====

	The <code>minecraft:dimension_type</code> registry is technically optional, but due to the required Dimension Type field, it is impossible to send a valid ~~[[Minecraft:Java Edition protocol/Packets#Login (play)~~\|Login (play)]] packet unless the registry has at least one entry.		The <code>minecraft:dimension_type</code> registry is technically optional, but due to the required Dimension Type field, it is impossible to send a valid {{packet\|Login (play)}} packet unless the registry has at least one entry.

	==== Biome requirements ====		==== Biome requirements ====

	A biome named <code>minecraft:plains</code> must be defined for the vanilla client to accept a ~~[[Minecraft:Java Edition protocol/Packets#Login (play)~~\|Login (play)]] packet. It is used as the default for unloaded chunks.		A biome named <code>minecraft:plains</code> must be defined for the vanilla client to accept a {{packet\|Login (play)}} packet. It is used as the default for unloaded chunks.

	=== Chicken variant requirements ===		==== Chicken variant requirements ====

	Due to their use in the default values of [[Minecraft:item component]]s, the following chicken variants must be defined for the vanilla client to accept a {{packet\|Finish Configuration}} packet:		Due to their use in the default values of [[Minecraft:item component]]s, the following chicken variants must be defined for the vanilla client to accept a {{packet\|Finish Configuration}} packet: