Minecraft:Hardcoded item properties (Java Edition)

Template:Italic title Template:Exclusive Template:Wip Template:Project Template:Cleanup Hardcoded item properties are aspects of Minecraft:items which are tied to the IDs and cannot be customized fully via the use of Minecraft:commands or Minecraft:data packs. That is, if an item has all of its item components removed, and is not a member of any item tags, referenced by any recipes, trades, advancement triggers, or any other more esoteric data-driven definitions (e.g. Minecraft:vault unlock items, Minecraft:predicates used in Minecraft:loot tablesTemplate:Note or what 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).

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) and the component Template:DCL. These properties are also described on this page.

Item stacks properties

Most item instances in the game are through item stacks. An item stack is defined by its id, count and components.

Count

The count of an item is the easiest to control, and can largely be controlled even in Survival mode. Changing commands and components gives you more freedom to control it, although items with a count higher than their Template:DCL have some side effects and it is not possible, even with commands, to exceed a count of 99 or be less than 1.

However, the count is rarely used to affect the property of an item stack. Exceptions include the weight of the item in a bundle to test if it is full, the weight of the item in a container to be used by comparators, and using the item in trades. It is possible to control the quantity of items needed for a trade by commands and datapacks, the weight of the item in container is partially controlled by Template:Cd, and in bundles, in addition to being partially controlled by Template:Cd, it is also by Template:DCL and by Template:DCL. Furthermore, most uses of item stacks that do not depend on their count cannot be controlled to have to need it.

Components

Some components are partially controlled by changes made to the item in Survival mode. All components are strongly controlled by commands, although not entirely, as valid data is still required.

It is also possible to control the components of future item instances via datapacks, such as controlling the components of items in a Minecraft:loot table, the components of the result of many Minecraft:recipes (but not all, especially when the recipe result depends on the ingredient components), the components of the gives in villager Minecraft:trade, or the components of items that are in structures but are not part of a loot table (such as some chests in secret rooms of the Minecraft:woodland mansion).

However, there are origins of items that are not controlled by datapacks or commands, thus making it impossible to control the initial components of these items without Minecraft:mods (although it is possible to test when these items are originated and change their components later using datapacks).

Changes to an item's stack properties, depending on whether or not a certain component has it, can vary considerably. In some cases, the component affects all items that possess it and is highly customizable. In other cases, the component only affects stack items with certain IDs, or the component doesn't have much customizable data. Furthermore, some components affect more than one item property, making it impossible to activate only some of them.

Sometimes, properties that can be controlled by components have a lower priority than properties that depend on the item's ID, to the point that being used on certain items partially or completely loses its effect.

Template:Anchor Default components

Default components are components that are defined for each item ID. If an item stack does not have a component defined in the component field, but has it as its default component, it will consider the value of its default component. If it has the component in the component field, it will consider the value of the component field.

With commands and datapacks, this control only extends to additional components, not default components. Default components depend solely on the item's ID and cannot be customized.

It is possible to remove a component of an item stack with Template:Cd. However, this will modify the item's data, adding a new component that serves to remove the previous one. This can impact, for example, comparisons of item data via commands, or picking up a block with a mouse click (since the block is only selected from your inventory if it doesn't have additional components).

Furthermore, some aspects of the items depend on their default component. For example, knowing which spawn egg will be picked up when clicking on an entity, or the villager controlling the number of items in the inventory to know whether to drop it.

Id

Often, an item's stack property depends on its ID. Sometimes it depends only on its ID, and other times it depends on both its ID and its components or count. The main objective of this article is to describe the item properties that depend on their ID; however, not all will be covered, as some item properties that depend on their ID are actually controlled by data packs and not hardcoded.

Note that all these properties, being controlled by ID and not by component, cannot be made so that only some item stacks possess them, because when adding an ID, all item stacks with the same ID will share it. Thus, customizing properties by component instead of ID is more powerful. Due to this and the impossibility of registering new IDs, it is possible that data pack projects will not be viable because they do not have enough items to define properties with different IDs.

Item tags

Many of an item's properties depend exclusively on it belonging to a certain item tag. Sometimes an item tag is used to describe a property that can also be changed at another time; for example, using a tag in a vanilla datapack file would allow you to directly use the item IDs there. However, there are item properties that can only be manipulated without mods by adding them to a tag. See item tag.

Recipes

Recipes can control the properties of items to be used in the manufacture of others. Although largely customizable, there are still some limitations, especially when considering the components of the ingredients for the final result. See Minecraft:recipes.

Enchantment definition

When defining an enchantment, it is necessary to define the items in Template:Cd and Template:Cd to specify which items can be crafted at the anvil and the enchanting table, respectively. See Minecraft:enchantment definition.

Mixed properties

Some properties may depend on the item's id, component, and count. Below is a list of these properties that can be controlled by data packs or commands.

Trade

Trade can be controlled either by commands (with Template:Cmd, editing villager data) or by Minecraft:villager trade definition. With them, you define the properties of an item stack, which can be trade for another by the villagers.

Item predicate

The item predicate is a sub-predicate of Minecraft:predicates. Predicates can be used to test if a certain item satisfies a certain condition, and if so, contribute to the activation a certain Minecraft:loot table or Minecraft:advancement trigger. Loot tables are used to obtain items at various times. Advancement triggers, in addition to being used to receive advancements, are also used to unlock recipes.

Predicates are even more important for customizations, being used in commands or in advancement triggers to activate functions. Some commands like Template:Cmd are also very important in testing items and have an effect. Although we can use such commands to simulate a hardcoded item property or inhibit properties of certain items, this will hardly be done in a completely similar way, and the hardcoded properties will continue to exist, only being inhibited or copied.

Code structure

There are at least three ways in which the game code describes the properties of an item associated with its ID.

Item.Properties

In class Template:Jicp, 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 data components

A complete list of default components in Template:V can be seen at Template:V-diff/items misode/mcmeta. The list for Template:V can be found here. Template:Collapse

Used item	Component	Used in
Template:ItemLink	Template:DCL	Template:ItemLink
Template:ItemLink	Template:DCL	Template:ItemLink
Template:ItemLink	Template:DCL	Template:ItemLink
Template:ItemLink	Template:DCL	Template:ItemLink
Template:ItemLink	Template:DCL	Template:ItemLink
Template:ItemLink	Template:DCL	Template:ItemLink
Template:ItemLink	Template:DCL	Template:ItemLink
Template:ItemLink	Template:DCL	Template:ItemLink
Template:ItemLink	Template:DCL	Template:ItemLink
Template:ItemLink	Template:DCL (all faces)	Template:InvLink

A notable exception is the Template:Cd property, which defines which item will remain in a recipe when using the item as a recipe. See below for a list of all craft reminders:

All craft remainder can also be used in custom Minecraft:recipes via Minecraft:data packs. In code is also used in the craft display item, however it apparently hasn't been implemented in the gameTemplate:Info needed.

Adding the component Template:DCL 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 (Template:Cd and Template:Cd) remains if it doesn't have a craft remainderTemplate:Note; if it does have a crafting remainder, the crafting remainder takes priority.

Another exception is the item Template:Cd, which can be Template:Cd or Template:Cd. Although its primary use is for the item name, the Template:DCL default component, this description id is also used for other things such as potion names and disc fragment descriptions.

The last exception is the Template:Cd property, although it's not important in the current version. It serves to list which Minecraft:experiments must be active to use a certain item in many cases. Currently, no item is exclusive to any experiment; thus, all have this property with its default value Template:Cd.

Most of the Template:Cd applied to items are applied from the item's registered in Template:Jicp.

Item subclasses (code structure)

In the Template:Jcp package, there are many classes that define properties for a certain item or a certain set of items; these classes extend the Template:Jicp class. A large part of the hardcoded item properties come from here.

These classes have Template:Cd as their name, such as Template:Cd, Template:Cd, and Template:Cd.

In many cases, when an item is registered in Template:Jicp, it is already created as a new instance of one of these classes.

Some of them are abstract classes, not having any item that is restricted as a new instance of that class; however, these classes are extended by other classes, and so on until reaching a class that is at least one item, which is then restricted as a new instance of the class.

Most of the properties of an item defined as belonging to a specific subclass are defined within the subclass itself. However, sometimes in other classes, Template:Cd is used to test if a certain item is an item of that class, and thus new properties can be defined for the item.

List

The table below shows the classes that extend Template:Jicp and the IDs of the items that are restricted as instances of them (in Template:Jicp).

See Template:Slink for details.

