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

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.}}
	}}		}}

SyncBot: Sync: updated from Minecraft

2026-09-10T11:04:54Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:04, 10 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.		'''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.

			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).

			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.
			<!--There is also a very particular case of "circular properties," where an item has a property but without mods there's no way to test it because there's no way to add another item to test the property. Example: ComposterBlock.OutputContainer -->

	Many of the properties associated with items in the game have been made controllable with the newly-introduced [[Minecraft:data component format]]; this intends to track things that are not currently controllable via components, [[Minecraft:Item_tag_(Java_Edition)\|item tags]], [[Minecraft:recipe#ava_Edition_JSON_format\|recipes]], [[Minecraft:Advancement_definition\|advancements]], [[Minecraft:Enchantment_definition\|enchantments]] and [[Minecraft:Villager_trade_definition\|trades]] (though may be in future).
	{{TOC\|none\|limit=2}}		{{TOC\|none\|limit=2}}

Line 132:		Line 136:
	All craft remainder can also be used in custom [[Minecraft:recipe]]s via [[Minecraft:data pack]]s. In code is also used in the craft display item, however it apparently hasn't been implemented in the game{{info needed}}.		All craft remainder can also be used in custom [[Minecraft:recipe]]s via [[Minecraft:data pack]]s. In code is also used in the craft display item, however it apparently hasn't been implemented in the game{{info needed}}.

	Adding some tags, such as {{tag link\|item\|wooden_trapdoors}}, to one of the items above allows it to be used as fuel while also having a crafting remainder. In the book and banner cloning recipe, the cloned item remains if it doesn't have a craft remainder{{note\|If the material in the book cloning recipe has the component {{DCL\|written_book_content}}, it will also remains.}}; if it does have a crafting remainder, the crafting remainder takes priority~~. Therefore, when placing one of the above items with a {{cd\|source}} in the book cloning recipe, instead of keeping the item, it will keep its crafting remainder~~.		Adding some tags, such as {{tag link\|item\|wooden_trapdoors}}{{Until\|Java 26.3}}, or add the component {{DCL\|cooking_fuel}}{{Upcoming\|Java 26.3}} to one of the items above allows it to be used as fuel while also having a crafting remainder. In the book and banner cloning recipe, the cloned item ({{cd\|banner}} and {{cd\|source}}) remains if it doesn't have a craft remainder{{note\|If the {{cd\|material}} in the book cloning recipe has the component {{DCL\|written_book_content}}, it will also remains.}}; if it does have a crafting remainder, the crafting remainder takes priority.

	Another exception is the item {{cd\|descriptionId}}, which can be {{cd\|''minecraft.item.<id>''}} or {{cd\|''minecraft.block.<id>''}}. Although its primary use is for the item name, the {{DCL\|item_name}} default component, this description id is also used for other things such as potion names and disc fragment descriptions.		Another exception is the item {{cd\|descriptionId}}, which can be {{cd\|''minecraft.item.<id>''}} or {{cd\|''minecraft.block.<id>''}}. Although its primary use is for the item name, the {{DCL\|item_name}} default component, this description id is also used for other things such as potion names and disc fragment descriptions.

SyncBot: Sync: updated from Minecraft

2026-09-07T11:08:11Z

Sync: updated from Minecraft

← Older revision		Revision as of 11:08, 7 September 2026
Line 959:		Line 959:
	Until [[Minecraft:Java Edition 26.3]], it only returns the interaction result {{cd\|PASS}}. However, in implementations, in addition to the [[Minecraft:w:Side_effect_(computer_science)\|side effect]]s (the core of the method), it can return interaction results such as {{cd\|FAIL}} and {{cd\|SUCCESS}}. These returns can have some subsequent effect as shown in the tree below.		Until [[Minecraft:Java Edition 26.3]], it only returns the interaction result {{cd\|PASS}}. However, in implementations, in addition to the [[Minecraft:w:Side_effect_(computer_science)\|side effect]]s (the core of the method), it can return interaction results such as {{cd\|FAIL}} and {{cd\|SUCCESS}}. These returns can have some subsequent effect as shown in the tree below.

	Upcoming [[Minecraft:Java Edition 26.3]], if the {{DCL\|block_transformer}} data default of the item in hand is not empty, it attempts to transform the interacted block, with the return value depending on the transformation; otherwise, it returns FAIL. However, default {{Cd\|block_transformer}} data components exist only for [[Minecraft:hoe]]s, [[Minecraft:shovel]]s, and [[Minecraft:axe]]s; many items still rely on hardcoded usage logic (see the implementations below).		Upcoming [[Minecraft:Java Edition 26.3]], if the {{DCL\|block_transformer}} data default of the item in hand is not empty, it attempts to transform the interacted block, with the return value depending on the transformation; otherwise, it returns {{Cd\|FAIL}}. However, default {{Cd\|block_transformer}} data components exist only for [[Minecraft:hoe]]s, [[Minecraft:shovel]]s, and [[Minecraft:axe]]s; many items still rely on hardcoded usage logic (see the implementations below).

	'''Uses tree'''		'''Uses tree'''
Line 981:		Line 981:

	* {{jicp\|-Stack}}.{{cd\|useOn(...)}}: If the player is in [[Minecraft:adventure mode]] and the item stack does not have the {{DCL\|can_place_on}} component corresponding to the clicked block, it returns fail.		* {{jicp\|-Stack}}.{{cd\|useOn(...)}}: If the player is in [[Minecraft:adventure mode]] and the item stack does not have the {{DCL\|can_place_on}} component corresponding to the clicked block, it returns fail.
	: Otherwise, call the method implemented in the item stack as item. If the method returns {{cd\|SUCCESS}} increases the item {{cd\|used}} [[Minecraft:statistic]] by one. Returns the return value of the called method.		: Otherwise, call the method implemented in the item stack as item. If the method returns {{cd\|SUCCESS}} increases the item {{cd\|used}} [[Minecraft:statistic]] by one. Returns the return value of the called method.{{More info\|Changes to the return on 26.3}} <!--
	* {{jcp\|net.minecraft.server.level.ServerPlayerGameMode}}.{{cd\|useItemOn(...)}}: Returns falls if the block being hit is exclusive of a unenabled [[Minecraft:experiment]]. The current version ~~[[Minecraft:1.21.11]]~~ does not have such blocks in the game.		ItemStack transformTo = success.heldItemTransformedTo() == null ? this : success.heldItemTransformedTo();
	: If the player is in the [[Minecraft:spectator]] mode: if the block has a menu, open the menu and return {{cd\|CONSUME}}, ~~otherwise~~ return {{cd\|PASS}}.
			ItemStack resultItemStack = transformTo.applyAfterUseComponentSideEffects(player, stackBeforeUse);

			return success.heldItemTransformedTo(resultItemStack);
			-->
			* {{jcp\|net.minecraft.server.level.ServerPlayerGameMode}}.{{cd\|useItemOn(...)}}: Returns falls if the block being hit is exclusive of a unenabled [[Minecraft:experiment]]. The current version does not have such blocks in the game.
			: If the player is in the [[Minecraft:spectator]] mode:
			:* If the block has a [[Minecraft:Interactable_blocks#Blocks_with_GUI\|menu]], open the menu and return {{cd\|CONSUME}}
			:* If the block is a portal ([[Minecraft:End Gateway (block)\|end gateway]], [[Minecraft:End Portal (block)\|end portal]], or [[Minecraft:Nether Portal (block)\|nether portal]]), attempt to teleport the player to the destination. If possible, remove the camera view of another entity beforehand. If not possible, display the message {{cd\|spectator.cannot_teleport}} in red on [[Minecraft:action bar]]. Return {{cd\|CONSUME}}. {{Upcoming\|Java 26.3}}
			:* Otherwise return {{cd\|PASS}}.
	: If the player is not [[Minecraft:sneaking]] or doesn't have items in either hand:		: If the player is not [[Minecraft:sneaking]] or doesn't have items in either hand:
	:* The player will attempt to use the item, or the empty hand, on the block. However, for this use, the previous method will not be used, but rather {{cd\|state.useItemOn(...)}}, which is a method controlled by the block ({{cd\|{{tooltip\|state\|BlockPos pos {{=}} hitResult.getBlockPos(); BlockState state {{=}} level.getBlockState(pos)}}}}). Sometimes this method will give different results depending on the item used; see {{sl\|\|Items member access}} for details.		:* The player will attempt to use the item, or the empty hand, on the block. However, for this use, the previous method will not be used, but rather {{cd\|state.useItemOn(...)}}, which is a method controlled by the block ({{cd\|{{tooltip\|state\|BlockPos pos {{=}} hitResult.getBlockPos(); BlockState state {{=}} level.getBlockState(pos)}}}}). Sometimes this method will give different results depending on the item used; see {{sl\|\|Items member access}} for details.
Line 991:		Line 1,000:
	:* If neither {{cd\|state.useItemOn(...)}} nor {{cd\|state.useWithoutItem(...)}} returns success, the method continues.		:* If neither {{cd\|state.useItemOn(...)}} nor {{cd\|state.useWithoutItem(...)}} returns success, the method continues.
	: If the item stack is empty or in [[Minecraft:use cooldown\|cooldown]], return {{cd\|PASS}}.		: If the item stack is empty or in [[Minecraft:use cooldown\|cooldown]], return {{cd\|PASS}}.
	: Finally, the {{cd\|ItemStack.useOn(...)}} method is called. If the player is in creative mode, the stack item quantity is restored, preventing any loss due to the called method. If the return is successful, the {{cd\|item_used_on_block}} is activated. Returns the return of the called method.		: Finally, the {{cd\|ItemStack.useOn(...)}} method is called. If the player is in creative mode, the stack item quantity is restored, preventing any loss due to the called method.{{More info\|In 26.3, at this point, the player can switch the item in their hand depending on the result.}} If the return is successful, the {{cd\|item_used_on_block}} is activated. Returns the return of the called method.
	: In {{jcp\|net.minecraft.server.level.DemoMode}}, output demo reminder and return {{cd\|PASS}}, if [[Minecraft:Demo Mode\|demo timer]] has end. Otherwise, it calls the supermethod, so the method will proceed normally.		: In {{jcp\|net.minecraft.server.level.DemoMode}}, output demo reminder and return {{cd\|PASS}}, if [[Minecraft:Demo Mode\|demo timer]] has end. Otherwise, it calls the supermethod, so the method will proceed normally.
	* {{jcp\|net.minecraft.server.level.ServerGamePacketListenerImpl}}.{{cd\|handleUseItemOn}}: Initially, it tests if the interaction is allowed, if positive, call the method. If the return of the called method is successful, the [[Minecraft:Advancement_definition#minecraft:any_block_use\|{{cd\|any_block_use}}]] is activated.		* {{jcp\|net.minecraft.server.level.ServerGamePacketListenerImpl}}.{{cd\|handleUseItemOn}}: Initially, it tests if the interaction is allowed, if positive, call the method. If the return of the called method is successful, the [[Minecraft:Advancement_definition#minecraft:any_block_use\|{{cd\|any_block_use}}]] is activated.
	: If the interaction is unsuccessful, the interaction direction is up, the interacted block is at its maximum height, and the item is a {{slink\|\|BlockItem}} or {{slink\|\|BucketItem}} instance with non-empty fluid and is not on cooldown, then send the system error message in [[Minecraft:action bar]] with the translation of {{cd\|build.tooHigh}} with the maximum height value of the dimension.		: If the interaction is unsuccessful, the interaction direction is up, the interacted block is at its maximum height, and the item is a {{slink\|\|BlockItem}} or {{slink\|\|BucketItem}} instance with non-empty fluid and is not on cooldown, then send the system error message in [[Minecraft:action bar]] with the translation of {{cd\|build.tooHigh}} with the maximum height value of the dimension.
	: If the return of the called method is {{cd\|SUCCESS}} or {{cd\|SUCCESS_SERVER}}, the player swings the hand used.		: If the return of the called method is {{cd\|SUCCESS}} or {{cd\|SUCCESS_SERVER}}, the player swings the hand used.
			: {{More info\|Message from the minimum Y value and hand movement type.}}
	<!--		<!--
	checking if the item is enabled (just like blocks, in the current version 1.21.11, all are), if the block is within the interaction range, and if the center of the block is less than 1.0000001 away from the interacted point on all axes. If any test fails, the method returns. In {{jcp\|net.minecraft.server.level.DemoMode}} test if has ended-->		checking if the item is enabled (just like blocks, in the current version 1.21.11, all are), if the block is within the interaction range, and if the center of the block is less than 1.0000001 away from the interacted point on all axes. If any test fails, the method returns. In {{jcp\|net.minecraft.server.level.DemoMode}} test if has ended-->

SyncBot: Sync: updated from Minecraft

2026-09-04T11:05:55Z

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.}}
	}}		}}

← 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.}}
	}}		}}

← Older revision		Revision as of 11:04, 10 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.		'''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.

			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).

			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.
			<!--There is also a very particular case of "circular properties," where an item has a property but without mods there's no way to test it because there's no way to add another item to test the property. Example: ComposterBlock.OutputContainer -->

	Many of the properties associated with items in the game have been made controllable with the newly-introduced [[Minecraft:data component format]]; this intends to track things that are not currently controllable via components, [[Minecraft:Item_tag_(Java_Edition)\|item tags]], [[Minecraft:recipe#ava_Edition_JSON_format\|recipes]], [[Minecraft:Advancement_definition\|advancements]], [[Minecraft:Enchantment_definition\|enchantments]] and [[Minecraft:Villager_trade_definition\|trades]] (though may be in future).
	{{TOC\|none\|limit=2}}		{{TOC\|none\|limit=2}}

Line 132:		Line 136:
	All craft remainder can also be used in custom [[Minecraft:recipe]]s via [[Minecraft:data pack]]s. In code is also used in the craft display item, however it apparently hasn't been implemented in the game{{info needed}}.		All craft remainder can also be used in custom [[Minecraft:recipe]]s via [[Minecraft:data pack]]s. In code is also used in the craft display item, however it apparently hasn't been implemented in the game{{info needed}}.

	Adding some tags, such as {{tag link\|item\|wooden_trapdoors}}, to one of the items above allows it to be used as fuel while also having a crafting remainder. In the book and banner cloning recipe, the cloned item remains if it doesn't have a craft remainder{{note\|If the material in the book cloning recipe has the component {{DCL\|written_book_content}}, it will also remains.}}; if it does have a crafting remainder, the crafting remainder takes priority~~. Therefore, when placing one of the above items with a {{cd\|source}} in the book cloning recipe, instead of keeping the item, it will keep its crafting remainder~~.		Adding some tags, such as {{tag link\|item\|wooden_trapdoors}}{{Until\|Java 26.3}}, or add the component {{DCL\|cooking_fuel}}{{Upcoming\|Java 26.3}} to one of the items above allows it to be used as fuel while also having a crafting remainder. In the book and banner cloning recipe, the cloned item ({{cd\|banner}} and {{cd\|source}}) remains if it doesn't have a craft remainder{{note\|If the {{cd\|material}} in the book cloning recipe has the component {{DCL\|written_book_content}}, it will also remains.}}; if it does have a crafting remainder, the crafting remainder takes priority.

	Another exception is the item {{cd\|descriptionId}}, which can be {{cd\|''minecraft.item.<id>''}} or {{cd\|''minecraft.block.<id>''}}. Although its primary use is for the item name, the {{DCL\|item_name}} default component, this description id is also used for other things such as potion names and disc fragment descriptions.		Another exception is the item {{cd\|descriptionId}}, which can be {{cd\|''minecraft.item.<id>''}} or {{cd\|''minecraft.block.<id>''}}. Although its primary use is for the item name, the {{DCL\|item_name}} default component, this description id is also used for other things such as potion names and disc fragment descriptions.

← Older revision		Revision as of 11:05, 4 September 2026
Line 2,668:		Line 2,668:
	Check if the item is a bucket. Used twice to determine the behavior of the fuel slot (the lower left slot in blocks [[Minecraft:furnace]], [[Minecraft:smoker]], and [[Minecraft:blast furnace]]):		Check if the item is a bucket. Used twice to determine the behavior of the fuel slot (the lower left slot in blocks [[Minecraft:furnace]], [[Minecraft:smoker]], and [[Minecraft:blast furnace]]):

	* In {{cd\|mayPlace(...)}}, to allow the bucket to be used in the fuel slot, even if it is not [[Minecraft:fuel]] (it is possible for it to be if it is added to a certain tag).		* In {{cd\|mayPlace(...)}}, to allow the bucket to be used in the fuel slot, even if it is not [[Minecraft:fuel]] (it is possible for it to be if it is added to a certain tag{{Until\|Java 26.3}}/added the data component {{DCL\|cooking_fuel}}{{Upcoming\|Java 26.3}}).
	** This does not change the quick move. Because what is tested to determine if an item can have a quick move to the fuel slot is whether it is a fuel.		** This does not change the quick move. Because what is tested to determine if an item can have a quick move to the fuel slot is whether it is a fuel.
	* In {{cd\|getMaxStackSize(...)}}, to limit the maximum number of buckets in the fuel slot to one.		* In {{cd\|getMaxStackSize(...)}}, to limit the maximum number of buckets in the fuel slot to one.

	{{-}}		{{-}}

	=== GrindstoneMenu ===		=== GrindstoneMenu ===
	{{Infobox hip\|class=GrindstoneMenu\|Enchanted Book\|pac=world.inventory}}		{{Infobox hip\|class=GrindstoneMenu\|Enchanted Book\|pac=world.inventory}}
Line 3,040:		Line 3,041:
	{{-}}		{{-}}
	===AbstractFurnaceBlockEntity===		===AbstractFurnaceBlockEntity===
	{{Infobox hip\|class=AbstractFurnaceBlockEntity\|Wet Sponge\|Bucket\|Water Bucket\|Inv=t\|pac=world.level.block.entity}}		{{Infobox hip\|class=AbstractFurnaceBlockEntity\|Wet Sponge\|Bucket\|Items=<Br>{{ItemLink\|Water Bucket}}{{Until\|Java 26.3}}\|Inv=t\|pac=world.level.block.entity}}

	Define the behavior of [[Minecraft:block entity]] associated with a [[Minecraft:furnace]], [[Minecraft:blast furnace]] and [[Minecraft:smoker]].		Define the behavior of [[Minecraft:block entity]] associated with a [[Minecraft:furnace]], [[Minecraft:blast furnace]] and [[Minecraft:smoker]].
Line 3,052:		Line 3,053:
	After that, shrink 1 item from ingredient slot.		After that, shrink 1 item from ingredient slot.

	{{ItemSprite\|Bucket}} {{ItemSprite\|Water Bucket}} '''canTakeItemThroughFace({{tooltip\|...\|int slot, ItemStack itemStack, Direction direction}})'''		{{ItemSprite\|Bucket}} {{ItemSprite\|Water Bucket}} '''canTakeItemThroughFace({{tooltip\|...\|int slot, ItemStack itemStack, Direction direction}})'''{{Until\|Java 26.3}}<!--Pre-1 use the tag #furnace_fuel_bottom_takeable-->

	Tests whether the container item can be take by a [[Minecraft:hopper]] or [[Minecraft:minecart with hopper]].		Tests whether the container item can be take by a [[Minecraft:hopper]] or [[Minecraft:minecart with hopper]].
	Returns true only if the face is the down. If it's the fuel slot (slot 1), the item must also be a bucket or a bucket ~~of water~~.		Returns true only if the face is the down. If it's the fuel slot (slot 1), the item must also be a bucket or a water bucket.

	Note: the down face only gives access to fuel and output slots (slots 1 and 2), so only items from the slots can be take.		Note: the down face only gives access to fuel and output slots (slots 1 and 2), so only items from the slots can be take.
Line 3,065:		Line 3,066:
	It always returns true for ingredient slot (slot 0) and always returns false for output slots (slot 2).		It always returns true for ingredient slot (slot 0) and always returns false for output slots (slot 2).

	For fuel slot (slot 1), it returns true if the item is fuel (see {{slink\|\|FuelValues}}) or if the item is a bucket but there is no bucket already in the slot.		For fuel slot (slot 1), it returns true if the item is fuel (see {{slink\|\|FuelValues}}{{Until\|Java 26.3}}/has a data component {{DCL\|cooking_fuel}}{{Upcoming\|Java 26.3}}) or if the item is a bucket but there is no bucket already in the slot.

	Note: the up face only gives access to ingredient slot (slot 0), and the side faces only give access to fuel slot (slot 1).		Note: the up face only gives access to ingredient slot (slot 0), and the side faces only give access to fuel slot (slot 1).
	{{-}}		{{-}}

	===BrewingStandBlockEntity===		===BrewingStandBlockEntity===
	{{Infobox hip\|class=BrewingStandBlockEntity\|Items=<BR>Until [[Minecraft:Java 26.3\|JE 26.3]]: {{Flatlist\|*{{ItemLink\|Potion}}		{{Infobox hip\|class=BrewingStandBlockEntity\|Items=<BR>Until [[Minecraft:Java 26.3\|JE 26.3]]: {{Flatlist\|*{{ItemLink\|Potion}}