Minecraft:Data component format - Revision history

SyncBot: Sync: updated from Minecraft

2026-06-03T11:05:00Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:05, 3 June 2026
Line 1:		Line 1:
	{{About\|the format in {{JE}}\|the legacy format\|Item format/Before 1.20.5\|the format in {{BE}}\|Item components}}		{{About\|the format in {{JE}}\|the legacy format\|Item format/Before 1.20.5\|the format in {{BE}}\|Item components}}
	{{~~redirect~~\|Component~~\|the text format\|Text component format~~}}{{exclusive\|java}}		{{for\|other uses\|Component}}{{exclusive\|java}}

	'''Data components''', or simply '''components''', are structured data used to store information and define behavior. Their IDs are [[Minecraft:namespaced identifier]]s, and their values can be any data type – see {{slink\|\|List of components}}.		'''Data components''', or simply '''components''', are structured data used to store information and define behavior. Their IDs are [[Minecraft:namespaced identifier]]s, and their values can be any data type – see {{slink\|\|List of components}}.

SyncBot: Sync: updated from Minecraft

2026-05-28T11:03:49Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:03, 28 May 2026
Line 518:		Line 518:
	* {{nbt\|compound\|components}}: Parent tag.		* {{nbt\|compound\|components}}: Parent tag.
	{{/item name}}		{{/item name}}
	''Example:'' {{command\|1=give @s diamond[minecraft:item_name="~~dirt~~"]}}		''Example:'' {{command\|1=give @s diamond[minecraft:item_name="Dirt"]}}
	* Gives a diamond that is named ~~dirt~~.</div>		* Gives a diamond that is named "Dirt".</div>

	=== jukebox_playable ===		=== jukebox_playable ===

SyncBot: Sync: updated from Minecraft

2026-05-26T11:06:08Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:06, 26 May 2026
Line 518:		Line 518:
	* {{nbt\|compound\|components}}: Parent tag.		* {{nbt\|compound\|components}}: Parent tag.
	{{/item name}}		{{/item name}}
	</div>		''Example:'' {{command\|1=give @s diamond[minecraft:item_name="dirt"]}}
			* Gives a diamond that is named dirt.</div>

	=== jukebox_playable ===		=== jukebox_playable ===

SyncBot: Sync: updated from Minecraft