Class	Items (id)
AirItem	air
ArmorStandItem	armor_stand
ArrowItem	arrow
BannerItem	white_banner, orange_banner, magenta_banner, light_blue_banner, yellow_banner, lime_banner, pink_banner, gray_banner, light_gray_banner, cyan_banner, purple_banner, blue_banner, brown_banner, green_banner, red_banner, black_banner
BlockItem	Template:Collapse
BoatItem	cherry_boat, birch_chest_boat, birch_boat, acacia_chest_boat, acacia_boat, spruce_chest_boat, spruce_boat, pale_oak_chest_boat, pale_oak_boat, oak_chest_boat, oak_boat, mangrove_chest_boat, mangrove_boat, jungle_chest_boat, jungle_boat, dark_oak_chest_boat, dark_oak_boat, cherry_chest_boat, bamboo_raft, bamboo_chest_raft
BoneMealItem	bone_meal
BottleItem	glass_bottle
BowItem	bow
BrushItem	brush
BucketItem	bucket, water_bucket, lava_bucket
BundleItem	bundle, white_bundle, orange_bundle, magenta_bundle, light_blue_bundle, yellow_bundle, lime_bundle, pink_bundle, gray_bundle, light_gray_bundle, cyan_bundle, purple_bundle, blue_bundle, brown_bundle, green_bundle, red_bundle, black_bundle
CompassItem	compass
CrossbowItem	crossbow
DebugStickItem	debug_stick
DiscFragmentItem	disc_fragment_5
DoubleHighBlockItem	Template:Collapse
DyeItem	white_dye, orange_dye, magenta_dye, light_blue_dye, yellow_dye, lime_dye, pink_dye, gray_dye, light_gray_dye, cyan_dye, purple_dye, blue_dye, brown_dye, green_dye, red_dye, black_dye
EggItem	egg, blue_egg, brown_egg
EmptyMapItem	map
EndCrystalItem	end_crystal
EnderEyeItem	ender_eye
EnderpearlItem	ender_pearl
ExperienceBottleItem	experience_bottle
FireChargeItem	fire_charge
FireworkRocketItem	firework_rocket
FishingRodItem	fishing_rod
FlintAndSteelItem	flint_and_steel
FoodOnAStickItem	carrot_on_a_stick, warped_fungus_on_a_stick
GameMasterBlockItem	command_block, repeating_command_block, chain_command_block, structure_block, jigsaw, test_block, test_instance_block
GlowInkSacItem	glow_ink_sac
HangingEntityItem	painting
HangingSignItem	warped_hanging_sign, spruce_hanging_sign, pale_oak_hanging_sign, oak_hanging_sign, mangrove_hanging_sign, jungle_hanging_sign, dark_oak_hanging_sign, crimson_hanging_sign, cherry_hanging_sign, birch_hanging_sign, bamboo_hanging_sign, acacia_hanging_sign
HoneycombItem	honeycomb
InkSacItem	ink_sac
InstrumentItem	goat_horn
Item	All, see Minecraft:Java_Edition_data_values/Items
ItemFrameItem	item_frame
KnowledgeBookItem	knowledge_book
LeadItem	lead
LingeringPotionItem	lingering_potion
MaceItem	mace
MapItem	filled_map
MinecartItem	minecart, chest_minecart, furnece_minecart, tnt_minecart, hopper_minecart, command_block_minecart
MobBucketItem	pufferfish_bucket, salmon_bucket, cod_bucket, tropical_fish_bucket, axolotl_bucket, tadpole_bucket
NameTagItem	name_tag
PlaceOnWaterBlockItem	lily_pad, frogspawn
PlayerHeadItem	player_head
PotionItem	potion
ProjectileWeaponItem
ScaffoldingBlockItem	scaffolding
ShearsItem	shears
ShieldItem	shield
SignItem	warped_sign, spruce_sign, pale_oak_sign, oak_sign, mangrove_sign, jungle_sign, dark_oak_sign, crimson_sign, cherry_sign, birch_sign, bamboo_sign, acacia_sign
SmithingTemplateItem
SnowballItem	snowball
SolidBucketItem	powder_snow_bucket
SpawnEggItem
SpectralArrowItem	spectral_arrow
SplashPotionItem	splash_potion
SpyglassItem	spyglass
StandingAndWallBlockItem	torch, soul_torch, copper_torch, tube_coral_fan, brain_coral_fan, bubble_coral_fan, fire_coral_fan, horn_coral_fan, dead_tube_coral_fan, dead_brain_coral_fan, dead_bubble_coral_fan, dead_fire_coral_fan, dead_horn_coral_fan, redstone_torch, skeleton_skull, wither_skeleton_skull, zombie_head, creeper_head, dragon_head, piglin_head
ThrowablePotionItem
TippedArrowItem	tipped_arrow
TridentItem	trident
WindChargeItem	wind_charge
WritableBookItem	writable_book
WrittenBookItem	written_book

Items class member access

In many parts of the game's code, within many contexts, direct access to an item's restricted area is used, by Template:Jicp member access, allowing to determine a property of that item.

In certain cases, this item call only serves to create the vanilla datapack, for example by creating item tags, recipes, Minecraft:loot tables and trades. Therefore, this is a property that can be fully controlled by Minecraft:datapacks. However, it's worth noting that many of these properties that we can fully control through data packs (and not through components) can only be controlled by the item's ID, not by its components.

Furthermore, in some cases, it creates a new instance of the item. This could be due to an item origin not controlled by a loot table (such as equipment or wither flowers), a visual effect (such as using items in a GUI), or some other use (such as a mob using an item as a projectile). In these cases, we are not strictly talking about an item property, as we are not discussing how a pre-existing item modifies the game.Template:Note

List

The table below shows all the classes that has a Template:Jicp memmber access, and the number of uses in each class. According to the code of Minecraft:26.1.

Legend：

• red The background indicates that all items within that class are used only for generating the vanilla datapack/resourepack.
• yellowThe background indicates that all items within them are a new instance, representing an item's origin, visual use, etc., and not a property of a pre-existing item.

See Template:Slink, for details of the classes without note

Item class

Template:Expand section

onUseTick(...)

onUseTick

Declaration Header	public void
Parameters	Level level, LivingEntity livingEntity, ItemStack itemStack, int ticksRemaining

Empty, for most items, it doesn't add any properties. However, it can add properties with its implementations, see below.

Uses tree

Implementations

• Template:ItemLink
• Template:ItemLink
• Template:ItemLink

onDestroyed(...)

onDestroyed

Declaration Header	public void
Parameters	ItemEntity itemEntity

Used for items to drop their contents to be destroyed. By default, nothing happens, having an effect only on instances of classes that implement it, see below.

Uses tree

Implementations

• Template:InvLink
• Template:ItemLink

canDestroyBlock(...)

canDestroyBlock

Declaration Header	public boolean
Parameters	ItemStack itemStack, BlockState state, Level level, BlockPos pos, LivingEntity user

Returns false if the player is in Template:Tooltip and the item has the Template:DCL component with Template:Cd set to false. In other cases it returns true.

Note that this method depends exclusively on the component and is not hardcoded. However, the method still has an implementation.

Uses tree

Implementations

• Template:ItemLink

useOn(...)

useOn

Declaration Header	public InteractionResult
Parameters	UseOnContext context

If the Template:DCL 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 Template:Cd. However, default Template:Cd data components exist only for Minecraft:hoes, Minecraft:shovels, and Minecraft:axes; many items still rely on hardcoded usage logic (see the implementations below).

Uses tree

Description of the methods:

• Template:Jicp.Template:Cd: If the player is in Minecraft:adventure mode and the item stack does not have the Template:DCL component corresponding to the clicked block, it returns fail.

Otherwise, call the method implemented in the item stack as item. If the method returns Template:Cd increases the item Template:Cd Minecraft:statistic by one. Returns the return value of the called method.Template:More info

