Minecraft:Hardcoded item properties (Java Edition) - Revision history

SyncBot: Sync: updated from Minecraft

2026-10-17T11:08:52Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:08, 17 October 2026
Line 5:		Line 5:
	{{cleanup}}		{{cleanup}}
	<!--{{TOC\|right}}-->		<!--{{TOC\|right}}-->
	'''Hardcoded item properties''' are aspects of [[Minecraft:item]]s which are tied to the [[Minecraft:Identifier#Java Edition usage\|IDs]] and cannot be customized fully via the use of [[Minecraft:commands]] or [[Minecraft:data pack]]s. That is, if an item has all of its [[Minecraft:Data component format\|item components]] removed, and is not a member of any [[Minecraft:Item tag (Java Edition)\|item tags]], referenced by any [[Minecraft:Recipe (Java Edition)\|recipe]]s, [[Minecraft:Villager trade definition\|trade]]s, [[Minecraft:Advancement definition\|advancement triggers]], or any other more esoteric data-driven definitions (e.g. [[Minecraft:vault]] unlock items, [[Minecraft:predicate]]s used in [[Minecraft:loot table]]s{{note\|Used for handling drops when using [[Minecraft:shears]]~~, unsure as to if others exist~~}} or what [[Minecraft:Enchantment definition\|enchantments]] can be applied to items), it still possesses a functionality based entirely on its item ID which cannot be removed from it, nor assigned to arbitrary other items.		'''Hardcoded item properties''' are aspects of [[Minecraft:item]]s which are tied to the [[Minecraft:Identifier#Java Edition usage\|IDs]] and cannot be customized fully via the use of [[Minecraft:commands]] or [[Minecraft:data pack]]s. That is, if an item has all of its [[Minecraft:Data component format\|item components]] removed, and is not a member of any [[Minecraft:Item tag (Java Edition)\|item tags]], referenced by any [[Minecraft:Recipe (Java Edition)\|recipe]]s, [[Minecraft:Villager trade definition\|trade]]s, [[Minecraft:Advancement definition\|advancement triggers]], or any other more esoteric data-driven definitions (e.g. [[Minecraft:vault]] unlock items, [[Minecraft:predicate]]s used in [[Minecraft:loot table]]s{{note\|Used for handling drops when using [[Minecraft:shears]]}} or what [[Minecraft:Enchantment definition\|enchantments]] can be applied to items), it still possesses a functionality based entirely on its item ID which cannot be removed from it, nor assigned to arbitrary other items.

	Many of the properties associated with items in the game have been made controllable with [[Minecraft:data component format]]; this intends to track things that are not currently controllable via any of the above data-driven item properties (though may be in future).		Many of the properties associated with items in the game have been made controllable with [[Minecraft:data component format]]; this intends to track things that are not currently controllable via any of the above data-driven item properties (though may be in future).

SyncBot: Sync: updated from Minecraft

2026-10-14T11:14:27Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:14, 14 October 2026
Line 2,909:		Line 2,909:
	* The shears take one of damage.		* The shears take one of damage.
	* The interaction returns success.		* The interaction returns success.
			{{anchor\|sheared}}
	'''3.''' Attempts to remove equipment from the entity. This is only possible if the following conditions are met simultaneously:		'''3.''' Attempts to remove equipment from the entity. This is only possible if the following conditions are met simultaneously:
	* The entity is a [[Minecraft:mob]]		* The entity is a [[Minecraft:mob]]
Line 2,915:		Line 2,915:
	* The player is not [[Minecraft:crouching\|{{Control\|crouching}}]]		* The player is not [[Minecraft:crouching\|{{Control\|crouching}}]]
	* If the entity is a wolf, the player is its owner; otherwise, the entity is not being ridden		* If the entity is a wolf, the player is its owner; otherwise, the entity is not being ridden
			* The entity is not a [[Minecraft:villager]] or a [[Minecraft:wandering trader]].{{Upcoming\|Java 26.4}}
	* At least one item in the entity's equipment slots has {{DCL\|equippable.can_be_sheared}} set to true and, unless the player is in Creative mode, does not have an enchantment with {{cd\|[[Minecraft:Enchantment_definition#prevent_armor_change\|prevent_armor_change]]}} effect components (e.g., [[Minecraft:Curse of Binding]] in vanilla)		* At least one item in the entity's equipment slots has {{DCL\|equippable.can_be_sheared}} set to true and, unless the player is in Creative mode, does not have an enchantment with {{cd\|[[Minecraft:Enchantment_definition#prevent_armor_change\|prevent_armor_change]]}} effect components (e.g., [[Minecraft:Curse of Binding]] in vanilla)
	In this case, a piece of equipment can be removed:		In this case, a piece of equipment can be removed:
Line 2,922:		Line 2,923:
	* Triggered [[Minecraft:Advancement_definition#minecraft:player_sheared_equipment\|{{cd\|player_sheared_equipment}}]] advancement trigger		* Triggered [[Minecraft:Advancement_definition#minecraft:player_sheared_equipment\|{{cd\|player_sheared_equipment}}]] advancement trigger
	* The interaction returns success.		* The interaction returns success.
	At most, one piece of equipment is dropped at a time, in the following order of slot priority: main hand, off-hand, feet, legs, chest, head, body and saddle.		At most, one piece of equipment is dropped at a time, in the following order of slot priority: main hand, off-hand, feet, legs, chest, head, body and saddle. Note that the item can be removed from any slot, regardless of the slot in {{DCL\|equippable.slot}}.

	'''4.''' ''wip''		'''4.''' ''wip''
	{{-}}		{{-}}

	===Mob===		===Mob===
	===CrossbowAttack===		===CrossbowAttack===

SyncBot: Sync: updated from Minecraft

2026-10-07T11:12:27Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:12, 7 October 2026
Line 1,105:		Line 1,105:
	* {{ItemLink\|Hanging Signs\|HangingSignItem\|link=#HangingSignItem}}		* {{ItemLink\|Hanging Signs\|HangingSignItem\|link=#HangingSignItem}}
	* {{ItemLink\|honeycomb\|HoneycombItem\|link=#HoneycombItem}}		* {{ItemLink\|honeycomb\|HoneycombItem\|link=#HoneycombItem}}
			* {{TOCSprite\|ItemLink\|Ice Ball\|IceBallItem}}{{Upcoming\|Java 26.4}}
	* {{ItemLink\|ink sac\|InkSacItem\|link=#InkSacItem}}		* {{ItemLink\|ink sac\|InkSacItem\|link=#InkSacItem}}
	* {{ItemLink\|goat horn\|InstrumentItem\|link=#InstrumentItem}}		* {{ItemLink\|goat horn\|InstrumentItem\|link=#InstrumentItem}}
Line 1,539:		Line 1,540:
	'''interactLivingEntity({{tooltip\|...\|ItemStack itemStack, Player player, LivingEntity target, InteractionHand type}})'''		'''interactLivingEntity({{tooltip\|...\|ItemStack itemStack, Player player, LivingEntity target, InteractionHand type}})'''
	{{hatnote\|Overrides method in [[#interactLivingEntity(...)\|{{jicp\|}}]]}}		{{hatnote\|Overrides method in [[#interactLivingEntity(...)\|{{jicp\|}}]]}}
			{{In development\|section=1\|removed=1\|Java\|\|26.4\|note=Replaced by the tag {{tag link\|item\|sheep_wool_dyes}}}}

	The interaction is only successful, instead of pass, when the interacting entity is a non-sheared live [[Minecraft:sheep]] of a different color than the {{cd\|dye}} component and the item stack has a {{cd\|dye}} component.		The interaction is only successful, instead of pass, when the interacting entity is a non-sheared live [[Minecraft:sheep]] of a different color than the {{cd\|dye}} component and the item stack has a {{cd\|dye}} component.
Line 1,918:		Line 1,920:
	{{-}}		{{-}}

			=== IceBallItem ===
			{{Expand section}}
			{{In development\|section=1\|Java\|\|26.4}}
			{{Infobox hardcoded item property\|class=IceBallItem\|Ice Ball\|impts={{cd\|ProjectileItem}}}}


			{{-}}
	=== GlowInkSacItem ===		=== GlowInkSacItem ===
	{{Infobox hardcoded item property\|class=GlowInkSacItem\|Glow Ink Sac\|impts={{cd\|SignApplicator}}}}		{{Infobox hardcoded item property\|class=GlowInkSacItem\|Glow Ink Sac\|impts={{cd\|SignApplicator}}}}
Line 2,359:		Line 2,368:
	* {{EntityLink\|Drowned\|{{jcp\|net.minecraft.world.entity.monster.zombie.Drowned}}\|link=#Drowned}}		* {{EntityLink\|Drowned\|{{jcp\|net.minecraft.world.entity.monster.zombie.Drowned}}\|link=#Drowned}}
	* {{EntityLink\|Trident\|{{jcp\|net.minecraft.world.entity.monster.zombie.Drowned.DrownedTridentAttackGoal}}\|link=#DrownedTridentAttackGoal}}		* {{EntityLink\|Trident\|{{jcp\|net.minecraft.world.entity.monster.zombie.Drowned.DrownedTridentAttackGoal}}\|link=#DrownedTridentAttackGoal}}
			* {{EntityLink\|Frostbite\|{{jcp\|net.minecraft.world.entity.monster.zombie.Frostbite}}\|link=#Frostbite}}{{Upcoming\|Java 26.4}}
	* {{EntityLink\|Zombie\|{{jcp\|net.minecraft.world.entity.monster.zombie.Zombie}}\|link=#Zombie}}		* {{EntityLink\|Zombie\|{{jcp\|net.minecraft.world.entity.monster.zombie.Zombie}}\|link=#Zombie}}
	* {{EntityLink\|Zombie Villager\|{{jcp\|net.minecraft.world.entity.monster.zombie.ZombieVillager}}\|link=#ZombieVillager}}		* {{EntityLink\|Zombie Villager\|{{jcp\|net.minecraft.world.entity.monster.zombie.ZombieVillager}}\|link=#ZombieVillager}}
Line 2,412:		Line 2,422:
	=== DispenseItemBehavior ===		=== DispenseItemBehavior ===
	{{Expand section}}		{{Expand section}}
	{{Infobox hardcoded item property\|class=DispenseItemBehavior\|Arrow\|Tipped Arrow\|Spectral Arrow\|Egg\|Blue Egg\|Brown Egg\|Snowball\|Bottle o' Enchanting\|Splash Potion\|Lingering Potion\|Firework Rocket\|Fire Charge\|Wind Charge\|Armor Stand\|Chest\|Oak Boat\|Spruce Boat\|Birch Boat\|Jungle Boat\|Dark Oak Boat\|Acacia Boat\|Cherry Boat\|Mangrove Boat\|Pale Oak Boat\|Bamboo Raft\|Oak Boat with Chest\|Spruce Boat with Chest\|Birch Boat with Chest\|Jungle Boat with Chest\|Dark Oak Boat with Chest\|Acacia Boat with Chest\|Cherry Boat with Chest\|Mangrove Boat with Chest\|Pale Oak Boat with Chest\|Bamboo Raft with Chest\|Lava Bucket\|Water Bucket\|Powder Snow Bucket\|Bucket of Salmon\|Bucket of Cod\|Bucket of Pufferfish\|Bucket of Tropical Fish\|Bucket of Axolotl\|Bucket of Tadpole\|Bucket\|Flint and Steel\|Bone Meal\|Wither Skeleton Skull\|Shulker Box\|White Shulker Box\|Orange Shulker Box\|Magenta Shulker Box\|Light Blue Shulker Box\|Yellow Shulker Box\|Lime Shulker Box\|Pink Shulker Box\|Gray Shulker Box\|Light Gray Shulker Box\|Cyan Shulker Box\|Purple Shulker Box\|Blue Shulker Box\|Brown Shulker Box\|Green Shulker Box\|Red Shulker Box\|Black Shulker Box\|Glass Bottle\|Glowstone\|Shears\|Brush\|Honeycomb\|Potion\|Minecart\|Minecart with Chest\|Minecart with Furnace\|Minecart with TNT\|Minecart with Hopper\|Minecart with Command Block\|pac=core.dispenser\|Inv=t}}		{{Infobox hardcoded item property\|class=DispenseItemBehavior\|Arrow\|Tipped Arrow\|Spectral Arrow\|Egg\|Blue Egg\|Brown Egg\|Snowball\|Bottle o' Enchanting\|Splash Potion\|Lingering Potion\|Firework Rocket\|Fire Charge\|Wind Charge\|Armor Stand\|Chest\|Oak Boat\|Spruce Boat\|Birch Boat\|Jungle Boat\|Dark Oak Boat\|Acacia Boat\|Cherry Boat\|Mangrove Boat\|Poplar Boat\|Pale Oak Boat\|Bamboo Raft\|Oak Boat with Chest\|Spruce Boat with Chest\|Birch Boat with Chest\|Jungle Boat with Chest\|Dark Oak Boat with Chest\|Acacia Boat with Chest\|Cherry Boat with Chest\|Mangrove Boat with Chest\|Poplar Boat with Chest\|Pale Oak Boat with Chest\|Bamboo Raft with Chest\|Lava Bucket\|Water Bucket\|Powder Snow Bucket\|Bucket of Salmon\|Bucket of Cod\|Bucket of Pufferfish\|Bucket of Tropical Fish\|Bucket of Axolotl\|Bucket of Sulfur Cube\|Bucket of Tadpole\|Bucket\|Flint and Steel\|Bone Meal\|Wither Skeleton Skull\|Shulker Box\|Glass Bottle\|Glowstone\|Shears\|Brush\|Honeycomb\|Potion\|Minecart\|Minecart with Chest\|Minecart with Furnace\|Minecart with TNT\|Minecart with Hopper\|Minecart with Command Block\|\|Items= {{Flatlist\|
			* {{BlockLink\|Shulker Boxes\|Dyed Shulker Box}} (ColorCollection)
			* {{ItemLink\|Ice Ball}}{{Upcoming\|Java 26.4}}}}
			\|pac=core.dispenser\|Inv=t}}

	'''bootStrap()'''		'''bootStrap()'''
Line 2,422:		Line 2,435:
	\|-		\|-
	\|{{InvLink\|Arrow}}		\|{{InvLink\|Arrow}}
	\|rowspan="11"\|ProjectileBehavior		\|rowspan="12"\|ProjectileBehavior
	\|-		\|-
	\|{{InvLink\|Tipped Arrow}}		\|{{InvLink\|Tipped Arrow}}
Line 2,431:		Line 2,444:
	\|-		\|-
	\|{{InvLink\|Snowball}}		\|{{InvLink\|Snowball}}
			\|-
			\|{{InvLink\|Ice Ball}}{{Upcoming\|Java 26.4}}
	\|-		\|-
	\|{{InvLink\|Bottle o' Enchanting}}		\|{{InvLink\|Bottle o' Enchanting}}
Line 2,454:		Line 2,469:
	\|-		\|-
	\|{{InvLink\|Lava Bucket}}		\|{{InvLink\|Lava Bucket}}
	\|rowspan="4"\|filledBucketBehavior		\|rowspan="5"\|filledBucketBehavior
	\|-		\|-
	\|{{InvLink\|Water Bucket}}		\|{{InvLink\|Water Bucket}}
Line 2,461:		Line 2,476:
	\|-		\|-
	\|{{ItemLink\|Bucket of aquatic mob}}		\|{{ItemLink\|Bucket of aquatic mob}}
			\|-
			\|{{ItemLink\|Bucket of Sulfur Cube}}
	\|-		\|-
	\|{{InvLink\|Bucket}} \|\|DefaultDispenseItemBehavior		\|{{InvLink\|Bucket}} \|\|DefaultDispenseItemBehavior
	\|-		\|-
	\|{{InvLink\|Flint and Steel}} \|\|~~OptionalDispenseItemBehavior~~		\|{{InvLink\|Flint and Steel}} \|\|FlintAndSteelDispenseItemBehavior
	\|-		\|-
	\|{{InvLink\|Bone Meal}} \|\|OptionalDispenseItemBehavior		\|{{InvLink\|Bone Meal}} \|\|OptionalDispenseItemBehavior
Line 2,499:		Line 2,516:

	{{-}}		{{-}}

	=== AnvilMenu ===		=== AnvilMenu ===

Line 2,947:		Line 2,965:
	===Drowned===		===Drowned===
	===DrownedTridentAttackGoal===		===DrownedTridentAttackGoal===
			===Frostbite===
	===Zombie===		===Zombie===
	===ZombieVillager===		===ZombieVillager===
Line 2,977:		Line 2,996:
	===LivingEntityRenderer===		===LivingEntityRenderer===
	===WitchRenderer===		===WitchRenderer===
	{{info needed section\|~~used~~ for ~~potions~~, ~~or something else?}}~~		{{info needed section\|More details}}
			Used for [[Minecraft:potion]] when renderedelized in the hand of the [[Minecraft:witch]], renderedelized tilted as if the witch were drinking.
	===AvatarRenderer===		===AvatarRenderer===
	===CuboidItemModelWrapper===		===CuboidItemModelWrapper===

SyncBot: Sync: updated from Minecraft

2026-09-20T11:09:37Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:09, 20 September 2026
Line 3,234:		Line 3,234:
	-->		-->
	\|{{HistoryLine\|\|26.3\|dev=snap1		\|{{HistoryLine\|\|26.3\|dev=snap1
	\|
	\|Removed {{jicp\|Bed}}. [[Minecraft:Bed]] (all 16 blocks in ColorCollection) are now just {{jicp\|Block}}. Previously, when placing a bed block (using the {{cd\|placeBlock(...)}}), it used update flags of 26 instead of 11.<ref>{{bug\|MC-308830}}</ref>		\|Removed {{jicp\|Bed}}. [[Minecraft:Bed]] (all 16 blocks in ColorCollection) are now just {{jicp\|Block}}. Previously, when placing a bed block (using the {{cd\|placeBlock(...)}}), it used update flags of 26 instead of 11.<ref>{{bug\|MC-308830}}</ref>
	\|{{Jicp\|Instrument}} now, in the method {{cd\|use(...)}}, hurt and break the item according to the new tag {{nbt\|int\|durability_damage}} from the [[Minecraft:instrument definition]], if it exists and is greater than 0. Furthermore, only add the cooldown if it is greater than {{cd\|0.0}}.		\|{{Jicp\|Instrument}} now, in the method {{cd\|use(...)}}, hurt and break the item according to the new tag {{nbt\|int\|durability_damage}} from the [[Minecraft:instrument definition]], if it exists and is greater than 0. Furthermore, only add the cooldown if it is greater than {{cd\|0.0}}.
Line 3,261:		Line 3,260:
	\|{{HistoryLine\|\|\|dev=?\|Villager food is now component controlled.}}		\|{{HistoryLine\|\|\|dev=?\|Villager food is now component controlled.}}
	\|{{HistoryLine\|\|\|dev=?\|Exploration maps are now handled differently.}}		\|{{HistoryLine\|\|\|dev=?\|Exploration maps are now handled differently.}}
			\|{{HistoryLine\|\|\|dev=?\|Composting is now component driven.}}
	}}		}}

SyncBot: Sync: updated from Minecraft

2026-09-19T11:14:03Z

Sync: updated from Minecraft

Show changes

SyncBot: Sync: updated from Minecraft

2026-09-16T11:21:53Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:21, 16 September 2026
Line 4:		Line 4:
	{{project\|Hardcoded item}}		{{project\|Hardcoded item}}
	{{cleanup}}		{{cleanup}}
			{{Update\|The article contains several templates as if version 26.3 had not yet been released.}}
	<!--{{TOC\|right}}-->		<!--{{TOC\|right}}-->
	'''Hardcoded item properties''' are aspects of [[Minecraft:item]]s which are tied to the [[Minecraft:Identifier#Java Edition usage\|IDs]] and cannot be customized fully via the use of [[Minecraft:commands]] or [[Minecraft:data pack]]s. That is, if an item has all of its [[Minecraft:Data component format\|item components]] removed, and is not a member of any [[Minecraft:Item tag (Java Edition)\|item tags]], referenced by any [[Minecraft:Recipe (Java Edition)\|recipe]]s, [[Minecraft:Villager trade definition\|trade]]s, [[Minecraft:Advancement definition\|advancement triggers]], or [[Minecraft:~~predicate~~]]~~{{note\|Used for~~ [[Minecraft:~~shears~~]] in [[Minecraft:loot table]]s~~.}}, or any other more esoteric data-driven definitions (e.g.~~ [[Minecraft:~~vault~~]] ~~unlock items~~, what [[Minecraft:Enchantment definition\|enchantments]] can be applied to items), it still possesses a functionality based entirely on its item ID which cannot be removed from it, nor assigned to arbitrary other items.		'''Hardcoded item properties''' are aspects of [[Minecraft:item]]s which are tied to the [[Minecraft:Identifier#Java Edition usage\|IDs]] and cannot be customized fully via the use of [[Minecraft:commands]] or [[Minecraft:data pack]]s. That is, if an item has all of its [[Minecraft:Data component format\|item components]] removed, and is not a member of any [[Minecraft:Item tag (Java Edition)\|item tags]], referenced by any [[Minecraft:Recipe (Java Edition)\|recipe]]s, [[Minecraft:Villager trade definition\|trade]]s, [[Minecraft:Advancement definition\|advancement triggers]], or any other more esoteric data-driven definitions (e.g. [[Minecraft:vault]] unlock items, [[Minecraft:predicate]]s used in [[Minecraft:loot table]]s{{note\|Used for handling drops when using [[Minecraft:shears]], unsure as to if others exist}} or what [[Minecraft:Enchantment definition\|enchantments]] can be applied to items), it still possesses a functionality based entirely on its item ID which cannot be removed from it, nor assigned to arbitrary other items.

	Many of the properties associated with items in the game have been made controllable with [[Minecraft:data component format]]; this intends to track things that are not currently controllable via any of the above data-driven item properties (though may be in future).		Many of the properties associated with items in the game have been made controllable with [[Minecraft:data component format]]; this intends to track things that are not currently controllable via any of the above data-driven item properties (though may be in future).
Line 87:		Line 88:
	In class {{jicp\|-.Properties}}, the game defines a series of functions that can be applied to an item and change its properties. However, the vast majority of these properties ultimately only modify the item's [[#Default components\|default data components]]		In class {{jicp\|-.Properties}}, the game defines a series of functions that can be applied to an item and change its properties. However, the vast majority of these properties ultimately only modify the item's [[#Default components\|default data components]]

	A complete list of default components in {{v\|java}} can be seen at [https://github.com/misode/mcmeta/blob/{{v\|java\|nolink=1}}-diff/items misode/mcmeta]. The list for {{v\|java-snap}} can be found [https://github.com/misode/mcmeta/tree/diff/items here].		A complete list of default components in {{v\|java}} can be seen at [https://github.com/misode/mcmeta/blob/{{v\|java\|nolink=1}}-diff/items misode/mcmeta]. {{#ifeq:{{v\|java-snap}}\|\|\|The list for {{v\|java-snap}} can be found [https://github.com/misode/mcmeta/tree/diff/items here].}}
	{{Collapse\|title=Note that some items are used as default components of other items.\|head=1}}		{{Collapse\|title=Note that some items are used as default components of other items.\|head=1}}
	<!--This is collapsing because it's not certain if it's a hardcoded property. But just to be safe, it's better to leave it collapsed than not include it on the page. -Aloi-->		<!--This is collapsing because it's not certain if it's a hardcoded property. But just to be safe, it's better to leave it collapsed than not include it on the page. -Aloi-->

SyncBot: Sync: updated from Minecraft

2026-09-15T11:09:42Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:09, 15 September 2026
Line 854:		Line 854:
	{{blist		{{blist
	\|class=treeview		\|class=treeview
	\|{{jicp\|-Stack}}.{{cd\|onUseTick({{tooltip\|...\|Level level, LivingEntity livingEntity, int ticksRemaining}})}}: Calls the method implemented in the item stack as item, after properties relating to {{DCL\|consumable}} and {{DCL\|~~kinetic_waapon~~}}~~{{verify\|Is this a typo, or does the code actually say this?}} components.~~		\|{{jicp\|-Stack}}.{{cd\|onUseTick({{tooltip\|...\|Level level, LivingEntity livingEntity, int ticksRemaining}})}}: Calls the method implemented in the item stack as item, after properties relating to {{DCL\|consumable}} and {{DCL\|kinetic_weapon}}
	{{blist\|class=treeview\|		{{blist\|class=treeview\|
	{{jcp\|net.minecraft.world.entity.LivingEntity}}.{{cd\|updateUsingItem({{tooltip\|...\|ItemStack useItem}})}}: Called at the beginning, in the {{jcp\|net.minecraft.server.level.ServerPlayer}} implementation after activating [[Minecraft:Advancement_definition#minecraft:\using_item\|{{cd\|using_item}}]] ~~tiger{{verify}}~~ criteria.		{{jcp\|net.minecraft.world.entity.LivingEntity}}.{{cd\|updateUsingItem({{tooltip\|...\|ItemStack useItem}})}}: Called at the beginning, in the {{jcp\|net.minecraft.server.level.ServerPlayer}} implementation after activating [[Minecraft:Advancement_definition#minecraft:using_item\|{{cd\|using_item}}]] trigger criteria.
	{{blist\|class=treeview\|		{{blist\|class=treeview\|
	{{jcp\|net.minecraft.world.entity.LivingEntity}}.{{cd\|updatingUsingItem()}}: Calls if the item stack used remains in the same hand of the entity.		{{jcp\|net.minecraft.world.entity.LivingEntity}}.{{cd\|updatingUsingItem()}}: Calls if the item stack used remains in the same hand of the entity.
Line 1,164:		Line 1,164:
	=== AirItem ===		=== AirItem ===

	{{~~hardcoded item property~~		{{Infobox hip\|class=AirItem\|block=1\|Air}}
	\|class=AirItem\|block=3\|Air}}

	Air has a block {{cd\|descriptionId}}, meaning its translation key is {{cd\|minecraft.block.air}}. However, unlike other items with this {{cd\|descriptionId}}, air is not an instance of {{jicp\|Block}}, because {{jicp\|Air}} does not extend {{jicp\|Block}}.		Air has a block {{cd\|descriptionId}}, meaning its translation key is {{cd\|minecraft.block.air}}. However, unlike other items with this {{cd\|descriptionId}}, air is not an instance of {{jicp\|Block}}, because {{jicp\|Air}} does not extend {{jicp\|Block}}.
Line 3,704:		Line 3,703:

	== History ==		== History ==
	{{info needed section\|History before [[Minecraft:Java Edition 26.1 Snapshot 1]] and after [[Minecraft:Java Edition 26.2]] <!--Previously, properties were controlled by NBT tags, so it still made sense to divide them between hardcoded and non-hardcoded properties. Although it's unlikely anyone will write the history from that long ago, NBT tags generally dealt with customizable aspects in Survival mode, unlike many components. Furthermore, since 2017 there have been properties controlled by tags and recipes that control the properties of items.--@Aloi4 -->}}		{{info needed section\|History before [[Minecraft:Java Edition 26.1 Snapshot 1]] and after [[Minecraft:Java Edition 26.3 Snapshot 2]] <!--Previously, properties were controlled by NBT tags, so it still made sense to divide them between hardcoded and non-hardcoded properties. Although it's unlikely anyone will write the history from that long ago, NBT tags generally dealt with customizable aspects in Survival mode, unlike many components. Furthermore, since 2017 there have been properties controlled by tags and recipes that control the properties of items.--@Aloi4 -->}}

	{{HistoryTable		{{HistoryTable
Line 3,814:		Line 3,813:
	-->		-->
	\|{{HistoryLine\|\|26.2\|dev=snap1		\|{{HistoryLine\|\|26.2\|dev=snap1
	\| Added items [[Minecraft:sulfur]], [[Minecraft:potent sulfur]], [[Minecraft:sulfur slab]], [[Minecraft:sulfur stairs]], [[Minecraft:sulfur wall]], [[Minecraft:polished sulfur block]], [[Minecraft:polished sulfur slab]], [[Minecraft:polished sulfur stairs]], [[Minecraft:polished sulfur wall]], [[Minecraft:sulfur bricks]], [[Minecraft:sulfur brick slab]], [[Minecraft:sulfur brick stairs]], [[Minecraft:sulfur brick wall]], [[Minecraft:cinnabar]], [[Minecraft:cinnabar slab]], [[Minecraft:cinnabar stairs]], [[Minecraft:cinnabar wall]], [[Minecraft:polished cinnabar block]], [[Minecraft:polished cinnabar slab]], [[Minecraft:polished cinnabar stairs]], [[Minecraft:polished cinnabar wall]], [[Minecraft:cinnabar bricks]], [[Minecraft:cinnabar brick slab]], [[Minecraft:cinnabar brick stairs]] and [[Minecraft:cinnabar brick wall]] as new instances of {{jicp\|Block}}		\| Added items [[Minecraft:sulfur]], [[Minecraft:potent sulfur]], [[Minecraft:sulfur slab]], [[Minecraft:sulfur stairs]], [[Minecraft:sulfur wall]], [[Minecraft:polished sulfur block]], [[Minecraft:polished sulfur slab]], [[Minecraft:polished sulfur stairs]], [[Minecraft:polished sulfur wall]], [[Minecraft:sulfur bricks]], [[Minecraft:sulfur brick slab]], [[Minecraft:sulfur brick stairs]], [[Minecraft:sulfur brick wall]], [[Minecraft:cinnabar]], [[Minecraft:cinnabar slab]], [[Minecraft:cinnabar stairs]], [[Minecraft:cinnabar wall]], [[Minecraft:polished cinnabar block]], [[Minecraft:polished cinnabar slab]], [[Minecraft:polished cinnabar stairs]], [[Minecraft:polished cinnabar wall]], [[Minecraft:cinnabar bricks]], [[Minecraft:cinnabar brick slab]], [[Minecraft:cinnabar brick stairs]], and [[Minecraft:cinnabar brick wall]] as new instances of {{jicp\|Block}}
	\| Added the item [[Minecraft:sulfur cube bucket]] as a new {{jicp\|MobBucket}} instance, with content (fluid) and emptySound is empty.		\| Added the item [[Minecraft:sulfur cube bucket]] as a new {{jicp\|MobBucket}} instance, with content (fluid) and emptySound is empty.
	\| Added the item [[Minecraft:sulfur cube spawn egg]] as a new {{jicp\|SpawnEgg}} instance.		\| Added the item [[Minecraft:sulfur cube spawn egg]] as a new {{jicp\|SpawnEgg}} instance.
Line 3,839:		Line 3,838:
	}}		}}
	\|{{HistoryLine\|\|\|dev=snap7		\|{{HistoryLine\|\|\|dev=snap7
	\| Added the item music disc bounce, as just a instance of {{jicp\|}}.		\| Added the item [[Minecraft:music disc bounce]], as just a instance of {{jicp\|}}.
	}}		}}
	\|{{HistoryLine\|\|\|dev=pre1		\|{{HistoryLine\|\|\|dev=pre1
Line 3,847:		Line 3,846:
	26.2 end!		26.2 end!
	-->		-->
	\|{{HistoryLine\|\|26.3\|dev=?\|~~Shovels~~ are now just ~~Item~~.}}		\|{{HistoryLine\|\|26.3\|dev=snap1
	\|{{~~HistoryLine~~\|\|\|~~dev=?~~\|~~Axes are now just Item~~.}}		\|
	\|{{~~HistoryLine~~\|\|\|~~dev=?~~\|~~Hoes are now just Item~~.}}		\|Removed {{jicp\|Bed}}. [[Minecraft:Bed]] (all 16 blocks in ColorCollection) are now just {{jicp\|Block}}. Previously, when placing a bed block (using the {{cd\|placeBlock(...)}}), it used update flags of 26 instead of 11.<ref>{{bug\|MC-308830}}</ref>
	\|{{~~HistoryLine~~\|\|\|~~dev=?~~\|~~Something significant~~ has ~~changed about decorated~~ pot ~~patterns~~ and ~~pot decorations~~.}}		\|{{Jicp\|Instrument}} now, in the method {{cd\|use(...)}}, hurt and break the item according to the new tag {{nbt\|int\|durability_damage}} from the [[Minecraft:instrument definition]], if it exists and is greater than 0. Furthermore, only add the cooldown if it is greater than {{cd\|0.0}}.
	\|{{HistoryLine\|\|\|dev=?\|~~Beds~~ are now just ~~BlockItem~~.}}		\| {{jicp\|SpawnEgg}} when used ({{cd\|useOn(...)}}) by op players in [[Minecraft:monster spawner]] or [[Minecraft:trial spawner]], sets the data according to the {{DCL\|entity_data}} component; previously, only the entity id was set.
			\| Access to items in {{jcp\|net.minecraft.world.level.block.entity.DecoratedPotPatterns}} has been removed and replaced by the component {{DCL\|provides_pottery_pattern}}. Previously, the sides of the decorated pot were saved with item ids, and each id was associated with a texture.
			\| Access to items in {{jcp\|net.minecraft.world.level.block.entity.PotDecorations}} has been removed; the [[Minecraft:brick]] no longer has the property of being the default item for [[Minecraft:decorated pot]] sides, making it possible to decorate pots with an empty side.
			\| Added [[Minecraft:poplar planks]], [[Minecraft:poplar sapling]], [[Minecraft:poplar log]], [[Minecraft:stripped poplar log]], [[Minecraft:stripped poplar wood]], [[Minecraft:poplar wood]], [[Minecraft:Red Poplar Leaves\|red poplar leaves]], [[Minecraft:Orange Poplar Leaves\|orange poplar leaves]], [[Minecraft:Yellow Poplar Leaves\|yellow poplar leaves]], [[Minecraft:red shrub]], [[Minecraft:wool stairs]] (ColorCollection), [[Minecraft:wool slab]] (ColorCollection), [[Minecraft:shelf mushroom]], [[Minecraft:poplar slab]], [[Minecraft:poplar shelf]], [[Minecraft:poplar fence]], [[Minecraft:poplar stairs]], [[Minecraft:poplar button]], [[Minecraft:poplar pressure plate]], [[Minecraft:poplar door]], [[Minecraft:poplar trapdoor]], and [[Minecraft:poplar fence gate]] as new instances of {{jicp\|Block}}.
			\| Added [[Minecraft:poplar boat]] and [[Minecraft:poplar boat with chest]] as new instances of {{jicp\|Boat}}.
			\| Added [[Minecraft:poplar sign]] as new istance of {{jicp\|Sign}}.
			\| Added [[Minecraft:poplar hanging sign]] as new istance of {{jicp\|HangingSign}}.
			\| In {{jicp\|Axe}}, poplar wood and poplar log were added to {{cd\|STRIPPABLES}}
			\| Added potted poplar sapling, a new instance of {{jbcp\|FlowerPot}}. Thus, through the {{cd\|useItemOn(...)}} method in {{jbcp\|FlowerPot}}, which import the {{jicp\|Block}}, the poplar sapling has the hardcoded property of interacting with the [[Minecraft:flower pot]].
			\| The new poplar boat and poplar boat with chest items have the behavior {{cd\|BoatDispenseItemBehavior}} in {{jcp\|net.minecraft.core.dispenser.DispenseItemBehavior}}.
			}}
			<!--26.3 snap1 end -->
			\|{{HistoryLine\|\|\|dev=snap2
			\| {{jicp\|Axe}}, {{jicp\|Hoe}}, and {{jicp\|Shovel}} have been removed. All items previously belonging to these classes ([[Minecraft:axes]], [[Minecraft:hoes]], and [[Minecraft:shovels]]) are now just {{jicp\|}}, and their behavior, previously defined by their class properties, is now given by {{DCL\|block_transformer}}. In the case of the shovels, some properties now depend on the tag {{tag link\|item\|dowses_campfires}}.
			\| The method {{cd\|useOn(...)}}, in {{jicp\|}}, transforms blocks according to the component {{cd\|block_transformer}} or returns {{cd\|PASS}} if it does not exist. Previously it always returned {{cd\|PASS}}.
			\| {{jicp\|Honeycomb}} now play a sound in the {{cd\|useOn(...)}} and {{cd\|tryApplyToSign(...)}} methods.
			\| In {{jicp\|DispenseItemBehavior}}, the behavior of [[Minecraft:honeycomb]] now play a sound.
			}}
			<!--26.3 snap2 end -->
	\|{{HistoryLine\|\|\|dev=?\|Brewing is now data-driven using the recipe system, removing some hardcoded item data as a result.}}		\|{{HistoryLine\|\|\|dev=?\|Brewing is now data-driven using the recipe system, removing some hardcoded item data as a result.}}
	\|{{HistoryLine\|\|\|dev=?\|Added CushionItem.}}		\|{{HistoryLine\|\|\|dev=?\|Added CushionItem.}}
	\|{{HistoryLine\|\|\|dev=?\|~~Dappled forest biome blocks~~, ~~wool slabs and stairs, and~~ concrete slabs and stairs, now exist under block item definitions of some sort.}}		\|{{HistoryLine\|\|\|dev=?\|Straw bed, concrete slabs and stairs, now exist under block item definitions of some sort.}}
	\|{{HistoryLine\|\|\|dev=?\|Villager food is now component controlled.}}		\|{{HistoryLine\|\|\|dev=?\|Villager food is now component controlled.}}
	\|{{HistoryLine\|\|\|dev=?\|Exploration maps are now handled differently.}}		\|{{HistoryLine\|\|\|dev=?\|Exploration maps are now handled differently.}}

SyncBot: Sync: updated from Minecraft

2026-09-14T11:06:42Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:06, 14 September 2026
Line 3,540:		Line 3,540:

	{\| class="wikitable"		{\| class="wikitable"
	! Items		! Items
	! Poits		! Poits{{verify\|as opposed to points?}}
	\|-		\|-
	\| {{ItemLink\|Bread}} \|\| 4		\| {{ItemLink\|Bread}} \|\| 4
Line 3,577:		Line 3,577:
	===LivingEntityRenderer===		===LivingEntityRenderer===
	===WitchRenderer===		===WitchRenderer===
			{{info needed section\|used for potions, or something else?}}
	===AvatarRenderer===		===AvatarRenderer===
	===CuboidItemModelWrapper===		===CuboidItemModelWrapper===

SyncBot: Sync: updated from Minecraft

2026-09-12T11:05:12Z

Sync: updated from Minecraft

Show changes

SyncBot: Sync: updated from Minecraft

2026-09-11T11:04:54Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:04, 11 September 2026
Line 7:		Line 7:

	<!--{{TOC\|right}}-->		<!--{{TOC\|right}}-->
	'''Hardcoded item properties''' are aspects of [[Minecraft:item]]s which are tied to the [[Minecraft:Identifier#Java Edition usage\|IDs]] and cannot be customized fully via the use of [[Minecraft:commands]] or [[Minecraft:data pack]]s. That is, if an item has all of its [[Minecraft:Data component format\|item components]] removed, and is not a member of any [[Minecraft:Item tag (Java Edition)\|item tags]], referenced by any [[Minecraft:~~Recipe_~~(~~Java_Edition~~)\|recipe]]s, [[Minecraft:Villager trade definition\|trade]]s, [[Minecraft:Advancement definition\|advancement triggers]], or [[Minecraft:predicate]]{{note\|Used for [[Minecraft:shears]] in [[Minecraft:loot table]]s.}}, or any other more esoteric data-driven definitions (e.g. [[Minecraft:vault]] unlock items), it still possesses a functionality based entirely on its item ID which cannot be removed from it, nor assigned to arbitrary other items.		'''Hardcoded item properties''' are aspects of [[Minecraft:item]]s which are tied to the [[Minecraft:Identifier#Java Edition usage\|IDs]] and cannot be customized fully via the use of [[Minecraft:commands]] or [[Minecraft:data pack]]s. That is, if an item has all of its [[Minecraft:Data component format\|item components]] removed, and is not a member of any [[Minecraft:Item tag (Java Edition)\|item tags]], referenced by any [[Minecraft:Recipe (Java Edition)\|recipe]]s, [[Minecraft:Villager trade definition\|trade]]s, [[Minecraft:Advancement definition\|advancement triggers]], or [[Minecraft:predicate]]{{note\|Used for [[Minecraft:shears]] in [[Minecraft:loot table]]s.}}, or any other more esoteric data-driven definitions (e.g. [[Minecraft:vault]] unlock items, what [[Minecraft:Enchantment definition\|enchantments]] can be applied to items), it still possesses a functionality based entirely on its item ID which cannot be removed from it, nor assigned to arbitrary other items.

	Many of the properties associated with items in the game have been made controllable with [[Minecraft:data component format]]; this intends to track things that are not currently controllable via ~~components,~~ item ~~tags, recipes, advancements, [[Minecraft:Enchantment_definition\|enchantments]] and trades~~ (though may be in future).		Many of the properties associated with items in the game have been made controllable with [[Minecraft:data component format]]; this intends to track things that are not currently controllable via any of the above data-driven item properties (though may be in future).

	Some properties are mixed, where they depend both on the hardcoded parts and on references to components, tags, etc. In these cases, items with the same components, tags, etc., would have different properties depending on the item's ID. For example, the properties of the [[Minecraft:spawn egg]], which depend on both the item's ID (being an instance of [[#SpawnEggItem\|SpawnEggItem]]) and the component {{DCL\|entity_data}}. These properties are also described on this page.		Some properties are mixed, where they depend both on the hardcoded parts and on references to components, tags, etc. In these cases, items with the same components, tags, etc., would have different properties depending on the item's ID. For example, the properties of the [[Minecraft:spawn egg]], which depend on both the item's ID (being an instance of [[#SpawnEggItem\|SpawnEggItem]]) and the component {{DCL\|entity_data}}. These properties are also described on this page.
Line 834:		Line 834:
	===getDefaultMaxStackSize()===		===getDefaultMaxStackSize()===
	-->		-->
	===onUseTick(...)===		=== onUseTick(...) ===

	{\| class="wikitable"		{\| class="wikitable"
	\|+ style="text-align: left \| onUseTick		\|+ style="text-align: left \| onUseTick
Line 857:		Line 856:
	{{blist		{{blist
	\|class=treeview		\|class=treeview
	\|{{jicp\|-Stack}}.{{cd\|onUseTick({{tooltip\|...\|Level level, LivingEntity livingEntity, int ticksRemaining}})}}: Calls the method implemented in the item stack as item, after properties relating to {{DCL\|consumable}} and {{DCL\|kinetic_waapon}} components.		\|{{jicp\|-Stack}}.{{cd\|onUseTick({{tooltip\|...\|Level level, LivingEntity livingEntity, int ticksRemaining}})}}: Calls the method implemented in the item stack as item, after properties relating to {{DCL\|consumable}} and {{DCL\|kinetic_waapon}}{{verify\|Is this a typo, or does the code actually say this?}} components.
	{{blist\|class=treeview\|		{{blist\|class=treeview\|
	{{jcp\|net.minecraft.world.entity.LivingEntity}}.{{cd\|updateUsingItem({{tooltip\|...\|ItemStack useItem}})}}: Called at the beginning, in the {{jcp\|net.minecraft.server.level.ServerPlayer}} implementation after activating [[Minecraft:Advancement_definition#minecraft:\using_item\|{{cd\|using_item}}]] tiger criteria.		{{jcp\|net.minecraft.world.entity.LivingEntity}}.{{cd\|updateUsingItem({{tooltip\|...\|ItemStack useItem}})}}: Called at the beginning, in the {{jcp\|net.minecraft.server.level.ServerPlayer}} implementation after activating [[Minecraft:Advancement_definition#minecraft:\using_item\|{{cd\|using_item}}]] tiger{{verify}} criteria.
	{{blist\|class=treeview\|		{{blist\|class=treeview\|
	{{jcp\|net.minecraft.world.entity.LivingEntity}}.{{cd\|updatingUsingItem()}}: Calls if the item stack used remains in the same hand of the entity.		{{jcp\|net.minecraft.world.entity.LivingEntity}}.{{cd\|updatingUsingItem()}}: Calls if the item stack used remains in the same hand of the entity.
Line 2,025:		Line 2,024:

	=== PlaceOnWaterBlockItem ===		=== PlaceOnWaterBlockItem ===
	{{~~empty~~ section}}		{{info needed section\|Presumably concerns lily pads and frogspawn, but what about spawn eggs and boats?}}

	=== PlayerHeadItem ===		=== PlayerHeadItem ===
	{{~~empty~~ section}}		{{info needed section\|Is this why {{bug\|MC-166998}}/{{bug\|MC-301817}} exist (aka heads using hardcoded rendering rather than either rendering an item model or equipment definition), or does that belong somewhere else?}}

	=== PotionItem ===		=== PotionItem ===

Line 3,703:		Line 3,704:

	== History ==		== History ==
	{{info needed section\|History before [[Minecraft:Java Edition 26.1 Snapshot 1]] and after [[Minecraft:Java Edition 26.2]] <!--Previously, properties were controlled by NBT tags, so it still made sense to divide them between hardcoded and non-hardcoded properties. Although it's unlikely anyone will write the history from that long ago, NBT tags generally dealt with customizable aspects in Survival mode, unlike many components. Furthermore, since 2017 there have been properties controlled by tags and recipes that control the properties of items.--@Aloi4 --> (e.g. removal of bed item and what it was replaced by/what changed, or how decorated pot handling was modified, and brewing migrated to recipes). also since at least three useon types are being removed in 26.3 those should be listed here}}		{{info needed section\|History before [[Minecraft:Java Edition 26.1 Snapshot 1]] and after [[Minecraft:Java Edition 26.2]] <!--Previously, properties were controlled by NBT tags, so it still made sense to divide them between hardcoded and non-hardcoded properties. Although it's unlikely anyone will write the history from that long ago, NBT tags generally dealt with customizable aspects in Survival mode, unlike many components. Furthermore, since 2017 there have been properties controlled by tags and recipes that control the properties of items.--@Aloi4 -->}}

	{{HistoryTable		{{HistoryTable
	\|{{HistoryLine\|~~Java~~}}		\|{{HistoryLine\|java}}
	\|{{HistoryLine\|\|1.13\|dev=17w43a\|Add [[Minecraft:datapack]] that control [[Minecraft:Advancement_definition\|advancement]]. Items used in advancement triggers are no longer hardcoded, such as iron bars, stone pickaxes, and lava buckets.}}		\|{{HistoryLine\|\|1.13\|dev=17w43a\|Add [[Minecraft:datapack]] that control [[Minecraft:Advancement_definition\|advancement]]. Items used in advancement triggers are no longer hardcoded, such as iron bars, stone pickaxes, and lava buckets.}}
	\|{{HistoryLine\|\|\|dev=17w48a\|[[Minecraft:Recipe (Java Edition)\|Recipes]] are now controlled by datapacks, so most recipes are no longer hardcoded, with the exception of special crafting recipes}}		\|{{HistoryLine\|\|\|dev=17w48a\|[[Minecraft:Recipe (Java Edition)\|Recipes]] are now controlled by datapacks, so most recipes are no longer hardcoded, with the exception of special crafting recipes}}
	\|{{HistoryLine\|\|\|dev=17w49a\|Added [[Minecraft:Tag (Java Edition)\|tag]]s, with the item tags {{tag link\|item\|planks\|wool}}. So, the properties of planks, repair tools, shields, and wool to be used with fuel were no longer hardcoded.}}		\|{{HistoryLine\|\|\|dev=17w49a\|Added [[Minecraft:Tag (Java Edition)\|tag]]s, with the item tags {{tag link\|item\|planks\|wool}}. So, the properties of planks, repair tools, shields, and wool to be used with fuel were no longer hardcoded.}}
	\|{{HistoryLine\|\|1.14\|dev=18w43a\|Added {{cd\|match_tool}} loot table condition, Now, the drop rate for using [[Minecraft:shears]] is controlled by [[Minecraft:loot tables]].{{Info needed\|The loot table already existed previously, so how was the drop rate controlled?}}}}		\|{{HistoryLine\|\|1.14\|dev=18w43a\|Added {{cd\|match_tool}} loot table condition, Now, the drop rate for using [[Minecraft:shears]] is controlled by [[Minecraft:loot tables]].{{Info needed\|The loot table already existed previously, so how was the drop rate controlled?}}}}
	\|{{HistoryLine\|\|1.20.5\|dev=24w09a\|Item NBT has been effectively removed, being replaced by the new [[Minecraft:data component format]]. Some hardcoded properties of items have also been migrated to this system.{{info needed\|which? ~~I know enchantment_glint_override was one of them, but~~ surely there were others?}}}}		\|{{HistoryLine\|\|1.20.5\|dev=24w09a\|Item NBT has been effectively removed, being replaced by the new [[Minecraft:data component format]]. Some hardcoded properties of items have also been migrated to this system.{{info needed\|which? surely there were others besides those mentioned below?}}}}
			\|{{HistoryLine\|\|\|dev=?\|The enchantment glint override component has been added, which presumably supplanted some unspecified hardcoded behaviour.}}
			\|{{HistoryLine\|\|\|dev=?\|Food data is now a component, presumably replacing hardcoded data definitions.}}
			\|{{HistoryLine\|\|\|dev=?\|Maximum item stack size is now a component, presumably replacing hardcoded data definitions.}}
			\|{{HistoryLine\|\|\|dev=?\|The maximum amount of damage an item can withstand is now a component, presumably replacing hardcoded data definitions.}}
			\|{{HistoryLine\|\|\|dev=?\|Whether items are destroyed by fire and lava or not is now a component, presumably replacing hardcoded data definitions.}}
			\|{{HistoryLine\|\|\|dev=?\|Rarity is now controlled by a component, presumably replacing hardcoded data definitions.}}
			\|{{HistoryLine\|\|\|dev=?\|Tool data is now a component, presumably replacing hardcoded data definitions.}}
			\|{{HistoryLine\|\|\|dev=?\|Whether tooltips are visible is now controlled by a component, presumably replacing hardcoded data definitions.}}
			\|{{HistoryLine\|\|\|dev=?\|Item names can now be controlled by a component, presumably replacing hardcoded data definitions.}}
	\|{{HistoryLine\|\|1.21\|dev=24w18a\|[[Minecraft:Enchantment definition\|Enchantment]]s are now controlled by datapacks, so the property of being enchanted by a certain enchantment has ceased to be hardcoded, except for [[Minecraft:book]].}}		\|{{HistoryLine\|\|1.21\|dev=24w18a\|[[Minecraft:Enchantment definition\|Enchantment]]s are now controlled by datapacks, so the property of being enchanted by a certain enchantment has ceased to be hardcoded, except for [[Minecraft:book]].}}
			\|{{HistoryLine\|\|\|dev=?\|Output items from eating food is now controlled by a component, presumably replacing hardcoded data definitions.}}
			\|{{HistoryLine\|\|\|dev=?\|Jukebox item usage is now a component, presumably replacing hardcoded data definitions.}}
	<!--		<!--
	26.1 Start		26.1 Start
Line 3,835:		Line 3,847:
	26.2 end!		26.2 end!
	-->		-->
			\|{{HistoryLine\|\|26.3\|dev=?\|Shovels are now just Item.}}
			\|{{HistoryLine\|\|\|dev=?\|Axes are now just Item.}}
			\|{{HistoryLine\|\|\|dev=?\|Hoes are now just Item.}}
			\|{{HistoryLine\|\|\|dev=?\|Something significant has changed about decorated pot patterns and pot decorations.}}
			\|{{HistoryLine\|\|\|dev=?\|Beds are now just BlockItem.}}
			\|{{HistoryLine\|\|\|dev=?\|Brewing is now data-driven using the recipe system, removing some hardcoded item data as a result.}}
			\|{{HistoryLine\|\|\|dev=?\|Added CushionItem.}}
			\|{{HistoryLine\|\|\|dev=?\|Dappled forest biome blocks, wool slabs and stairs, and concrete slabs and stairs, now exist under block item definitions of some sort.}}
			\|{{HistoryLine\|\|\|dev=?\|Villager food is now component controlled.}}
			\|{{HistoryLine\|\|\|dev=?\|Exploration maps are now handled differently.}}
	}}		}}

← Older revision		Revision as of 11:09, 20 September 2026
Line 3,234:		Line 3,234:
	-->		-->
	\|{{HistoryLine\|\|26.3\|dev=snap1		\|{{HistoryLine\|\|26.3\|dev=snap1
	\|
	\|Removed {{jicp\|Bed}}. [[Minecraft:Bed]] (all 16 blocks in ColorCollection) are now just {{jicp\|Block}}. Previously, when placing a bed block (using the {{cd\|placeBlock(...)}}), it used update flags of 26 instead of 11.<ref>{{bug\|MC-308830}}</ref>		\|Removed {{jicp\|Bed}}. [[Minecraft:Bed]] (all 16 blocks in ColorCollection) are now just {{jicp\|Block}}. Previously, when placing a bed block (using the {{cd\|placeBlock(...)}}), it used update flags of 26 instead of 11.<ref>{{bug\|MC-308830}}</ref>
	\|{{Jicp\|Instrument}} now, in the method {{cd\|use(...)}}, hurt and break the item according to the new tag {{nbt\|int\|durability_damage}} from the [[Minecraft:instrument definition]], if it exists and is greater than 0. Furthermore, only add the cooldown if it is greater than {{cd\|0.0}}.		\|{{Jicp\|Instrument}} now, in the method {{cd\|use(...)}}, hurt and break the item according to the new tag {{nbt\|int\|durability_damage}} from the [[Minecraft:instrument definition]], if it exists and is greater than 0. Furthermore, only add the cooldown if it is greater than {{cd\|0.0}}.
Line 3,261:		Line 3,260:
	\|{{HistoryLine\|\|\|dev=?\|Villager food is now component controlled.}}		\|{{HistoryLine\|\|\|dev=?\|Villager food is now component controlled.}}
	\|{{HistoryLine\|\|\|dev=?\|Exploration maps are now handled differently.}}		\|{{HistoryLine\|\|\|dev=?\|Exploration maps are now handled differently.}}
			\|{{HistoryLine\|\|\|dev=?\|Composting is now component driven.}}
	}}		}}

← Older revision		Revision as of 11:21, 16 September 2026
Line 4:		Line 4:
	{{project\|Hardcoded item}}		{{project\|Hardcoded item}}
	{{cleanup}}		{{cleanup}}
			{{Update\|The article contains several templates as if version 26.3 had not yet been released.}}
	<!--{{TOC\|right}}-->		<!--{{TOC\|right}}-->
	'''Hardcoded item properties''' are aspects of [[Minecraft:item]]s which are tied to the [[Minecraft:Identifier#Java Edition usage\|IDs]] and cannot be customized fully via the use of [[Minecraft:commands]] or [[Minecraft:data pack]]s. That is, if an item has all of its [[Minecraft:Data component format\|item components]] removed, and is not a member of any [[Minecraft:Item tag (Java Edition)\|item tags]], referenced by any [[Minecraft:Recipe (Java Edition)\|recipe]]s, [[Minecraft:Villager trade definition\|trade]]s, [[Minecraft:Advancement definition\|advancement triggers]], or [[Minecraft:~~predicate~~]]~~{{note\|Used for~~ [[Minecraft:~~shears~~]] in [[Minecraft:loot table]]s~~.}}, or any other more esoteric data-driven definitions (e.g.~~ [[Minecraft:~~vault~~]] ~~unlock items~~, what [[Minecraft:Enchantment definition\|enchantments]] can be applied to items), it still possesses a functionality based entirely on its item ID which cannot be removed from it, nor assigned to arbitrary other items.		'''Hardcoded item properties''' are aspects of [[Minecraft:item]]s which are tied to the [[Minecraft:Identifier#Java Edition usage\|IDs]] and cannot be customized fully via the use of [[Minecraft:commands]] or [[Minecraft:data pack]]s. That is, if an item has all of its [[Minecraft:Data component format\|item components]] removed, and is not a member of any [[Minecraft:Item tag (Java Edition)\|item tags]], referenced by any [[Minecraft:Recipe (Java Edition)\|recipe]]s, [[Minecraft:Villager trade definition\|trade]]s, [[Minecraft:Advancement definition\|advancement triggers]], or any other more esoteric data-driven definitions (e.g. [[Minecraft:vault]] unlock items, [[Minecraft:predicate]]s used in [[Minecraft:loot table]]s{{note\|Used for handling drops when using [[Minecraft:shears]], unsure as to if others exist}} or what [[Minecraft:Enchantment definition\|enchantments]] can be applied to items), it still possesses a functionality based entirely on its item ID which cannot be removed from it, nor assigned to arbitrary other items.

	Many of the properties associated with items in the game have been made controllable with [[Minecraft:data component format]]; this intends to track things that are not currently controllable via any of the above data-driven item properties (though may be in future).		Many of the properties associated with items in the game have been made controllable with [[Minecraft:data component format]]; this intends to track things that are not currently controllable via any of the above data-driven item properties (though may be in future).
Line 87:		Line 88:
	In class {{jicp\|-.Properties}}, the game defines a series of functions that can be applied to an item and change its properties. However, the vast majority of these properties ultimately only modify the item's [[#Default components\|default data components]]		In class {{jicp\|-.Properties}}, the game defines a series of functions that can be applied to an item and change its properties. However, the vast majority of these properties ultimately only modify the item's [[#Default components\|default data components]]

	A complete list of default components in {{v\|java}} can be seen at [https://github.com/misode/mcmeta/blob/{{v\|java\|nolink=1}}-diff/items misode/mcmeta]. The list for {{v\|java-snap}} can be found [https://github.com/misode/mcmeta/tree/diff/items here].		A complete list of default components in {{v\|java}} can be seen at [https://github.com/misode/mcmeta/blob/{{v\|java\|nolink=1}}-diff/items misode/mcmeta]. {{#ifeq:{{v\|java-snap}}\|\|\|The list for {{v\|java-snap}} can be found [https://github.com/misode/mcmeta/tree/diff/items here].}}
	{{Collapse\|title=Note that some items are used as default components of other items.\|head=1}}		{{Collapse\|title=Note that some items are used as default components of other items.\|head=1}}
	<!--This is collapsing because it's not certain if it's a hardcoded property. But just to be safe, it's better to leave it collapsed than not include it on the page. -Aloi-->		<!--This is collapsing because it's not certain if it's a hardcoded property. But just to be safe, it's better to leave it collapsed than not include it on the page. -Aloi-->

← Older revision		Revision as of 11:09, 15 September 2026
Line 854:		Line 854:
	{{blist		{{blist
	\|class=treeview		\|class=treeview
	\|{{jicp\|-Stack}}.{{cd\|onUseTick({{tooltip\|...\|Level level, LivingEntity livingEntity, int ticksRemaining}})}}: Calls the method implemented in the item stack as item, after properties relating to {{DCL\|consumable}} and {{DCL\|~~kinetic_waapon~~}}~~{{verify\|Is this a typo, or does the code actually say this?}} components.~~		\|{{jicp\|-Stack}}.{{cd\|onUseTick({{tooltip\|...\|Level level, LivingEntity livingEntity, int ticksRemaining}})}}: Calls the method implemented in the item stack as item, after properties relating to {{DCL\|consumable}} and {{DCL\|kinetic_weapon}}
	{{blist\|class=treeview\|		{{blist\|class=treeview\|
	{{jcp\|net.minecraft.world.entity.LivingEntity}}.{{cd\|updateUsingItem({{tooltip\|...\|ItemStack useItem}})}}: Called at the beginning, in the {{jcp\|net.minecraft.server.level.ServerPlayer}} implementation after activating [[Minecraft:Advancement_definition#minecraft:\using_item\|{{cd\|using_item}}]] ~~tiger{{verify}}~~ criteria.		{{jcp\|net.minecraft.world.entity.LivingEntity}}.{{cd\|updateUsingItem({{tooltip\|...\|ItemStack useItem}})}}: Called at the beginning, in the {{jcp\|net.minecraft.server.level.ServerPlayer}} implementation after activating [[Minecraft:Advancement_definition#minecraft:using_item\|{{cd\|using_item}}]] trigger criteria.
	{{blist\|class=treeview\|		{{blist\|class=treeview\|
	{{jcp\|net.minecraft.world.entity.LivingEntity}}.{{cd\|updatingUsingItem()}}: Calls if the item stack used remains in the same hand of the entity.		{{jcp\|net.minecraft.world.entity.LivingEntity}}.{{cd\|updatingUsingItem()}}: Calls if the item stack used remains in the same hand of the entity.
Line 1,164:		Line 1,164:
	=== AirItem ===		=== AirItem ===

	{{~~hardcoded item property~~		{{Infobox hip\|class=AirItem\|block=1\|Air}}
	\|class=AirItem\|block=3\|Air}}

	Air has a block {{cd\|descriptionId}}, meaning its translation key is {{cd\|minecraft.block.air}}. However, unlike other items with this {{cd\|descriptionId}}, air is not an instance of {{jicp\|Block}}, because {{jicp\|Air}} does not extend {{jicp\|Block}}.		Air has a block {{cd\|descriptionId}}, meaning its translation key is {{cd\|minecraft.block.air}}. However, unlike other items with this {{cd\|descriptionId}}, air is not an instance of {{jicp\|Block}}, because {{jicp\|Air}} does not extend {{jicp\|Block}}.
Line 3,704:		Line 3,703:

	== History ==		== History ==
	{{info needed section\|History before [[Minecraft:Java Edition 26.1 Snapshot 1]] and after [[Minecraft:Java Edition 26.2]] <!--Previously, properties were controlled by NBT tags, so it still made sense to divide them between hardcoded and non-hardcoded properties. Although it's unlikely anyone will write the history from that long ago, NBT tags generally dealt with customizable aspects in Survival mode, unlike many components. Furthermore, since 2017 there have been properties controlled by tags and recipes that control the properties of items.--@Aloi4 -->}}		{{info needed section\|History before [[Minecraft:Java Edition 26.1 Snapshot 1]] and after [[Minecraft:Java Edition 26.3 Snapshot 2]] <!--Previously, properties were controlled by NBT tags, so it still made sense to divide them between hardcoded and non-hardcoded properties. Although it's unlikely anyone will write the history from that long ago, NBT tags generally dealt with customizable aspects in Survival mode, unlike many components. Furthermore, since 2017 there have been properties controlled by tags and recipes that control the properties of items.--@Aloi4 -->}}

	{{HistoryTable		{{HistoryTable
Line 3,814:		Line 3,813:
	-->		-->
	\|{{HistoryLine\|\|26.2\|dev=snap1		\|{{HistoryLine\|\|26.2\|dev=snap1
	\| Added items [[Minecraft:sulfur]], [[Minecraft:potent sulfur]], [[Minecraft:sulfur slab]], [[Minecraft:sulfur stairs]], [[Minecraft:sulfur wall]], [[Minecraft:polished sulfur block]], [[Minecraft:polished sulfur slab]], [[Minecraft:polished sulfur stairs]], [[Minecraft:polished sulfur wall]], [[Minecraft:sulfur bricks]], [[Minecraft:sulfur brick slab]], [[Minecraft:sulfur brick stairs]], [[Minecraft:sulfur brick wall]], [[Minecraft:cinnabar]], [[Minecraft:cinnabar slab]], [[Minecraft:cinnabar stairs]], [[Minecraft:cinnabar wall]], [[Minecraft:polished cinnabar block]], [[Minecraft:polished cinnabar slab]], [[Minecraft:polished cinnabar stairs]], [[Minecraft:polished cinnabar wall]], [[Minecraft:cinnabar bricks]], [[Minecraft:cinnabar brick slab]], [[Minecraft:cinnabar brick stairs]] and [[Minecraft:cinnabar brick wall]] as new instances of {{jicp\|Block}}		\| Added items [[Minecraft:sulfur]], [[Minecraft:potent sulfur]], [[Minecraft:sulfur slab]], [[Minecraft:sulfur stairs]], [[Minecraft:sulfur wall]], [[Minecraft:polished sulfur block]], [[Minecraft:polished sulfur slab]], [[Minecraft:polished sulfur stairs]], [[Minecraft:polished sulfur wall]], [[Minecraft:sulfur bricks]], [[Minecraft:sulfur brick slab]], [[Minecraft:sulfur brick stairs]], [[Minecraft:sulfur brick wall]], [[Minecraft:cinnabar]], [[Minecraft:cinnabar slab]], [[Minecraft:cinnabar stairs]], [[Minecraft:cinnabar wall]], [[Minecraft:polished cinnabar block]], [[Minecraft:polished cinnabar slab]], [[Minecraft:polished cinnabar stairs]], [[Minecraft:polished cinnabar wall]], [[Minecraft:cinnabar bricks]], [[Minecraft:cinnabar brick slab]], [[Minecraft:cinnabar brick stairs]], and [[Minecraft:cinnabar brick wall]] as new instances of {{jicp\|Block}}
	\| Added the item [[Minecraft:sulfur cube bucket]] as a new {{jicp\|MobBucket}} instance, with content (fluid) and emptySound is empty.		\| Added the item [[Minecraft:sulfur cube bucket]] as a new {{jicp\|MobBucket}} instance, with content (fluid) and emptySound is empty.
	\| Added the item [[Minecraft:sulfur cube spawn egg]] as a new {{jicp\|SpawnEgg}} instance.		\| Added the item [[Minecraft:sulfur cube spawn egg]] as a new {{jicp\|SpawnEgg}} instance.
Line 3,839:		Line 3,838:
	}}		}}
	\|{{HistoryLine\|\|\|dev=snap7		\|{{HistoryLine\|\|\|dev=snap7
	\| Added the item music disc bounce, as just a instance of {{jicp\|}}.		\| Added the item [[Minecraft:music disc bounce]], as just a instance of {{jicp\|}}.
	}}		}}
	\|{{HistoryLine\|\|\|dev=pre1		\|{{HistoryLine\|\|\|dev=pre1
Line 3,847:		Line 3,846:
	26.2 end!		26.2 end!
	-->		-->
	\|{{HistoryLine\|\|26.3\|dev=?\|~~Shovels~~ are now just ~~Item~~.}}		\|{{HistoryLine\|\|26.3\|dev=snap1
	\|{{~~HistoryLine~~\|\|\|~~dev=?~~\|~~Axes are now just Item~~.}}		\|
	\|{{~~HistoryLine~~\|\|\|~~dev=?~~\|~~Hoes are now just Item~~.}}		\|Removed {{jicp\|Bed}}. [[Minecraft:Bed]] (all 16 blocks in ColorCollection) are now just {{jicp\|Block}}. Previously, when placing a bed block (using the {{cd\|placeBlock(...)}}), it used update flags of 26 instead of 11.<ref>{{bug\|MC-308830}}</ref>
	\|{{~~HistoryLine~~\|\|\|~~dev=?~~\|~~Something significant~~ has ~~changed about decorated~~ pot ~~patterns~~ and ~~pot decorations~~.}}		\|{{Jicp\|Instrument}} now, in the method {{cd\|use(...)}}, hurt and break the item according to the new tag {{nbt\|int\|durability_damage}} from the [[Minecraft:instrument definition]], if it exists and is greater than 0. Furthermore, only add the cooldown if it is greater than {{cd\|0.0}}.
	\|{{HistoryLine\|\|\|dev=?\|~~Beds~~ are now just ~~BlockItem~~.}}		\| {{jicp\|SpawnEgg}} when used ({{cd\|useOn(...)}}) by op players in [[Minecraft:monster spawner]] or [[Minecraft:trial spawner]], sets the data according to the {{DCL\|entity_data}} component; previously, only the entity id was set.
			\| Access to items in {{jcp\|net.minecraft.world.level.block.entity.DecoratedPotPatterns}} has been removed and replaced by the component {{DCL\|provides_pottery_pattern}}. Previously, the sides of the decorated pot were saved with item ids, and each id was associated with a texture.
			\| Access to items in {{jcp\|net.minecraft.world.level.block.entity.PotDecorations}} has been removed; the [[Minecraft:brick]] no longer has the property of being the default item for [[Minecraft:decorated pot]] sides, making it possible to decorate pots with an empty side.
			\| Added [[Minecraft:poplar planks]], [[Minecraft:poplar sapling]], [[Minecraft:poplar log]], [[Minecraft:stripped poplar log]], [[Minecraft:stripped poplar wood]], [[Minecraft:poplar wood]], [[Minecraft:Red Poplar Leaves\|red poplar leaves]], [[Minecraft:Orange Poplar Leaves\|orange poplar leaves]], [[Minecraft:Yellow Poplar Leaves\|yellow poplar leaves]], [[Minecraft:red shrub]], [[Minecraft:wool stairs]] (ColorCollection), [[Minecraft:wool slab]] (ColorCollection), [[Minecraft:shelf mushroom]], [[Minecraft:poplar slab]], [[Minecraft:poplar shelf]], [[Minecraft:poplar fence]], [[Minecraft:poplar stairs]], [[Minecraft:poplar button]], [[Minecraft:poplar pressure plate]], [[Minecraft:poplar door]], [[Minecraft:poplar trapdoor]], and [[Minecraft:poplar fence gate]] as new instances of {{jicp\|Block}}.
			\| Added [[Minecraft:poplar boat]] and [[Minecraft:poplar boat with chest]] as new instances of {{jicp\|Boat}}.
			\| Added [[Minecraft:poplar sign]] as new istance of {{jicp\|Sign}}.
			\| Added [[Minecraft:poplar hanging sign]] as new istance of {{jicp\|HangingSign}}.
			\| In {{jicp\|Axe}}, poplar wood and poplar log were added to {{cd\|STRIPPABLES}}
			\| Added potted poplar sapling, a new instance of {{jbcp\|FlowerPot}}. Thus, through the {{cd\|useItemOn(...)}} method in {{jbcp\|FlowerPot}}, which import the {{jicp\|Block}}, the poplar sapling has the hardcoded property of interacting with the [[Minecraft:flower pot]].
			\| The new poplar boat and poplar boat with chest items have the behavior {{cd\|BoatDispenseItemBehavior}} in {{jcp\|net.minecraft.core.dispenser.DispenseItemBehavior}}.
			}}
			<!--26.3 snap1 end -->
			\|{{HistoryLine\|\|\|dev=snap2
			\| {{jicp\|Axe}}, {{jicp\|Hoe}}, and {{jicp\|Shovel}} have been removed. All items previously belonging to these classes ([[Minecraft:axes]], [[Minecraft:hoes]], and [[Minecraft:shovels]]) are now just {{jicp\|}}, and their behavior, previously defined by their class properties, is now given by {{DCL\|block_transformer}}. In the case of the shovels, some properties now depend on the tag {{tag link\|item\|dowses_campfires}}.
			\| The method {{cd\|useOn(...)}}, in {{jicp\|}}, transforms blocks according to the component {{cd\|block_transformer}} or returns {{cd\|PASS}} if it does not exist. Previously it always returned {{cd\|PASS}}.
			\| {{jicp\|Honeycomb}} now play a sound in the {{cd\|useOn(...)}} and {{cd\|tryApplyToSign(...)}} methods.
			\| In {{jicp\|DispenseItemBehavior}}, the behavior of [[Minecraft:honeycomb]] now play a sound.
			}}
			<!--26.3 snap2 end -->
	\|{{HistoryLine\|\|\|dev=?\|Brewing is now data-driven using the recipe system, removing some hardcoded item data as a result.}}		\|{{HistoryLine\|\|\|dev=?\|Brewing is now data-driven using the recipe system, removing some hardcoded item data as a result.}}
	\|{{HistoryLine\|\|\|dev=?\|Added CushionItem.}}		\|{{HistoryLine\|\|\|dev=?\|Added CushionItem.}}
	\|{{HistoryLine\|\|\|dev=?\|~~Dappled forest biome blocks~~, ~~wool slabs and stairs, and~~ concrete slabs and stairs, now exist under block item definitions of some sort.}}		\|{{HistoryLine\|\|\|dev=?\|Straw bed, concrete slabs and stairs, now exist under block item definitions of some sort.}}
	\|{{HistoryLine\|\|\|dev=?\|Villager food is now component controlled.}}		\|{{HistoryLine\|\|\|dev=?\|Villager food is now component controlled.}}
	\|{{HistoryLine\|\|\|dev=?\|Exploration maps are now handled differently.}}		\|{{HistoryLine\|\|\|dev=?\|Exploration maps are now handled differently.}}

← Older revision		Revision as of 11:04, 11 September 2026
Line 7:		Line 7:

	<!--{{TOC\|right}}-->		<!--{{TOC\|right}}-->
	'''Hardcoded item properties''' are aspects of [[Minecraft:item]]s which are tied to the [[Minecraft:Identifier#Java Edition usage\|IDs]] and cannot be customized fully via the use of [[Minecraft:commands]] or [[Minecraft:data pack]]s. That is, if an item has all of its [[Minecraft:Data component format\|item components]] removed, and is not a member of any [[Minecraft:Item tag (Java Edition)\|item tags]], referenced by any [[Minecraft:~~Recipe_~~(~~Java_Edition~~)\|recipe]]s, [[Minecraft:Villager trade definition\|trade]]s, [[Minecraft:Advancement definition\|advancement triggers]], or [[Minecraft:predicate]]{{note\|Used for [[Minecraft:shears]] in [[Minecraft:loot table]]s.}}, or any other more esoteric data-driven definitions (e.g. [[Minecraft:vault]] unlock items), it still possesses a functionality based entirely on its item ID which cannot be removed from it, nor assigned to arbitrary other items.		'''Hardcoded item properties''' are aspects of [[Minecraft:item]]s which are tied to the [[Minecraft:Identifier#Java Edition usage\|IDs]] and cannot be customized fully via the use of [[Minecraft:commands]] or [[Minecraft:data pack]]s. That is, if an item has all of its [[Minecraft:Data component format\|item components]] removed, and is not a member of any [[Minecraft:Item tag (Java Edition)\|item tags]], referenced by any [[Minecraft:Recipe (Java Edition)\|recipe]]s, [[Minecraft:Villager trade definition\|trade]]s, [[Minecraft:Advancement definition\|advancement triggers]], or [[Minecraft:predicate]]{{note\|Used for [[Minecraft:shears]] in [[Minecraft:loot table]]s.}}, or any other more esoteric data-driven definitions (e.g. [[Minecraft:vault]] unlock items, what [[Minecraft:Enchantment definition\|enchantments]] can be applied to items), it still possesses a functionality based entirely on its item ID which cannot be removed from it, nor assigned to arbitrary other items.

	Many of the properties associated with items in the game have been made controllable with [[Minecraft:data component format]]; this intends to track things that are not currently controllable via ~~components,~~ item ~~tags, recipes, advancements, [[Minecraft:Enchantment_definition\|enchantments]] and trades~~ (though may be in future).		Many of the properties associated with items in the game have been made controllable with [[Minecraft:data component format]]; this intends to track things that are not currently controllable via any of the above data-driven item properties (though may be in future).

	Some properties are mixed, where they depend both on the hardcoded parts and on references to components, tags, etc. In these cases, items with the same components, tags, etc., would have different properties depending on the item's ID. For example, the properties of the [[Minecraft:spawn egg]], which depend on both the item's ID (being an instance of [[#SpawnEggItem\|SpawnEggItem]]) and the component {{DCL\|entity_data}}. These properties are also described on this page.		Some properties are mixed, where they depend both on the hardcoded parts and on references to components, tags, etc. In these cases, items with the same components, tags, etc., would have different properties depending on the item's ID. For example, the properties of the [[Minecraft:spawn egg]], which depend on both the item's ID (being an instance of [[#SpawnEggItem\|SpawnEggItem]]) and the component {{DCL\|entity_data}}. These properties are also described on this page.
Line 834:		Line 834:
	===getDefaultMaxStackSize()===		===getDefaultMaxStackSize()===
	-->		-->
	===onUseTick(...)===		=== onUseTick(...) ===

	{\| class="wikitable"		{\| class="wikitable"
	\|+ style="text-align: left \| onUseTick		\|+ style="text-align: left \| onUseTick
Line 857:		Line 856:
	{{blist		{{blist
	\|class=treeview		\|class=treeview
	\|{{jicp\|-Stack}}.{{cd\|onUseTick({{tooltip\|...\|Level level, LivingEntity livingEntity, int ticksRemaining}})}}: Calls the method implemented in the item stack as item, after properties relating to {{DCL\|consumable}} and {{DCL\|kinetic_waapon}} components.		\|{{jicp\|-Stack}}.{{cd\|onUseTick({{tooltip\|...\|Level level, LivingEntity livingEntity, int ticksRemaining}})}}: Calls the method implemented in the item stack as item, after properties relating to {{DCL\|consumable}} and {{DCL\|kinetic_waapon}}{{verify\|Is this a typo, or does the code actually say this?}} components.
	{{blist\|class=treeview\|		{{blist\|class=treeview\|
	{{jcp\|net.minecraft.world.entity.LivingEntity}}.{{cd\|updateUsingItem({{tooltip\|...\|ItemStack useItem}})}}: Called at the beginning, in the {{jcp\|net.minecraft.server.level.ServerPlayer}} implementation after activating [[Minecraft:Advancement_definition#minecraft:\using_item\|{{cd\|using_item}}]] tiger criteria.		{{jcp\|net.minecraft.world.entity.LivingEntity}}.{{cd\|updateUsingItem({{tooltip\|...\|ItemStack useItem}})}}: Called at the beginning, in the {{jcp\|net.minecraft.server.level.ServerPlayer}} implementation after activating [[Minecraft:Advancement_definition#minecraft:\using_item\|{{cd\|using_item}}]] tiger{{verify}} criteria.
	{{blist\|class=treeview\|		{{blist\|class=treeview\|
	{{jcp\|net.minecraft.world.entity.LivingEntity}}.{{cd\|updatingUsingItem()}}: Calls if the item stack used remains in the same hand of the entity.		{{jcp\|net.minecraft.world.entity.LivingEntity}}.{{cd\|updatingUsingItem()}}: Calls if the item stack used remains in the same hand of the entity.
Line 2,025:		Line 2,024:

	=== PlaceOnWaterBlockItem ===		=== PlaceOnWaterBlockItem ===
	{{~~empty~~ section}}		{{info needed section\|Presumably concerns lily pads and frogspawn, but what about spawn eggs and boats?}}

	=== PlayerHeadItem ===		=== PlayerHeadItem ===
	{{~~empty~~ section}}		{{info needed section\|Is this why {{bug\|MC-166998}}/{{bug\|MC-301817}} exist (aka heads using hardcoded rendering rather than either rendering an item model or equipment definition), or does that belong somewhere else?}}

	=== PotionItem ===		=== PotionItem ===

Line 3,703:		Line 3,704:

	== History ==		== History ==
	{{info needed section\|History before [[Minecraft:Java Edition 26.1 Snapshot 1]] and after [[Minecraft:Java Edition 26.2]] <!--Previously, properties were controlled by NBT tags, so it still made sense to divide them between hardcoded and non-hardcoded properties. Although it's unlikely anyone will write the history from that long ago, NBT tags generally dealt with customizable aspects in Survival mode, unlike many components. Furthermore, since 2017 there have been properties controlled by tags and recipes that control the properties of items.--@Aloi4 --> (e.g. removal of bed item and what it was replaced by/what changed, or how decorated pot handling was modified, and brewing migrated to recipes). also since at least three useon types are being removed in 26.3 those should be listed here}}		{{info needed section\|History before [[Minecraft:Java Edition 26.1 Snapshot 1]] and after [[Minecraft:Java Edition 26.2]] <!--Previously, properties were controlled by NBT tags, so it still made sense to divide them between hardcoded and non-hardcoded properties. Although it's unlikely anyone will write the history from that long ago, NBT tags generally dealt with customizable aspects in Survival mode, unlike many components. Furthermore, since 2017 there have been properties controlled by tags and recipes that control the properties of items.--@Aloi4 -->}}

	{{HistoryTable		{{HistoryTable
	\|{{HistoryLine\|~~Java~~}}		\|{{HistoryLine\|java}}
	\|{{HistoryLine\|\|1.13\|dev=17w43a\|Add [[Minecraft:datapack]] that control [[Minecraft:Advancement_definition\|advancement]]. Items used in advancement triggers are no longer hardcoded, such as iron bars, stone pickaxes, and lava buckets.}}		\|{{HistoryLine\|\|1.13\|dev=17w43a\|Add [[Minecraft:datapack]] that control [[Minecraft:Advancement_definition\|advancement]]. Items used in advancement triggers are no longer hardcoded, such as iron bars, stone pickaxes, and lava buckets.}}
	\|{{HistoryLine\|\|\|dev=17w48a\|[[Minecraft:Recipe (Java Edition)\|Recipes]] are now controlled by datapacks, so most recipes are no longer hardcoded, with the exception of special crafting recipes}}		\|{{HistoryLine\|\|\|dev=17w48a\|[[Minecraft:Recipe (Java Edition)\|Recipes]] are now controlled by datapacks, so most recipes are no longer hardcoded, with the exception of special crafting recipes}}
	\|{{HistoryLine\|\|\|dev=17w49a\|Added [[Minecraft:Tag (Java Edition)\|tag]]s, with the item tags {{tag link\|item\|planks\|wool}}. So, the properties of planks, repair tools, shields, and wool to be used with fuel were no longer hardcoded.}}		\|{{HistoryLine\|\|\|dev=17w49a\|Added [[Minecraft:Tag (Java Edition)\|tag]]s, with the item tags {{tag link\|item\|planks\|wool}}. So, the properties of planks, repair tools, shields, and wool to be used with fuel were no longer hardcoded.}}
	\|{{HistoryLine\|\|1.14\|dev=18w43a\|Added {{cd\|match_tool}} loot table condition, Now, the drop rate for using [[Minecraft:shears]] is controlled by [[Minecraft:loot tables]].{{Info needed\|The loot table already existed previously, so how was the drop rate controlled?}}}}		\|{{HistoryLine\|\|1.14\|dev=18w43a\|Added {{cd\|match_tool}} loot table condition, Now, the drop rate for using [[Minecraft:shears]] is controlled by [[Minecraft:loot tables]].{{Info needed\|The loot table already existed previously, so how was the drop rate controlled?}}}}
	\|{{HistoryLine\|\|1.20.5\|dev=24w09a\|Item NBT has been effectively removed, being replaced by the new [[Minecraft:data component format]]. Some hardcoded properties of items have also been migrated to this system.{{info needed\|which? ~~I know enchantment_glint_override was one of them, but~~ surely there were others?}}}}		\|{{HistoryLine\|\|1.20.5\|dev=24w09a\|Item NBT has been effectively removed, being replaced by the new [[Minecraft:data component format]]. Some hardcoded properties of items have also been migrated to this system.{{info needed\|which? surely there were others besides those mentioned below?}}}}
			\|{{HistoryLine\|\|\|dev=?\|The enchantment glint override component has been added, which presumably supplanted some unspecified hardcoded behaviour.}}
			\|{{HistoryLine\|\|\|dev=?\|Food data is now a component, presumably replacing hardcoded data definitions.}}
			\|{{HistoryLine\|\|\|dev=?\|Maximum item stack size is now a component, presumably replacing hardcoded data definitions.}}
			\|{{HistoryLine\|\|\|dev=?\|The maximum amount of damage an item can withstand is now a component, presumably replacing hardcoded data definitions.}}
			\|{{HistoryLine\|\|\|dev=?\|Whether items are destroyed by fire and lava or not is now a component, presumably replacing hardcoded data definitions.}}
			\|{{HistoryLine\|\|\|dev=?\|Rarity is now controlled by a component, presumably replacing hardcoded data definitions.}}
			\|{{HistoryLine\|\|\|dev=?\|Tool data is now a component, presumably replacing hardcoded data definitions.}}
			\|{{HistoryLine\|\|\|dev=?\|Whether tooltips are visible is now controlled by a component, presumably replacing hardcoded data definitions.}}
			\|{{HistoryLine\|\|\|dev=?\|Item names can now be controlled by a component, presumably replacing hardcoded data definitions.}}
	\|{{HistoryLine\|\|1.21\|dev=24w18a\|[[Minecraft:Enchantment definition\|Enchantment]]s are now controlled by datapacks, so the property of being enchanted by a certain enchantment has ceased to be hardcoded, except for [[Minecraft:book]].}}		\|{{HistoryLine\|\|1.21\|dev=24w18a\|[[Minecraft:Enchantment definition\|Enchantment]]s are now controlled by datapacks, so the property of being enchanted by a certain enchantment has ceased to be hardcoded, except for [[Minecraft:book]].}}
			\|{{HistoryLine\|\|\|dev=?\|Output items from eating food is now controlled by a component, presumably replacing hardcoded data definitions.}}
			\|{{HistoryLine\|\|\|dev=?\|Jukebox item usage is now a component, presumably replacing hardcoded data definitions.}}
	<!--		<!--
	26.1 Start		26.1 Start
Line 3,835:		Line 3,847:
	26.2 end!		26.2 end!
	-->		-->
			\|{{HistoryLine\|\|26.3\|dev=?\|Shovels are now just Item.}}
			\|{{HistoryLine\|\|\|dev=?\|Axes are now just Item.}}
			\|{{HistoryLine\|\|\|dev=?\|Hoes are now just Item.}}
			\|{{HistoryLine\|\|\|dev=?\|Something significant has changed about decorated pot patterns and pot decorations.}}
			\|{{HistoryLine\|\|\|dev=?\|Beds are now just BlockItem.}}
			\|{{HistoryLine\|\|\|dev=?\|Brewing is now data-driven using the recipe system, removing some hardcoded item data as a result.}}
			\|{{HistoryLine\|\|\|dev=?\|Added CushionItem.}}
			\|{{HistoryLine\|\|\|dev=?\|Dappled forest biome blocks, wool slabs and stairs, and concrete slabs and stairs, now exist under block item definitions of some sort.}}
			\|{{HistoryLine\|\|\|dev=?\|Villager food is now component controlled.}}
			\|{{HistoryLine\|\|\|dev=?\|Exploration maps are now handled differently.}}
	}}		}}