2026-05-24T11:07:08Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:07, 24 May 2026
Line 4:		Line 4:
	'''Data components''', or simply '''components''', are structured data used to store information and define behavior. Their IDs are [[Minecraft:namespaced identifier]]s, and their values can be any data type – see {{slink\|\|List of components}}.		'''Data components''', or simply '''components''', are structured data used to store information and define behavior. Their IDs are [[Minecraft:namespaced identifier]]s, and their values can be any data type – see {{slink\|\|List of components}}.

	When used by [[Minecraft:item]]s, they are referred as '''item components''' or '''item stack components'''. They can exist anywhere that an item is stored, such as the [[Minecraft:Player.dat format\|player's inventory]], container [[Minecraft:Block entity format\|block entities]], and [[Minecraft:structure file]]s. ~~Not~~ all characteristics of items are covered by data components. For properties of items ~~that are defined by code and cannot be modified through components~~, see [[Minecraft:Java Edition hardcoded item properties]].		When used by [[Minecraft:item]]s, they are referred as '''item components''' or '''item stack components'''. They can exist anywhere that an item is stored, such as the [[Minecraft:Player.dat format\|player's inventory]], container [[Minecraft:Block entity format\|block entities]], and [[Minecraft:structure file]]s. Importantly, not all characteristics of items are covered by data components, and remain as fixed properties associated with the item ID; the behaviour cannot be removed from the item, nor applied to a different item that does not have that behaviour by default. For a reasonably comprehensive list of such properties associated with items in the latest version, see [[Minecraft:Java Edition hardcoded item properties]].

	Data components are only partly implemented for [[Minecraft:block entities]]. They partially replace the [[Minecraft:NBT format]] and allow some block data to be read or copied through predicates and loot functions.		Data components are only partly implemented for [[Minecraft:block entities]]. They partially replace the [[Minecraft:NBT format]] and allow some block data to be read or copied through predicates and loot functions.

SyncBot: Sync: updated from Minecraft

2026-05-13T11:05:38Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:05, 13 May 2026
Line 24:		Line 24:
	{{for\|the legacy format before 1.20.5\|Item format/Before 1.20.5}}		{{for\|the legacy format before 1.20.5\|Item format/Before 1.20.5}}

	Every item type (item ID) has a set of ''default'' data components. Item stacks must specify an item ID, which ~~implicity~~ sets these default components, but they may be ~~overriden~~ by that individual item stack. Default components are not saved on individual item stacks.		Every item type (item ID) has a set of ''default'' data components. Item stacks must specify an item ID, which implicitly sets these default components, but they may be overridden by that individual item stack. Default components are not saved on individual item stacks.

	When saved in the [[Minecraft:NBT format]], items are written as a compound with the following tags:		When saved in the [[Minecraft:NBT format]], items are written as a compound with the following tags:
Line 40:		Line 40:
	Block entities are stored in the [[Minecraft:NBT format]]. While they still use NBT tags for their individual properties, any non-default data components that exist on the item used to place the block will be saved.		Block entities are stored in the [[Minecraft:NBT format]]. While they still use NBT tags for their individual properties, any non-default data components that exist on the item used to place the block will be saved.

	Some NBT data on block entities are treated as data components when ~~transfering~~ data between items and blocks. For example, the <code>Items</code> field in a chest is interpreted as the <code>minecraft:container</code> component, despite being labeled and structured differently.		Some NBT data on block entities are treated as data components when transferring data between items and blocks. For example, the <code>Items</code> field in a chest is interpreted as the <code>minecraft:container</code> component, despite being labeled and structured differently.

	<div class="treeview">		<div class="treeview">

SyncBot: Sync: updated from Minecraft

2026-04-26T11:05:45Z

Sync: updated from Minecraft

@@ Line 1,323: / Line 1,323: @@
 **** {{nbt|string}}: A world modifier.
 *** {{nbt|boolean|include_description}}: Whether to show the mine ingredients in the tooltip of this mine item.
 </div>
 {{Collapse|tail=1}}

SyncBot: Sync: updated from Minecraft

2026-04-21T11:05:07Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:05, 21 April 2026
Line 343:		Line 343:
	{{/damage_resistant}}		{{/damage_resistant}}
	</div>		</div>
			''Example:'' {{command\|give @s cake[damage_resistant{{=}}{types:"#minecraft:is_fire"}]}}
			* Gives a cake that is immune to all types of fire damage.

	=== damage_type ===		=== damage_type ===
Line 1,084:		Line 1,086:
	== Non-encoded components ==		== Non-encoded components ==
	These data components exist and are used by the game internally, but are not encoded on items. Therefore, they cannot be used in commands, nor seen with {{command\|data}}.		These data components exist and are used by the game internally, but are not encoded on items. Therefore, they cannot be used in commands, nor seen with {{command\|data}}.

			=== additional_trade_cost ===

			<div class="treeview">
			* {{nbt\|compound\|components}}: Parent tag.
			** {{nbt\|int\|minecraft:additional_trade_cost}}: Used on the {{cd\|gives}} item of a [[Minecraft:villager trade definition\|villager trade]] to add to the {{cd\|count}} of the {{cd\|wants}} item.
			</div>

	=== creative_slot_lock ===		=== creative_slot_lock ===
Line 1,097:		Line 1,106:
	* {{nbt\|compound\|components}}: Parent tag.		* {{nbt\|compound\|components}}: Parent tag.
	** {{nbt\|int\|minecraft:map_post_processing}}: Only used internally when this [[Minecraft:filled map]] has been duplicated or locked in a [[Minecraft:crafting table]] or a [[Minecraft:cartography table]]. Can be 0 (lock) or 1 (scale), adding the "Locked" line or "Scale" line in this item's tooltip, respectively.		** {{nbt\|int\|minecraft:map_post_processing}}: Only used internally when this [[Minecraft:filled map]] has been duplicated or locked in a [[Minecraft:crafting table]] or a [[Minecraft:cartography table]]. Can be 0 (lock) or 1 (scale), adding the "Locked" line or "Scale" line in this item's tooltip, respectively.
	~~</div>~~

	~~=== additional_trade_cost ===~~
	~~{{in development\|java\|\|26.1\|section=1}}~~
	~~<div class="treeview">~~
	* {{nbt\|compound\|components}}: Parent tag.
	** {{nbt\|int\|minecraft:additional_trade_cost}}: Used on the {{cd\|gives}} item of a [[Minecraft:villager trade definition\|villager trade]] to add to the {{cd\|count}} of the {{cd\|wants}} item.
	</div>		</div>

SyncBot: Sync: updated from Minecraft

2026-04-18T11:07:10Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:07, 18 April 2026
Line 359:		Line 359:
	{{/death_protection}}</div>		{{/death_protection}}</div>
	''Example:'' {{command\|/give @s nether_star[death_protection{{=}}{death_effects:[{type:'minecraft:clear_all_effects'}]}]}}		''Example:'' {{command\|/give @s nether_star[death_protection{{=}}{death_effects:[{type:'minecraft:clear_all_effects'}]}]}}
	* Gives a nether star that protects the holder from death and ~~when did so,~~ removes all status effects from the holder.		* Gives a nether star that protects the holder from death and removes all status effects from the holder.

	=== debug_stick_state ===		=== debug_stick_state ===
Line 479:		Line 479:
	</div>		</div>
	''Example:'' {{command\|/give @s nether_star[equippable{{=}}{slot:"head"},glider{{=}}{}]}}		''Example:'' {{command\|/give @s nether_star[equippable{{=}}{slot:"head"},glider{{=}}{}]}}
	* Gives a nether star that can be equipped in the head slot and if on the head, allows the player to glide.		* Gives a nether star that can be equipped in the head slot, and if is placed on the head, it allows the player to glide.

	=== instrument ===		=== instrument ===

SyncBot: Sync: new page from Minecraft

2026-04-12T11:09:40Z

Sync: new page from Minecraft

Show changes

← Older revision		Revision as of 11:05, 3 June 2026
Line 1:		Line 1:
	{{About\|the format in {{JE}}\|the legacy format\|Item format/Before 1.20.5\|the format in {{BE}}\|Item components}}		{{About\|the format in {{JE}}\|the legacy format\|Item format/Before 1.20.5\|the format in {{BE}}\|Item components}}
	{{~~redirect~~\|Component~~\|the text format\|Text component format~~}}{{exclusive\|java}}		{{for\|other uses\|Component}}{{exclusive\|java}}

	'''Data components''', or simply '''components''', are structured data used to store information and define behavior. Their IDs are [[Minecraft:namespaced identifier]]s, and their values can be any data type – see {{slink\|\|List of components}}.		'''Data components''', or simply '''components''', are structured data used to store information and define behavior. Their IDs are [[Minecraft:namespaced identifier]]s, and their values can be any data type – see {{slink\|\|List of components}}.