• Template:Jcp.Template:Cd: 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 menu, open the menu and return Template:Cd
• If the block is a portal (end gateway, end portal, or 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 Template:Cd in red on Minecraft:action bar. Return Template:Cd.
• Otherwise return Template:Cd.

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 Template:Cd, which is a method controlled by the block (Template:Cd). Sometimes this method will give different results depending on the item used; see Template:Sl for details.
• If the interaction returns any success, [[Minecraft:Advancement_definition#minecraft:item_used_on_block|Template:Cd]] is activated and the method is completed, returning the same result.
• If the interaction returns Template:Cd and the interacting hand is the mainhand, the player attempts to interact with the block using the Template:Cd method.
  • If the interaction returns any success, [[Minecraft:Advancement_definition#minecraft:default_block_use|Template:Cd]] is activated the method is completed, returning the same result.
• If neither Template:Cd nor Template:Cd returns success, the method continues.

If the item stack is empty or in cooldown, return Template:Cd.

Finally, the Template:Cd method is called. If the player is in creative mode, the stack item quantity is restored, preventing any loss due to the called method.Template:More info If the return is successful, the Template:Cd is activated. Returns the return of the called method.

In Template:Jcp, output demo reminder and return Template:Cd, if demo timer has end. Otherwise, it calls the supermethod, so the method will proceed normally.

• Template:Jcp.Template:Cd: 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|Template:Cd]] 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 Template:Slink or Template:Slink instance with non-empty fluid and is not on cooldown, then send the system error message in Minecraft:action bar with the translation of Template:Cd with the maximum height value of the dimension.

If the return of the called method is Template:Cd or Template:Cd, the player swings the hand used.

Template:More info

Implementations Template:Columns-list Template:Font color The implementation uses a supermethod, calling that method.

Item subclasses

Template:Expand section Only subsections marked with an asterisk (Template:Past) aren't empty.

AirItem

Air has a block Template:Cd, meaning its translation key is Template:Cd. However, unlike other items with this Template:Cd, air is not an instance of Template:Jicp, because Template:Jicp does not extend Template:Jicp.

getName(Template:Tooltip) Template:Hatnote

Defined ignoring the item stack components, therefore, it is always a translation of Template:Cd regardless of the component Template:DCL.

This has an effect on stacked items that are treated as if they were air (for example, items with a count of 0).

Note that many other properties of the air item are defined elsewhere in the code. See Template:Slink.

ArmorStandItem

useOn(Template:Tooltip) Template:Hatnote

If the interaction involves clicking on the bottom face of a block, it fails.

The target position for placing the Minecraft:armor stand is the bottom center of the block next to the interacted block, in the direction of the interacted face. The game simulates the Minecraft:hitbox of an armor stand in this position; if the hitbox collides with a block or intersects with an entity hitbox (except Minecraft:spectators), the interaction fails.

The game attempts to obtain the armor stand, based on the item's components Template:DCL, Template:DCL, and Template:DCL. If it cannot be generated, the interaction fails.

If the armor stand is generated, apply in the following order:

• The armor stand rotates 202.5° according to the player's rotation, but rounds its rotation down to some multiple of 45°;
• The Minecraft:sound event armor stand place (Template:Cd) is played;
• The Minecraft:game event Template:Cd is produced;
• The item stack is shrunk by one.

The interaction returns success given no aforementioned fails occur.

Armor stand entity data:

• Template:Nbt Entity data
  • Template:Nbt inherit/apply components from item stack
  • Template:Nbt: Template:Cd.
  • Template:Nbt: The target position. Try moving up to one block down, looking for a collision box that connects with the armor support's hitbox. This attempt is made before applying the Template:DCL component.
  • Template:Nbt:
    • Template:Nbt: See above.
    • Template:Nbt: Template:Cd.
  • Template:Nbt: With the exception of id, Rotation, Passengers , and UUID, it can be defined by Template:DCL. The Template:DCL only has an effect if the Template:DCL is Template:Cd. CustomName, data, and Pos have priority to be defined by component Template:DCL.

ArrowItem

createArrow(Template:Tooltip)

Creates an Template:Cd projectile entity from the item.

Used by Template:Cd in Template:Slink, and by Minecraft:skeletons and Minecraft:illusioners via Template:Slink.

For regular arrows, creates an arrow projectile with:

• Template:Nbt Entity data
  • Template:Nbt inherit/apply components from item stack
  • Template:Nbt: Template:Cd.
  • Template:Nbt:
    • Template:Nbt: Owner's X coordinate.
    • Template:Nbt: Owner's eye Y coordinate minus Template:Cd.
    • Template:Nbt: Owner's Z coordinate.
  • Template:Nbt: The item stack copy, with count 1.
  • Template:Nbt: The fired from weapon copy, if it exists.
  • Template:Nbt: According to the effect components Template:Cd of the weapon enchantments, if it exists. The item stack can be used for requirements.
  • Template:Nbt: Template:Cd (creative only) if the item has the component Template:DCL, Template:Cd (allowed) otherwise.
  • Template:Nbt: The owner Minecraft:UUID.

asProjectile(Template:Tooltip) Template:Hatnote

Creates an arrow projectile not fired from any weapon, used by Minecraft:dispensers and Minecraft:ominous item spawners, with:

• Template:Nbt Entity data
  • Template:Nbt inherit/apply components from item stack
  • Template:Nbt: Template:Cd.
  • Template:Nbt: The position.
  • Template:Nbt: The item stack copy, with count 1.
  • Template:Nbt: Template:Cd (allowed), regardless of Template:DCL.

BannerItem

getColor()

Used by the [[Minecraft:Recipe_(Java_Edition)#crafting_special_*|Template:Cd]] recipe type to determine whether the banner colors match, and by the [[Minecraft:Recipe_(Java_Edition)#crafting_special_*|Template:Cd]] recipe type to set the Template:DCL of the shield.

This is done by calling the Template:Cd method of Template:Cd on the item's block form, and as such the block forms of a Template:Cd must extend Template:Cd.

BlockItem

Each item in this class is associated with a block, defined in Template:Jicp. With few exceptions, the item has the same id as the associated block and Template:Cd is the item's Template:Cd.

Item overrides methods

useOn(Template:Tooltip) Template:Hatnote

Try placing the block with Template:Cd (see Template:Slink for details).

If the result of place is any success and the item does not have the component Template:DCL, return that result from place. Otherwise, use the item (see Template:Slink) and return the result of use.

shouldPrintOpWarning(Template:Tooltip) Template:Hatnote

If the player has Minecraft:Permission level gamemaster (level 2) and the item has the component Template:DCL, it returns true if the block entity id is Template:Cd, Template:Cd, Template:Cd, Template:Cd, Template:Cd, or Template:Cd. Otherwise, it returns false.

canFitInsideContainerItems() Template:Hatnote

Returns false if the associated block is an instance of Template:Jbcp, in other words, one of the 17 Minecraft:shulker boxes.

onDestroyed(Template:Tooltip) Template:Hatnote

Set the Template:DCL component of the entity item to empty. If the component existed previously, drop all the item stacks it contained at the entity item's position.

Block by item

There are two methods in Template:Jicp related to associating the item with its associated block and vice-versa:

• Template:Cd: Returns the block Template:Cd, defined when registering the item in Template:Jicp.
• Template:Cd: Put the pair Template:Cd in Template:Cd. Used only with the Template:Jicp.Template:Cd map.

In Template:Jicp, ItemBlocks are registered using either the Template:Cd method or the Template:Cd method.

In Template:Cd given a block, an item is created with the same id, and with the block description id, after that Template:Cd is used to save the block and item in Template:Cd. There are some variations, which can be summarized as: adding default components to the item (by Template:Slink), making the item a different class, a subclass of ItemBlock and put alternative blocks in Template:Jicp.Template:Cd.

Only two items have alternate blocks:

• Template:InvLink: has the Template:BlockLink as an alternate block,

• Template:InvLink: has Template:BlockLink, Template:BlockLink, and Template:BlockLink as alternate blocks.

However, in Template:Slink, there is an override of Template:Cd, adding the wallblock corresponding to each item in the list.

In Template:Cd the item's ID is defined separately and uses the item's description ID. Items can have other default components, but it is always a BlockItem and not a subclass. Below is the complete list of items registered with this method:

Resin clump and nether wart has the same ID but it still has different ID descriptions.

The method Template:Cd is only used in Template:Jicp, however Template:Cd has many more uses.

[...]

The Template:Jicp.Template:Cd map is used in the Template:Jicp.Template:Cd method, where for each block it searches for its associated item, and if it doesn't exist, it associates it with the air item. This method is used only in Template:Jbcp.Template:Cd which returns the item associated with the block. The Template:Jbcp.Template:Cd method, however, has multiple uses.

[...]

BoatItem

use(Template:Tooltip) Template:Hatnote

Checks if the player is looking at a block (including fluids) and passes if not. Then checks if any pickable entities' pick hitboxes contain the player's eye position and passes if so.

Then tries to create a boat entity with a type hardcoded for each item ID at the block targeted and fails if the entity cannot be created. If it is spawned, its yaw rotation is set to the player's yaw rotation. Then fails if the boat is intersecting anything except fluid.

Finally, adds the boat to the world, produces an Template:Cd Minecraft:game event, consumes one item from the stack, adds to the item used statistic, and succeeds.

BoneMealItem

All the behavior of bone meal is hardcoded in this class.

useOn(Template:Tooltip) Template:Hatnote

First calls Template:Cd. If it returns Template:Cd, the interaction succeeds, the stack shrinks by one, world event 1505 (bone meal particles and sound) is caused, and an Template:Cd Minecraft:game event is produced.

Otherwise, checks if a full solid face was clicked (passing if not) and calls Template:Cd, succeeding as described above if it returns Template:Cd. If it returns Template:Cd, the interaction passes.

growCrop(Template:Tooltip)

Tries to bone meal a Template:Cd. If it is valid, regardless of whether it succeeds, returns Template:Cd (otherwise returns Template:Cd).

Also used by Minecraft:dispensers and Template:Slink.

growWaterPlant(Template:Tooltip)

Attempts to grow plants underwater, defaulting to Minecraft:seagrass. Returns Template:Cd if the block next to the clicked face is not a full water block, and Template:Cd otherwise.

If used in a biome in Template:Tag link, the block next to the clicked face is replaced with a random block in Template:Tag link if a side face was clicked, and other seagrass blocks that would be placed have a 1/4 chance of being replaced with random blocks from Template:Tag link.

Also used by Minecraft:dispensers.

BottleItem

use(Template:Tooltip) Template:Hatnote

First checks for Minecraft:area effect clouds owned by an Minecraft:ender dragon (i.e. dragon's breath) within 2 blocks of the player's hitbox. If there is at least one, picks one and reduces its radius by 0.5, plays the Template:Cd sound event, produces a Template:Cd game event, triggers the Template:Cd advancement trigger, transforms a bottle (or all of them, if the player is in Creative mode) into Minecraft:dragon's breath, and succeeds.

If there is not any dragon's breath, checks if the player is interacting with water (passing otherwise) and plays the Template:Cd sound event, produces a Template:Cd game event, transforms a bottle (or all of them) into a Minecraft:water bottle, and succeeds.

CompassItem

isFoil(Template:Tooltip) Template:Hatnote

Overridden to Template:Cd if this stack has the Template:DCL component.

inventoryTick(Template:Tooltip) Template:Hatnote

If this stack has the Template:DCL component, updates the tracker (i.e. sets it to empty if it is invalidated).

useOn(Template:Tooltip) Template:Hatnote

If the clicked block was a Minecraft:lodestone, instead play the Template:Cd sound event and create a lodestone compass by setting the Template:DCL component. If in creative mode or with a stack size greater than 1, all components are copied to a new item that gains Template:DCL and the original stack is shrunk by one. The interaction succeeds.

getName(Template:Tooltip) Template:Hatnote

If this stack has the Template:DCL component, instead return the lodestone compass item name (translation Template:Cd)

CushionItem

useOn(Template:Tooltip) Template:Hatnote

Position the cushion. Method partially described in Template:Slink.

The interaction fails if the clicked face is not the up fece. Otherwise, summon an Axis-Aligned Bounding Box (AABB) with size of a cushion's hitbox (16×4×16 pixels), the X and Z axes centered on the interlocking block, and the minimum of the Y-axis at the clicked position.

If a cushion cannot survive in the AABB block (Template:Jcp.Template:Cd), the interaction fails. The test consists of invoking a new AABB block with the same width, but Template:Frac of a pixel higher than the existing AABB block, below the existing AABB. Then, it checks if at least one block position (entire position) containing the new AABB has a block whose interaction box intersects the AABB. If no block intersects, the test fails.

At this point, the interaction returns success on the client side, and so the player moves their hand. Although the interaction may still fail on the server side, as described below:

• If the hitbox of an existing cushion is intersected by the AABB, the interaction fails.
• Try summoning a cushion, with Template:Cd and Template:Cd defined repeatedly by the Template:DCL and Template:DCL components of the item stack. If, for some reason, it is not possible to invoke it, the interaction fails.
• Position the cushion in the same position as the AABB. The y-rotation of the cushion is defined by Template:Cd, where Template:Cd is the player's y-rotation. The x-rotation is defined as zero.
• Set the cushion color to match the item color (the item color is defined by ColorCollection when registering them).
• Play Minecraft:sound event cushion place (Template:Sound)
• Produce the Minecraft:game event Template:Cd (output 14)
• Consumes one item from the player, except if the player is in Template:Tooltip.

The interaction returns success given no aforementioned fails occur.

DebugStickItem

Handles all the behavior of the Minecraft:debug stick as described on its page.

canDestroyBlock(Template:Tooltip) Template:Hatnote

Always returns Template:Cd, and triggers an interaction selecting a block state.

useOn(Template:Tooltip) Template:Hatnote

Triggers an interaction cycling the value of a block state, failing if that interaction fails (if the player cannot use game master blocks, if the block has no properties, or if the item does not have the Template:DCL component) and succeeding otherwise.

DiscFragmentItem

appendHoverText(Template:Tooltip) Template:Hatnote

Define the first line of the tooltip as the translation of Template:Cd in gray (Template:Color).

This line cannot be hidden by the Template:DCL component, except to completely hide the tooltip with Template:Cd set to Template:Cd.

DoubleHighBlockItem

placeBlock(Template:Tooltip) Template:Hatnote

Sets the block above to water if there is water above (including waterlogged blocks) and air otherwise before placing the block normally, effectively replacing the block above while leaving water intact for waterlogging.Template:Info needed

DyeItem

Each item has a default Template:DCL component, defined in Template:Jicp.

When two sheep, cats, or dogs breed, take the color of each parent (the color of the wool or the color of the collar) and search all items that have the component Template:Cd of that color as a default and try to create the first recipe for each pair. If the result of some of these recipes is an item with the component Template:Cd, that color will be used for the offspring; otherwise, a random color from the parents is added.

Thus, the color of these animals depends on the hardcoded property of the dyes, and the color can only be edited along with the item's recipes. Only dyes have the component Template:Cd by default, and each value of the component exists in exactly one dye.

interactLivingEntity(Template:Tooltip) Template:Hatnote

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 Template:Cd component and the item stack has a Template:Cd component.

In case of success, the Minecraft:sound dye use is played, set the sheep color and shrink the item stack by one.

tryApplyToSign(Template:Tooltip) Template:Hatnote

If the stack item does not contain the Template:Cd component, it returns false.

Try changing the text color on the sign, on the side being interacted with, to the color of the dye.

In case of success, the dye used sound is played and returns true. Otherwise, returns false.

EggItem

use(Template:Tooltip) Template:Hatnote

Always succeeds. Plays the Template:Cd sound effect, consumes an item, awards statistics, and spawns an egg projectile with:

• Template:Nbt Entity data
  • Template:Nbt: Template:Cd
  • Template:Nbt:
    • Template:Nbt: Owner's X coordinate.
    • Template:Nbt: Owner's eye Y coordinate minus Template:Cd.
    • Template:Nbt: Owner's Z coordinate.
  • Template:Nbt: a copy of the item stack with the count set to 1.
  • Template:Nbt: The player Minecraft:UUID.

The projectile is fired with an uncertainty of 1 and a power of 1.5.

asProjectile(Template:Tooltip) Template:Hatnote

Used by Minecraft:dispensers and Minecraft:ominous item spawners. Creates an egg projectile with:

• Template:Nbt Entity data
  • Template:Nbt: Template:Cd
  • Template:Nbt: The position.
  • Template:Nbt: a copy of the item stack with the count set to 1.

No item components are used.

EmptyMapItem

use(Template:Tooltip) Template:Hatnote

Always succeeds. Consumes an item, awards statistics, plays the Template:Cd sound effect, creates map data from the player's X and Z position, with a scale of 0, that tracks their position within range, and gives the player a Minecraft:filled map with its Template:DCL component pointing to that map data.

EndCrystalItem

useOn(Template:Tooltip) Template:Hatnote

Fails if the block clicked is not Minecraft:obsidian or Minecraft:bedrock, or if the block above the one clicked is not empty. Then checks for entities in a 1x2x1 box above the clicked block and fails if there are any.

If none of those checks failed, the interaction succeeds, the stack is shrunk by 1, and an end crystal is spawned with:

• Template:Nbt Entity data
  • Template:Nbt: Template:Cd
  • Template:Nbt: The bottom center of the block above the one clicked.
  • Template:Nbt: Template:Cd

No item components are used.

Triggers an Template:Cd Minecraft:game event, and checks if the Minecraft:ender dragon should be respawned if the current dimension has a dragon fight.

EnderEyeItem

getUseDuration(Template:Tooltip) Template:Hatnote

Always returns 0, ignoring item components.

useOn(Template:Tooltip) Template:Hatnote

Passes if the targeted block is not an Minecraft:end portal frame or if the frame is already with eye. Then always succeeds, pushes Minecraft:entities up to compensate for the block's new shape (see details below), sets the targeted frame's Template:Cd state to Template:Cd, shrinks the stack by 1, updates attached Minecraft:comparators, and causes world event 1503.

Then checks if and where an end portal should be activated, and fills the end portal blocks accordingly, causing world event 1038 globally from the center of the 3x3 portal. See Template:Slink for more information on activating the portal.

Entity push details: all entities, except Minecraft:spectator players, whose Minecraft:bounding box intersects the new parte of the end portal frame's Minecraft:collision box (known as 8x3x8 pixels, centered on the top face) are subject to push attempts. The entity attempts to move one block upward and stops when it ceases to intercept the collision box; if it fails, it does not move. If it succeeds, it teleports. Note that this moves entities like Minecraft:cushions, which normally don't move.

use(Template:Tooltip) Template:Hatnote

Passes if the player is targeting an end portal frame, even if filled.

Then starts using the item, and tries to find a structure in Template:Tag link, using the same method used in Template:Cmd. The found structure is not necessarily the closest<ref>Template:Bug</ref>. The search process occurs in the following steps.

1. If the tag is empty, the Minecraft:debug flag Template:Cd is enable, or world option Generate Structures is false, return null
2. List all Minecraft:structure sets that have at least one structure in the tag, prioritizing structures in tag order. If the list is empty, return null.
3. For all Template:Cd type structure sets, search for all Minecraft:chunks where the set of structures can be positioned and check if any exist. If found a structure that is in the tag, consider it as block position Template:Cd. Save the block position in Template:Cd and in Template:Cd the Minecraft:euclidian distance from the player's block to that position, if it is the first structure found or if the distance is less than or equal to the previous Template:Cd.
4. For all Template:Cd type structure sets, search for structures in a 201×201 grid of N×N chunks, where N is the Template:Nbt of the structure set. For each region, a structure is searched for up to one structure.
   • First, search in regions closest to the center, with a Minecraft:manhattan distance (radius varying from 0 to 100). For regions with the same manhattan distance, prioritize those with the smallest X-axis; for regions with the same X-axis, prioritize those with the smallest Z-axis.
   • Upon finding a structure (that is in the tag) with a certain radius, no further searches are made for structures with larger radius, from any structure set. This can lead to premature searches when finding a structure with a large spacing.
   • Upon finding a structure (that is in the tag) with a certain radius, no further searches are made for structures from the same structure set. This creates priority for structures with smaller X or Z axes, even if they are further away from other structures in the same structure set.
   • Each structure found saves its position depending on its chunk position and the Template:Nbt of the structure set. If the player's block position distance is less than or equal to Template:Cd, update Template:Cd and Template:Cd.
5. Retunr Template:Cd (null if none is found).

The interaction ends and returns to consume if nothing is found.

If one is found, a Template:Cd Minecraft:game event is produced, and an eye of ender projectile is created with:

• Template:Nbt Entity data
  • Template:Nbt: Template:Cd
  • Template:Nbt: The center of the player's bounding box.
  • Template:Nbt: The item stack with the count set to 1.

The ender eye is set to target to the structure, but this is not serialized as NBT data<ref>Template:Bug</ref>. They are saved in three local variables, all of which are reset when the entity is reloaded:

• Template:Nbt: It may not exist. If this exists, each tick changes the Template:Nbt of the ender eye as it approaches that position. Defined as Template:Cd if Template:Cd or Template:Cd otherwise, where Template:Cd are the distance from the corner of the block position Template:Cd minus the initial position of the ender eye. Set to null on reload.
• Template:Nbt: Each tick increases by one; if it exceeds 80, it emits the Template:Cd sound event (volume 1, pitch 1) and the eye is destroyed. Set to 0. Set to 0 on reload.
• Template:Nbt: Defines what happens after the eye is destroyed, in the entity's position. If true, it summons an item entity with the same ID as the Template:Nbt; the components are not preserved. If false, causes world event 2003. Template:Tooltip defined with an 80% chance of being Template:Cd. Set to Template:Cd on reload.

Finally, trigger the advancement trigger [[Minecraft:Advancement_definition#minecraft:used_ender_eye|Template:Cd]], with a distance is calculated by Template:Cd, where Template:Cd are the distance from the player and Template:Cd, the Template:Cd sound event is played at a Template:Tooltip pitch between 0.33 and 0.5, an item is consumed, and Minecraft:statistics (Template:Cd) are awarded. Return success_server.

EnderpearlItem

use(Template:Tooltip) Template:Hatnote

Always succeeds. Plays the Template:Cd sound effect, consumes an item, awards statistics, and spawns an ender pearl projectile with:

• Template:Nbt Entity data
  • Template:Nbt: Template:Cd
  • Template:Nbt:
    • Template:Nbt: Owner's X coordinate.
    • Template:Nbt: Owner's eye Y coordinate minus Template:Cd.
    • Template:Nbt: Owner's Z coordinate.
  • Template:Nbt: It depends on the owner's rotation (<math>xRot</math> and <math>yRot</math>):
    • Template:Nbt: <math>\left( -\sin\left(yRot \cdot \pi/180\right) \cdot \cos\left(xRot \cdot \pi/180\right) + 0.0172275 \cdot \left(\text{nextDouble}() - \text{nextDouble}()\right) \right) \cdot 1.5</math>
    • Template:Nbt: <math>\left( -\sin\left(xRot \cdot \pi/180\right) + 0.0172275 \cdot \left(\text{nextDouble}() - \text{nextDouble}()\right) \right) \cdot 1.5</math>
    • Template:Nbt: <math> \left( \cos\left(yRot \cdot {\pi}/{180}\right) \cdot \cos\left(xRot \cdot \pi/180\right) + 0.0172275 \cdot \left(\text{nextDouble}() - \text{nextDouble}()\right) \right) \cdot 1.5</math>
  • Template:Nbt: It depends on the Template:Nbt (<math>xMot</math>, <math>yMot</math>, <math>zMot</math>):
    • Template:Nbt: <math>\operatorname{atan2}\left(yMot, \, (xMot)^2 + (zMoy)^2\right) \cdot 57.2957763671875</math>
    • Template:Nbt: <math>\operatorname{atan2}\left(xMot, \, zMot\right) \cdot 57.2957763671875</math>
  • Template:Nbt: a copy of the item stack with the count set to 1.
  • Template:Nbt: The player Minecraft:UUID.
  • Template:Nbt: NBT ags that vary by entity effect according to enchantments with the Template:Cd effect component on the Template:DCL item component. It is calculated last. Such effects have an eventual scope beyond the tags.

The projectile is fired with an uncertainty of 1 and a power of 1.5, defined the motion and rotation (see above).

ExperienceBottleItem

use(Template:Tooltip) Template:Hatnote

Always succeeds. Plays the Template:Cd sound effect, consumes an item, awards statistics, and spawns an experience bottle projectile with:

• Template:Nbt Entity data
  • Template:Nbt: Template:Cd
  • Template:Nbt:
    • Template:Nbt: Owner's X coordinate.
    • Template:Nbt: Owner's eye Y coordinate minus Template:Cd.
    • Template:Nbt: Owner's Z coordinate.
  • Template:Nbt: a copy of the item stack with the count set to 1.
  • Template:Nbt: The player Minecraft:UUID.

The projectile is fired with an uncertainty of 1, a power of 0.7, and a pitch offset of -20°.

asProjectile(Template:Tooltip) Template:Hatnote

Used by Minecraft:dispensers and Minecraft:ominous item spawners. Creates an experience bottle projectile with:

• Template:Nbt Entity data
  • Template:Nbt: Template:Cd
  • Template:Nbt: The position.
  • Template:Nbt: a copy of the item stack with the count set to 1.

No item components are used.

createDispenseConfig() Template:Hatnote

Sets the projectile to be dispensed at 0.5 times the default uncertainty and 1.25 times the default power.

See Minecraft:Projectile#Shot from dispenser for these values.

FireChargeItem

useOn(Template:Tooltip) Template:Hatnote

First checks if the targeted block is an unlit Minecraft:campfire, Minecraft:soul campfire, Minecraft:candle, dyed candle, Minecraft:cake with candle, or cake with dyed candle. If so, its Template:Cd state is set to Template:Cd, the Template:Cd sound effect is played, a Template:Cd Minecraft:game event is produced.

If not, checks if a Minecraft:fire block can be placed adjacent to the clicked face, and if so places the fire block, emits the sound effect, produces a Template:Cd game event.

If either case succeeded, the stack is shrunk by 1 and the interaction succeeds. Otherwise the interaction fails.

asProjectile(Template:Tooltip) Template:Hatnote

Used by Minecraft:dispensers and Minecraft:ominous item spawners. Randomizes the direction slightly and creates a small fireball projectile with:

• Template:Nbt Entity data
  • Template:Nbt: Template:Cd
  • Template:Nbt: The position.
  • Template:Nbt: The randomized direction. Each axis receives the value -1, 0, or 1 (depending on the direction) plus a random number Template:Cd. Each axis has the random number calculated separately. After that, the vector is normalized and mutilates by 0.1.Template:More info
  • Template:Nbt: A copy of the item stack with the count set to 1.

shoot(Template:Tooltip) Template:Hatnote

Overridden to do nothing, since Template:Nbt is set by Template:Cd instead.

createDispenseConfig() Template:Hatnote

Sets the projectile to be dispensed fully outside the dispenser, with an uncertainty of 6.6666665, a power of 1, and a world event override of 1018.

FireworkRocketItem

useOn(Template:Tooltip) Template:Hatnote

Passes if not used by a gliding player. Otherwise succeeds, shrinking the stack by 1 and spawning a firework rocket projectile with:

• Template:Nbt Entity data
  • Template:Nbt: Template:Cd
  • Template:Nbt: The clicked location, offset away from the block by 0.15 blocks.
  • Template:Nbt: A copy of the item stack.
  • Template:Nbt: 0
  • Template:Nbt: The firework lifetime depending on its Template:DCL component: 10 * Template:Cd (or 0 if there is no Template:DCL component) + random(0 to 5) + random(0 to 6)
  • Template:Nbt: The player Minecraft:UUID.

use(Template:Tooltip) Template:Hatnote

Passes unless the player is gliding. Otherwise succeeds, breaking all Minecraft:leads attached to the player (and playing Template:Cd if there were any), consuming one item, awarding statistics, and spawning a firework rocket projectile stuck to the player (which is not serialized as NBT data) with:

• Template:Nbt Entity data
  • Template:Nbt: Template:Cd
  • Template:Nbt: The player's position.
  • Template:Nbt: A copy of the item stack.
  • Template:Nbt: 0
  • Template:Nbt: The firework lifetime, same formula as above.
  • Template:Nbt: The player Minecraft:UUID.

asProjectile(Template:Tooltip) Template:Hatnote

Creates a firework rocket projectile with:

• Template:Nbt Entity data
  • Template:Nbt: Template:Cd
  • Template:Nbt: The position.
  • Template:Nbt: A copy of the item stack with the count set to 1.
  • Template:Nbt: 0
  • Template:Nbt: The firework lifetime, same formula as above.
  • Template:Nbt: Template:Cd

createDispenseConfig() Template:Hatnote

Sets the projectile to be dispensed 0.50001 blocks away from the center of the dispenser, with an uncertainty of 1, a power of 0.5, and a world event override of 1004.

FishingRodItem

use(Template:Tooltip) Template:Hatnote

Always succeeds.

If the player does not already have a fishing hook attached:

• The Template:Cd sound effect is played.
• The Template:Cd and Template:Cd effect components are applied from enchantments on the item stack, they define local fishing bobber variables without saving them in the NBT tag:
  • Template:Nbt: Used in the Minecraft:loot context of the fishing loot table, Template:Cd. Defined by the maximum between 0 and the value given by Template:Cd.
  • Template:Nbt: How much is timeUntilLured reduced after being defined as a random number between 100 and 600 (both inclusive). Defined as a maximum between 0 and 20 times the value given by Template:Cd.
• A Minecraft:fishing bobber is spawned with the fishing time reduction and luck bonus (which are not serialized) and with:

• Template:Nbt Entity data
  • Template:Nbt: Template:Cd
  • Template:Nbt: The player UUID.
  • Template:Nbt: The player's eye position, offset by 0.3 blocks in the XZ plane in the direction of their Y rotation.
  • Template:Nbt: The vector pointing away from the player in the XZ plane, with a Y motion of <math>clamp(-\tan(-xRotation), -5, 5)</math>, normalized with a length of 0.6, and then offset on each axis by random numbers in a triangular distribution around 0.5 with a spread of 0.0103365.
  • Template:Nbt:
    • Template:Nbt <math>atan2(Motion.x, Motion.z)</math> to degrees
    • Template:Nbt <math>atan2(Motion.y, length(Motion.xz))</math> to degrees
  • Template:Nbt: NBT ags that vary by entity effect according to enchantments with the Template:Cd effect component on the Template:DCL item component. It is calculated last. Such effects have an eventual scope beyond the tags.

• The item used statistic is awarded.
• An Template:Cd Minecraft:game event is produced.

If the player does already have a fishing hook attached:

• The fishing bobber is retrieved.
• The item stack is damaged by one of these criteria:
  • 3 if an item stack was hooked.
  • 5 if another entity was hooked.
  • 1 if the bobber got a bite fishing, which then rolls the Template:Cd loot table and creates the resulting item.
  • 2 if the bobber was on the ground.
  • 0 by default.
• The Template:Cd sound effect is played.
• An Template:Cd game event is produced.

FlintAndSteelItem

useOn(Template:Tooltip) Template:Hatnote

First checks if the targeted block is an unlit Minecraft:campfire, Minecraft:soul campfire, Minecraft:candle, dyed candle, Minecraft:cake with candle, or cake with dyed candle. If so, its Template:Cd state is set to Template:Cd, the Template:Cd sound effect is played, a Template:Cd Minecraft:game event is produced, the item stack is damaged by 1, and the interaction succeeds.

If not, checks if a Minecraft:fire block can be placed adjacent to the clicked face, and if so places the fire block, emits the sound effect, produces a Template:Cd game event, triggers the Template:Cd advancement trigger, damages the item by 1, and succeeds.

If the fire block cannot be placed the interaction fails.

FoodOnAStickItem

Each FoodOnAStickItem has an interactable entity type and an amount to damage the item when used, set for each item ID:

• Minecraft:Carrot on a Stick can interact with Minecraft:pigs and is damaged by 7 when used.
• Minecraft:Warped Fungus on a Stick can interact with Minecraft:striders and is damaged by 1 when used.

use(Template:Tooltip) Template:Hatnote

If the player is riding an entity that is Template:Cd and that is the entity type set for this item, the entity is boosted, the item is damaged by the amount set for this item, and if it breaks it is converted to Template:Cd (with all components copied, count set to 1, and damage set to 0). The interaction succeeds.

If those conditions are not met, the item used statistic is awarded and the interaction passes.

GameMasterBlockItem

getPlacementState(Template:Tooltip) Template:Hatnote

Overridden to null if placed by a player that cannot use game master blocks (i.e. is not in Creative mode), making place interactions fail.

GlowInkSacItem

tryApplyToSign(Template:Tooltip) Template:Hatnote

Try changing Template:Cd on the Minecraft:sign's front or back text (depending on isFrontText) to Template:Cd.

If successful, the Template:Cd sound effect is played and returns Template:Cd. Otherwise (if the text was already glowing) returns Template:Cd.

NameTagItem

interactLivingEntity(Template:Tooltip) Template:Hatnote

The interaction will only be successful, instead of pass, when:

• the item has a Template:DCL component, and
• the entity isn't a Minecraft:player, Minecraft:leash knot, Minecraft:lightning bolt, or Minecraft:fishing bobber.

If the entity is alive, sets its Template:Cd to be the same as the name tag. If the entity is a mob, also sets Template:Cd true. Shrink the item stack of the item by one.

Note: This method is only called for living entities, so it ends up being a redundant under certain conditions. Even though the ender dragon is a living entity, this method is never called by it because when trying to interact with it, the Template:Cd is actually being interacted, which is not a living entity.

PotionItem

useOn(Template:Tooltip) Template:Hatnote

The interaction will only be successful, instead of pass, when:

• the face of the interacted block was not directed downward,
• the block is in the #convertable_to_mud tag, and
• the potion's content is water.

In case of success, apply in the following order:

1. Play the generic splash Minecraft:sound event (Template:Cd),
2. Set Minecraft:glass bottle in hand,
3. Send splash particles,
4. Play the bottle empty sound event (Template:Cd),
5. Produce the Minecraft:game event Template:Cd,
6. Convert the block to Minecraft:mud.

getName(Template:Tooltip) Template:Hatnote

If the item has the component Template:Cd, the name name is defined from it. The item uses the translation key Template:Cd, where Template:Cd is the custom name of the potion contents, if available, and otherwise is the name of the potion in potion contents (see Template:Slink), if available. If nether is available, is "Template:Cd".

This name will replace the name defined by Template:DCL. However, it can still be replaced by the Template:DCL, if available.

ShieldItem

getName(Template:Tooltip) Template:Hatnote

If the item has the component Template:DCL, the name is defined from it. The item uses the translation key Template:Cd.

This name will replace the name defined by Template:DCL component. However, it can still be replaced by the Template:DCL component, if available.

SmithingTemplateItem

New SmithingTemplateItem

Each instance of SmithingTemplateItem has a series of class-specific attributes, which are defined by Template:Cd. However, these attributes are not defined separately for each item; instead, they are defined by the Template:Cd and Template:Cd methods, where respectively defines the attributes of netherite upgrade and of all armor trims. In Template:Jicp, only the item components are defined (by Template:Slink, which in this case is only the Template:DCL component).

These methods use the Template:Cd, Template:Cd, Template:Cd, and Template:Cd auxiliary methods, and many auxiliary constants to create these attributes. Below is the complete table of these attributes:

Attribute	Items	Value
appliesTo	Armor Trim	Minecraft:Text component format	Template:Cd
		Text in Template:Mono	"Armor" (Template:Color)
	Netherite Upgrade	Text component format	Template:Cd
		Text in Template:Mono	"Diamond Equipment" (Template:Color)
ingredients	Armor Trim	Text component format	Template:Cd
		Text in Template:Mono	"Ingots & Crystals" (Template:Color)
	Netherite Upgrade	Text component format	Template:Cd
		Text in Template:Mono	"Netherite Ingot" (Template:Color)
baseSlotDescription	Armor Trim	Text component format	Template:Cd
		Text in Template:Mono	"Add a piece of armor" (Template:Color)
	Netherite Upgrade	Text component format	Template:Cd
		Text in Template:Mono	"Add diamond armor, weapon, or tool" (Template:Color)
additionsSlotDescription	Armor Trim	Text component format	Template:Cd
		Text in Template:Mono	"Add ingot or crystal" (Template:Color)
	Netherite Upgrade	Text component format	Template:Cd
		Text in Template:Mono	"Add Netherite Ingot" (Template:Color)
baseSlotEmptyIcons	Armor Trim	Asset ID
		Textures
	Netherite Upgrade	Asset ID	Template:Flatlist
		Textures	Template:Flatlist
additionalSlotEmptyIcons	Armor Trim	Asset ID	Template:Flatlist
		Textures	Template:Flatlist
	Netherite Upgrade	Asset ID	Template:Flatlist
		Textures	Template:Flatlist

Asset ID refers to textures file path in Template:Mono.

Append hover text

public void appendHoverText(Template:Tooltip) Template:Hatnote

Add the following lines to the beginning of the item's tooltip, in order:

• "Smithing Template" (Template:Color)
  • Template:Cd
• Empty line
  • Template:Cd
• "Applies to:" (Template:Color)
  • Template:Cd
• Space append to Template:Cd
  • Template:Cd
• "Ingredients:" (Template:Color)
  • Template:Cd
• Space append to Template:Cd
  • Template:Cd

Smithing table screen

There are 4 methods that always give the assigned values ​​of the sprint items, namely Template:Cd, Template:Cd, Template:Cd, and Template:Cd. All of them are used only in the Template:Jcp class. This class defines the behavior of the menu slots in the Minecraft:smithing table, controlling both the sprint that appears in empty slots and the tooltip when hovering the mouse over an empty slot. Furthermore, this class uses two instanceof of SmithingTemplateItem (and in no other class of the code is it used instanceof of SmithingTemplateItem).

Slot background

Slots 0, 1, and 2 of the menu use a rendering of their variable background given by a list of identifiers (asset IDs), defined by the class Template:Jcp. With each tick update:

• If the icons list is different from the old icons list, update the icons list and reset the index of the list to zero.
• If the current list is not empty:
  • Increase the tick count by one.
  • If the tick count is a multiple of 30, increase the index of the identifier by one; return to zero if it exceeds the limit of the list.

And when render the slot background:

• If the list is empty or the slot is not empty: do nothing.
• If the tick count is greater than 30 and fewer than t + a < 4.0, where t is how many ticks have passed the last multiple of 30: render the previous icon (one index lower or the last one in the list if the index is zero) with Template:Cd transparency.Template:More info
• Renderize the current index with Template:Cd of transparency.

Note that in this way each icon occupies the slot for 30 ticks and has a smooth transition of 4 ticks.

In Template:Jcp, each tick updates the tick of Template:Jcp, from slots 0, 1, and 2, with a list that may vary:

• For slot 0, a list of two elements is always used; these are: Template:Mono and Template:Mono.

Template:Flatlist

• For slot 1, if there is no instance of SmithingTemplateItem in slot 0, the list is empty. If there is, it is the Template:Cd of the item.
• For slot 2, if there is no instance of SmithingTemplateItem in slot 0, the list is empty. If there is, it is the Template:Cd of the item.

Boarding Tooltips

Depending on the mouse position, among other factors, the switcher table menu renders a tooltip.

• Mouse over a rectangular area around the arrow: if the recipe has an error (has items in slots 0, 1, and 3 but no result): "Item can't be upgraded this way" (Template:Color)
  • Template:Cd
  • When there is a recipe error, it also renders a red X above the arrow:
    • File:GUI error.png Template:Mono
• If the mouse is in slot 0 and it is empty: "Add Smithing Template" (Template:Color)
  • Template:Cd
• If the mouse is in slot 1, it is not empty, and slot 0 has an instance of SmithingTemplateItem: the Template:Cd from item in slot 0.
• If the mouse is in slot 2, it is not empty, and slot 0 has an instance of SmithingTemplateItem: the Template:Cd from item in slot 0.
• In any other case: it does not render a menu tooltip (although it continues to render item tooltips normally).

WritableBookItem

use(Template:Tooltip) Template:Hatnote

Open item GUI and increases the Template:Cd Minecraft:statistic by one. Always returns successful.

Note:

The item GUI depends on the components Template:DCL and Template:DCL. Therefore:

• If the item does not have either component: nothing is opened, but there is still an increase in statistics and usage animation.
• If the item has only one of these components: the corresponding GUI opens.
• If both components are present: both GUIs open, but the written book content GUI completely overlays the writable book content GUI, which the player can see briefly on the screen.

Therefore, the GUI are entirely dependent on the components and independent of the item ID. However, it is only possible to open them with the Minecraft:book and quill and Minecraft:written book, since only these items attempt to open the GUI.

WrittenBookItem

use(Template:Tooltip) Template:Hatnote

Completely identical to Template:Cd; see the Template:Slink.

Items member access

Blocks

Entity

Client Template:Columns-list Item Template:Columns-list Loot Template:Columns-list

Misc Template:Columns-list

DispenseItemBehavior

bootStrap()

Defines the item's behavior when Minecraft:dispenser. The behaviors Template:Cd and Template:Cd are largely defined uniquely for each item.

Item	Behavior
Template:InvLink	ProjectileBehavior
Template:InvLink
Template:InvLink
Template:ItemLink
Template:InvLink
Template:InvLink
Template:InvLink
Template:InvLink
Template:InvLink
Template:InvLink
Template:InvLink
Template:InvLink	DefaultDispenseItemBehavior
Template:InvLink	OptionalDispenseItemBehavior
Template:ItemLink	BoatDispenseItemBehavior
Template:ItemLink
Template:InvLink	filledBucketBehavior
Template:InvLink
Template:InvLink
Template:ItemLink
Template:InvLink	DefaultDispenseItemBehavior
Template:InvLink	OptionalDispenseItemBehavior
Template:InvLink	OptionalDispenseItemBehavior
Template:InvLink	OptionalDispenseItemBehavior
Template:BlockLink	shulkerBoxDispenseBehavior
Template:InvLink	OptionalDispenseItemBehavior
Template:InvLink	OptionalDispenseItemBehavior
Template:InvLink	ShearsDispenseItemBehavior
Template:InvLink	OptionalDispenseItemBehavior
Template:InvLink	OptionalDispenseItemBehavior
Template:InvLink	DefaultDispenseItemBehavior
Template:InvLink	MinecartDispenseItemBehavior
Template:InvLink
Template:InvLink
Template:InvLink
Template:InvLink
Template:InvLink

AnvilMenu

createResult()

If the Minecraft:anvil input is an enchanted book, it will initially consider any Minecraft:enchantment as compatible. However, if the enchantment is the same or does it conflict with any enchantment in the current list of enchantments in the result, it will no longer be considered compatible.

In other words, it's as if the enchanted book were in [[Minecraft:Enchantment_definition#JSON_format|Template:Cd]] for all enchantment definition, when we consider the anvil.

CartographyTableMenu

mayPlace(Template:Tooltip) Template:Hatnote

Returns true only if it is one of the three items listed above. Used to determine which items can be placed in the slot 1 of the Minecraft:cartography table.

setupResultSlot(Template:Tooltip)

Used to define the result item of the cartography table:

• If the Template:Cd (item in slot 0) does not have a Template:Cd (data associated with its Template:DCL component), it will not yield any results.

• If it's paper and the Template:Cd is not locked and has a scale less than 4, the resulting is one copy of the Template:Cd with the Template:DCL component set to 1 (SCALE).

• If it's glass and the Template:Cd is not locked, the resulting is one copy of the Template:Cd with the Template:Cd component set to 0 (LOCK).

• If it's empty map, the resulting is two copy of the Template:Cd.

Note: It's possible to use the cartography table regardless of the Template:Cd ID; it only needs to have the Template:Cd component with data. However, when retrieving an item that the ID isn't filled_map with the Template:Cd component, the game crashes<ref>Template:Bug</ref>. However, using the empty map still works for item duplication.

quickMoveStack(Template:Tooltip)

When using the quick click (Template:Keys + click) in the inventory with the cartography table menu is open, it attempts to move these items to slot 1. Notes:

• If the item has the Template:Cd component, it attempts to move it to slot 0 and does not go to slot 1 (even if it fails to go to slot 0).
• This prevents quick clicking from moving them between storage slots and hotbar slots and vice versa, when the cartography table menu is open. Even if the itens fails to move to the slot 1.

EnchantmentMenu

Template:ItemSprite mayPlace(Template:Tooltip) Template:Hatnote

Only lapis lazuli can be placed in the slot 1 of Minecraft:enchantment table.

Template:ItemSprite clickMenuButton(Template:Tooltip)

Right before a book is enchanted on an enchantment table, it becomes an Minecraft:enchanted book.

Template:ItemSprite getEnchantmentList(Template:Tooltip)

When creating a list of enchantments to enchant a book on an enchantment table, remove one enchantment at random if the list has more than one enchantment.

Template:ItemSprite quickMoveStack(Template:Tooltip)

When using the quick click (Template:Key + click) in the inventory with the enchantment table menu is open, it attempts to move the lapis lazuli to slot 1. This prevents quick clicking from moving the lapis lazuli to slot 0.

FurnaceFuelSlot

isBucket(Template:Tooltip)

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 Template:Cd, to allow the bucket to be used in the fuel slot, even if it is not Minecraft:fuel (i.e it does has not the component Template:DCL).
  • 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 Template:Cd, to limit the maximum number of buckets in the fuel slot to one.

GrindstoneMenu

removeNonCursesFrom(Template:Tooltip)

When using an enchanted book on the Minecraft:grindstone, after all non-curses enchantments have been removed, if the enchanted book does not retain an (curse) enchantment, it is transmuted into a Minecraft:book.

BeehiveBlock

useItemOn(Template:Tooltip)

It encodes the interaction of an item on a Minecraft:bee nest and on a Minecraft:beehive.

If the honey level is less than 5, or the item is not one of those listed below, the interaction returns 'try with empathy hand', otherwise returns success. The interaction depends on the item:

• If the item is a shears, apply in the following order:
  • drop the loot table Template:Cd (3x Template:ItemLink);
  • the Minecraft:sound event beehive shear (Template:Cd) is played;
  • causes one damage from the shear;
  • and produce the game event Template:Cd.
• If is glass bottle, apply in the following order:
  • shrink the item by one;
  • the sound event bottle fill (Template:Cd) is played;
  • give the player a Minecraft:honey bottle, placing it in their hand if it's empty; otherwise, try placing it in their inventory. If that's not possible, the honey bottle is dropped;
  • and produce the game event Template:Cd.

For both items, after that, increases the item used Minecraft:statistic by one and test if the beehive is in the smoke. If not, proceed in the following order:

• if there is at least one bee in the hive, each Minecraft:bee in a 17x13x17 area around the hive becomes aggressive toward a random player in the same area;
• all the bees leave the hive and become aggressive toward the player.

Then, even if the beehive is in the smoke, the honey level is reduced to zero.

CandleCakeBlock

useItemOn(Template:Tooltip)

When interacting with an flint and steel or a fire charge on a cake with candle or a cake with dyed candle, the method immediately returns Template:Cd. The effect of these items on the cake is determined by Template:Cd in its classes (see Template:Slink, Template:Slink and Template:Slink).

This also prevents the player from trying to eat the cake, unlike all other items. Note that with these items, the player cannot eat the cake even if the candle is already lit.

ChiseledBookShelfBlock

addBook(Template:Tooltip)

When adding an enchanted book to the Minecraft:chiseled bookshelf, use Minecraft:sound event Template:Cd (Template:Sound) instead of Template:Cd (Template:Sound).

Note: The items that can be added to the chiseled bookshelf are controlled by the tag Template:Tag link, therefore it is not a hardcoded property.

removeBook(Template:Tooltip)

When remove an enchanted book to the chiseled bookshelf, use sound event Template:Cd (Template:Sound) instead of Template:Cd (Template:Sound).

OutputContainer

canTakeItemThroughFace(Template:Tooltip)

Returns whether a Template:Cd 8 Minecraft:composter face can move an item to a Minecraft:hopper or Minecraft:minecart with hopper.

Returns true iff the face is dowm, the item to be removed is a bone meal, and no item has been removed from the container.

In practice, requiring the item to be bone meal doesn't change anything, as this is the only item that can be in the simple container, and this is hardcoded when generating the simple container. Although this may change with Minecraft:mods or future updates (such as composter extraction being controlled by a Minecraft:loot table).

Whenever a hopper is enabled and not Template:Tooltip, it attempts to remove an item from the composter; even if it fails, the composter is emptied. For example, a hopper with a single redstone in each slot under a composter will empty it but won't extract anything.<ref>Template:Bug</ref>

LightBlock

getShape(Template:Tooltip)

Define the light block shape. The shape depends on the context; if the player is holding the light item, it will be a full block; otherwise, it will be empty.

PowderSnowBlock

canEntityWalkOnPowderSnow(Template:Tooltip)

Used in Template:Cd to help test whether the Minecraft:powder snow has a full block Minecraft:collision box.

Returns true iff the entity is in Template:Tag link tag or the entity is a living entity and has a leather border in the Template:Cd slot.

By Template:Cd the powder snow's collision box is empty by default, but it can change depending on the context:

• If it is being placed or the context does not have an entity: empty
• If the entity is falling for more than 2.5 blocks: A column of 16×14.4×16 pixels
• If the entity is a falling block: Full block (16×16×16)
• If the entity is above the block, isn't Minecraft:sneaking and Template:Cd: Full block (16×16×16)

PumpkinBlock

useItemOn(Template:Tooltip)

When using a shears on a Minecraft:pumpkin, instead of returning 'try_with_empty_hand' like other items, returning 'success' and occurs:

• Set Template:Cd as the direction of the interaction or in the opposite direction from the player if the interaction occurred on the y-axis,
• Drop the Minecraft:loot table Template:Cd (4x Template:ItemLink), in Template:Cd,
• Player the Minecraft:sound event pumpink carve (Template:Sound).
• Convert the pumpkin into a Minecraft:carved pumpkin with the face given by Template:Cd,
• Reduces the Minecraft:durability of the shear by 1,
• Produce the Minecraft:game event Template:Cd,
• Increases the item Template:Cd Minecraft:statistic by one.

RespawnAnchorBlock

isRespawnFuel(Template:Tooltip)

Used in Template:Cd to test if the item is fuel for the Minecraft:respawn anchor. Returns true iff the item is a glowstone.

In Template:Cd, when use the glowstone on the respawn anchor with Template:Cd < 4, the following occurs:

• Increase the anchor's Template:Cd by one
• Produce the Minecraft:game event Template:Cd,
• Player the Minecraft:sound event respawn anchor charge (Template:Sound),
• Shrink the item stack by one,
• Retunr Template:Cd

If the player has glowstone in their offhand but in their mainhand, and is interacting with the mainhand, and the Template:Cd is less than 4, returns 'pass' instead of 'try with empty hand'. This prevents the setting respawn and exploding at the anchor at the same time.

SweetBerryBushBlock

useItemOn(Template:Tooltip)

If the item stack is a bone meal and the Minecraft:sweet berry bush's Template:Cd is not 3, the maximum, then return 'pass' instead of 'try with empty hand'. This causes the bone meal effect to be applied (see Template:Slink and Template:Slink) and prevents the attempt to harvest the sweet berry bush.

TntBlock

useItemOn(Template:Tooltip)

If the item used in Minecraft:TNT is one of these:

• If the Template:Gmr game rule is Template:Cd:
  • Send in Minecraft:action bar "TNT explosion are disabled" (Template:Cd),
  • Return Template:Cd
• If the game rule is Template:Cd:
  • Summon a Minecraft:primed TNT (with Template:Cd 80) in the block's position,
  • Play the Minecraft:sound event tnt primed (Template:Sound),
  • Produce the Minecraft:game event Template:Cd,
  • Set air block at the block's position,
  • If the item is Minecraft:flint and steel, reduces the Minecraft:durability by 1, else, shrink the item stack by one,
  • Increase the item used statistic by one,
  • Return Template:Cd.

Otherwise, it returns 'try with empty hand' (but currently TNT has no effect on Template:Cd, thus is the same that return 'pass').

TripWireBlock

playerWillDestroy(Template:Tooltip)

When a player destroys a Minecraft:tripwire, just before it is removed, if the item in mainhand is a shears:

• Set the tripwire's Template:Cd to true and update the adjacent blocks,
• Produce the Minecraft:game event Template:Cd.

After the tripwire is broken, it updates the neighboring blocks as if it still existed and was Template:Cd true. This causes the Template:Tooltip Minecraft:tripwire hook to recalculate its stats, considering this wire as "wireSource". If Template:Cd is false, the tipwire hook will set its Template:Cd to true (because has a connected tripwire that is Template:Cd and not Template:Cd). If Template:Cd is true, because the disarmed tripwire is the "wireSource", it will set the tripwire hood's Template:Cd to false, and consequently set Template:Cd to false. In both cases, because there is a "wireSource", the tripwire hood will be recalculated its stats at 10 ticks (this time without a "wireSource", and probably resulting in both Template:Cd and Template:Cd false).

In other words, unless there are other tripwire interfering:

• Destroy a tripwire without shears: the connected tripwire hooks immediately set Template:Cd true and remain Template:Cd true. After 10 ticks they set Template:Cd and Template:Cd to false.
• Destroy a tripwire with shears: the tripwire hooks immediately set Template:Cd to false and remain Template:Cd false.

WeatheringCopperGolemStatueBlock

useItemOn(Template:Tooltip)

When using an item that is not in Template:Tag link in the Minecraft:copper golem statue, Minecraft:exposed copper golem statue, Minecraft:weathered copper golem statue, or Minecraft:oxidized copper golem statue:

• If the item is a honeycomb, return Template:Cd. Thus, the use of the item will depend on the Template:Cd (see Template:Slink and Template:Slink)
• Else, update the golem pose and return Template:Cd.

If the item is in the tag Template:Cd:

• If the block is (unaffected) copper golem statue it will try to generate a copper golem, if successful it will return Template:Cd.
• Else, return Template:Cd.

WitherSkullBlock

canSpawnMob(Template:Tooltip)

Used to test if an item to be dispensed can be helpful in spawning the Minecraft:wither. For the item to be dispensed as a block, it is necessary that, in addition to this method returning true, that the Template:Cd (the target where the dispenser attempts to place the block) is Minecraft:air, cave air or void air.

Returns true if all the points below occur:

• The item is a wither skeleton skull.
• The y-axis of the Template:Cd is at least two blocks above the dimension y-minimum.
• The difficulty is not peaceful.
• In any of the three axes and in any of the four rotations forms the pattern below, where some Template:BlockSprite is the Template:Cd (it can have any block in Template:BlockSprite), Template:BlockSprite is a block in the tag Template:Tag link and Template:BlockSprite is air, cave air or void air.

Requiring the item to be a wither skeleton skull is circular, since only the wither skeleton skull has the behavior in the dispenser to try to spawn the wither, and this behavior is also hardcoded (see Template:Slink). However, this property may be effective if in the future it becomes possible to customize item behaviors in the dispenser.

AbstractFurnaceBlockEntity

Define the behavior of Minecraft:block entity associated with a Minecraft:furnace, Minecraft:blast furnace and Minecraft:smoker.

Template:InvLink Template:ItemSprite burn(Template:Tooltip)

Used at the end of the Minecraft:smelting process, to add the result to output slot (slot 2).

After adding the result to output slot, if the item in ingredient slot (slot 0) is a wet sponge and the item in fuel slot (slot 1) is a bucket, set a water bucket in fuel slot.

After that, shrink 1 item from ingredient slot.

Template:ItemSprite canPlaceItem(Template:Tooltip)

Tests whether a hopper, minecart with hopper or a Minecraft:dropper can place item in the container.

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 (has a data component Template:DCL) 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).

BrewingStandBlockEntity

Define the behavior of Minecraft:block entity associated with a Minecraft:brewing stand.

canTakeItemThroughFace(Template:Tooltip)

Tests whether the item in the container can be take by a hopper or minecart with hopper.

Returns true only if the slot is not the slot 3, or if the slot is 3 and the item is a glass bottle.

This was probably intended to take the glass bottle that could be obtained by using a single Minecraft:dragon's breath in slot 3, by the craft remainder.

Note: The down face not give access to slot 4, since the hoppers only try to take items from the down face, they should never take items from slot 4.

VaultConfig

VaultConfig()

Define the default Template:Cd in the Template:Cd in Template:Cd Minecraft:block entity as trial key. So the trial key can open Minecraft:vaults whose Template:Cd has not been changed.

However, it is possible to change the Template:Cd using commands, this key property only applies to default vaults.

AgeableMob

canUseGoldenDandelion(Template:Tooltip)

Returns true when the following occur simultaneously:

• The item in hand is a golden dandelion
• Template:Cd is true
• Template:Cd is zero
• The mob is not in the Template:Tag link tag

This method is used twice:

• Template:Jcp.Template:Cd — The Template:Cd parameter actually checks if the ageable mob is a baby (Template:Cd < 0 and can be a baby), and the Template:Cd is Template:Cd. If it returns true, sets age locked and returns Template:Cd. Otherwise, it returns Template:Cd (via the super method). Most ageable mobs do not have this interaction directly, as the method has many overrides; however, at some point, it is activated via the super method.

• Template:Jcp.Template:Cd — The Template:Cd parameter is always true, and the Template:Cd is the same as above. Before testing whether the golden dandelion works, try feeding the tadpole (feed it when the item is in the Template:Tag link tag and the tadpole is not age-locked). If it doesn't feed, try using the golden dandelion; if successful, set it to age-locked and return it to the Template:Cd. Otherwise, try to catch the tadpole in the bucket.

When age locked is set, it occurs in order:

1. Invert the value of the NBT tag Template:Cd;
2. Sets the Template:Cd to 0 for tadpoles, −48000 for sniffers, and −24000 for other mobs;
3. Set Template:Cd to 40;
4. Consume one item from the player's hand.
5. If age is locked:

• Set persistence required
• Paly sound Template:Cd (Template:Sound)

Otherwise

• Paly sound Template:Cd (Template:Sound)

Entity

interact(Template:Tooltip)

Attempt to interact with the entity in the following order. If one attempt fails, try the next.

1. The player attempts to attach entities currently leashed to them onto the entity being interacted with. This interaction does not depend on the item held in hand. If at least one entity is successfully leashed, the interaction returns success (and concludes).

2. If the item held is shears, attempt to remove the leashes from the entity being interacted with.

• This attempts to remove both the leash securing the interacted entity and any leashes from nearby entities (within a 32×32×32 cuboid centered on the interacted entity) that are attached to the interacted entity.
• When a leash is removed, it is dropped at the position of the leashed entity.

If at least one leash is dropped:

• Produce the game event Template:Cd Minecraft:game event.
• The Template:Cd sound plays.
• The shears take one of damage.
• The interaction returns success.

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 player is holding shears
• The player is not [[Minecraft:crouching|Template:Control]]
• If the entity is a wolf, the player is its owner; otherwise, the entity is not being ridden
• At least one item in the entity's equipment slots has Template:DCL set to true and, unless the player is in Creative mode, does not have an enchantment with Template:Cd effect components (e.g., Minecraft:Curse of Binding in vanilla)

In this case, a piece of equipment can be removed:

• The shears take one of damage
• Produce the Minecraft:game event Template:Cd
• Drop the equipment
• Triggered [[Minecraft:Advancement_definition#minecraft:player_sheared_equipment|Template:Cd]] advancement trigger
• 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.

4. wip

Villager

mobInteract(Template:Tooltip)

When interacting with a Minecraft:villager, if the interaction use a villager spawn egg, if the villager is sleeping, currently trading, or is not alive, the interaction returns the result of the supermethod (see Template:Slink). Note that if the item is the villager spawn egg, it always returns pass.

This prevents starting a Minecraft:trade or Template:Cd (for babies and villagers without trades), and returns success.

However, if the supermethod returns pass, it try to equip the item on the villager, by the Template:DCL component, via the Template:Jicp.Template:Cd method.

The addition of the villager spawn egg check was likely intended to ensure the egg spawns a baby villager instead starting a trade; however, in the interaction check order, the attempt to spawn a baby villager with a spawn egg occurs before this method. Consequently, it is possible to spawn a baby villager using any spawn egg that possesses the Template:DCL component with the ID Template:Cd. This property also allows the villager spawn egg to be equipped, provided it does not have the Template:DCL component with the ID Template:Cd (which requires removing the default component), which does not occur with other items.<ref>Template:Bug</ref>

Old article stub