This is a list of various data structures that the game uses for multiple different advancement triggers. These data structures are not advancements on their own; rather, they are bits of information that are copied into an advancement trigger's conditions. For example, the minecraft:slept_in_bed, minecraft:location, and minecraft:nether_travel advancement triggers all use the same shared "location" data structure within its conditions object.
Since a lot of triggers share the same data structures, separating them into this list greatly reduces the character length of the guide. Each trigger that makes use of a shared data structure will still have an example usage of that data structure, while this list will provide all possible options of that structure.
- Example
- Range
- Location object
- Distance object
- Status effects object
- Item object
- Entity object
- Block object
- Damage object
- Damage flags object
- Death object
On the minecraft:entity_hurt_player trigger page, the first thing listed is what the advancement does when no options are specified. Below that is a list of "Conditions", with each condition stating when it's making use of one of the data structures listed here (in this case, it uses the shared damage data structure). Below that is an example of that data structure being used.
A large number of advancement features make use of a "range" object, which is a comparison of the incoming number (such as the number of occupied inventory slots) to the specified range of numbers.
To check for an exact value, simply declare the range as a number. The following checks if the compared value is exactly 3.
"occupied": 3To check between two values, the range must be specified as an object containing min and max numbers. The following checks if the compared value is between 1 and 3.
"occupied": {
"min": 1,
"max": 3
}You can alternatively specify only the minmum or only the maximum, which will ignore a check for the opposing limiter. For example, the following checks if there are at least 3 occupied slots. The player's inventory could have 7 occupied slots and they will still match.
"occupied": {
"min": 3
}Versus the opposite, where the following checks if there are at most 2 occupied slots. The player's inventory could have 0 occupied slots and they will still match.
"occupied": {
"max": 2
}A location object contains a small amount of data to specify an origin, biome, or generated structure. All options are available anywhere that this location object is used.
The position object contains x, y, and z ranges to check the global position of the player in the world. You do not need to specify all of the axes. For example, the following checks if the player is at Y62 or lower.
"location_object": {
"position": {
"y": {
"max": 62.0
}
}
}The biome string specifies the name ID of the biome that the player must stand within. You can find a list of name IDs for biomes here. The following checks if the player has visited the "minecraft:desert" biome.
"location_object": {
"biome": "minecraft:desert"
}The feature string specifies the name ID of a structure. The player must be standing within the bounding box of that structure to be detected. Accepted values include: "pillager_outpost", "mineshaft", "mansion", "jungle_pyramid", "desert_pyramid", "igloo", "shipwreck", "swamp_hut", "stronghold", "monument", "ocean_ruin", "fortress", "endcity", "buried_treasure", "village".
The following checks if the player is inside an "endcity" structure.
"location_object": {
"feature": "endcity"
}The dimension string specifies the name ID of a dimension to find the player in. Accepted values are "minecraft:overworld", "minecraft:the_nether", and "minecraft:the_end". The following checks if the player is anywhere in the nether.
"location_object": {
"dimension": "minecraft:the_nether"
}The distance object contains information about the distance between the advancement-earning player and an unspecified origin. The origin cannot be directly defined but changes depending on the trigger; see each trigger that uses this for specific information. All options are available anywhere that this location object is used.
The x, y, and z ranges each check if the player is a number of blocks in either direction of the origin in the specified axis. You do not need to specify all of the axes. For example, the following checks if the player is within 40 blocks in either the positive or negative X direction of the origin.
"distance_object": {
"x": {
"max": 40.0
}
}The absolute range checks if the player is within a number of blocks on all axes. You would use this instead of x/y/z if all axes are uniform. The following checks if the player is outside a 5-block range of an origin.
"distance_object": {
"absolute": {
"min": 5.0
}
}The horizontal range checks if the player is within a number of blocks on the X and Z axes, ignoring the Y axis. The following checks if the player is withn a 10-block range of an origin, but only on the X and Z axes.
"distance_object": {
"horizontal": {
"max": 10.0
}
}A status effect object contains nested objects, whose key names reflect status effect IDS. All options are available anywhere that this item object is used.
The amplifier range checks the amplifier of the specified effect. The following checks if the amplifier is 10 or higher.
"effects_object": {
"minecraft:levitation": {
"amplifier": {
"min": 10
}
}
}The duration range checks the remaining duration in ticks of the specified effect. The following checks if the effect has at least 15 seconds (300 ticks) remaining.
"effects_object": {
"minecraft:levitation": {
"duration": {
"max": 300
}
}
}The ambient boolean checks if the effect has the "ambient" flag set to true.
"effects_object": {
"minecraft:levitation": {
"ambient": true
}
}The visible boolean checks if the effect has the "visible" flag set to true.
"effects_object": {
"minecraft:levitation": {
"visible": true
}
}An item object contains a handful of data to compare to an incoming item stack. All options are available anywhere that this item object is used.
You cannot use both item and tag together.
The item string specifies a base item ID to compare the item to. The following checks if the item is redstone.
"item_object": {
"item": "minecraft:redstone"
}The tag string instead specifies the resource location to an ID group, minus the designating # character. These groups are a list of item IDs that the incoming item can match any one of. Default groups for items include: "#minecraft:wool", "#minecraft:planks", "#minecraft:stone_bricks", "#minecraft:wooden_buttons", "#minecraft:buttons", "#minecraft:carpets", "#minecraft:wooden_doors", "#minecraft:doors", "#minecraft:saplings", and "#minecraft:logs". Adding custom groups requires the use of data packs. The following checks if the item matches any of the IDs in the "minecraft:doors" group (which checks both the "#minecraft:wooden_doors" group as well as the "minecraft:iron_door" item ID).
"item_object": {
"tag": "minecraft:doors"
}The durability range specifies the remaining durability of an item. The following checks if the item has 400 or more durability remaining.
"item_object": {
"durability": {
"min": 400
}
}The count range specifies the number of items in a single stack. This cannot be used to check the number of items across the inventory as a whole. The following checks if the item has 16 or more in its stack.
"item_object": {
"count": {
"min": 16
}
}The potion string specifies the default brewed potion ID that the item must contain, specified in the Potion NBT string. The wiki contains a list of those IDs here.
"item_object": {
"potion": "minecraft:invisibility"
}The item does not have to be a potion. As long as the item has the Potion NBT string, it will match:
/give @p minecraft:stone 1 0 {Potion:"minecraft:invisibility"}
The enchantments list checks the item's enchantments (whether in the ench NBT list for all items excluding books, or the StoredEnchantments NBT list for only books) for matching data. If only an empty object is specified, the player's inventory is checked for any enchanted items.
"item_object": {
"enchantments": [
{
}
]
}The enchantment string will specify the enchantment ID to look for. The following checks the item for the Sharpness enchantment.
"item_object": {
"enchantments": [
{
"enchantment": "minecraft:sharpness"
}
]
}The levels range will specify the range of levels to find for an enchantment. The following checks if the player has any enchantments level 3 or higher.
"item_object": {
"enchantments": [
{
"levels": {
"min": 3
}
}
]
}And combining it with an ID, the following checks if the player has Sharpness 5.
"item_object": {
"enchantments": [
{
"enchantment": "minecraft:sharpness",
"levels": 5
}
]
}The nbt string compares the raw NBT input to the item's NBT data. This raw data starts within the tag compound of the item format and must be surrounded by curly brackets. The following checks if the item has a specific display name.
"item_object": {
"nbt": "{display:{Name:\"Test\"}}"
}An entity object contains a handful of data to compare to an incoming entity. All options are available anywhere that this entity object is used.
The type string specifies the entity ID to match against. For example, the following checks if the incoming entity is a creeper.
"entity_object": {
"type": "minecraft:creeper"
}The distance distance object specifies the distance between the advancement-earning player and an entity's origin. The following checks if the player is within 10 blocks of the entity.
"entity_object": {
"distance": {
"absolute": {
"max": 10
}
}
}The location location object checks data concerning the entity's location in the world. The following checks if the entity is in the desert biome.
"entity_object": {
"location": {
"biome": "minecraft:desert"
}
}The effects status effects object checks data concerning the entity's status effects. The following checks if the entity has Speed 2.
"entity_object": {
"effects": {
"minecraft:speed": {
"amplifier": 2
}
}
}The nbt string compares the raw NBT input to the entity's NBT data. This raw data starts within the root of the entity format and must be surrounded by curly brackets. If the entity being checked is a player, the SelectedItem compound (containing the player's mainhand item) will be appended to the player's NBT before comparing to the provided input. The following checks if the entity has a specific tag within its Tags list.
"entity_object": {
"nbt": "{Tags:[\"findme\"]}"
}The flags object contains various boolean fields that further describe the entity. The following includes a list of all acceptable flags.
"entity_object": {
"flags": {
"is_on_fire": false,
"is_sneaking": false,
"is_sprinting": false,
"is_swimming": false,
"is_baby": false
}
}The equipment object contains nested objects that each make use of the shared item object to describe the armor and weapons that the entity is wearing.
"entity_object": {
"equipment": {
"head": {
"item": "minecraft:stone"
},
"chest": {
"item": "minecraft:stone"
},
"legs": {
"item": "minecraft:stone"
},
"feet": {
"item": "minecraft:stone"
},
"mainhand": {
"item": "minecraft:stone"
},
"offhand": {
"item": "minecraft:stone"
}
}
}The catType string takes in a resource location pointing to the texture file of the corresponding cat type. For example, the following checks if the cat is a tabby.
"entity_object": {
"catType": "minecraft:textures/entity/cat/tabby.png"
}A block object contains a handful of data to compare to an incoming block. All options are available anywhere that this entity object is used.
The block string specifies a base block ID to detect the player in. For example, the following checks if the block has the base ID of "minecraft:tallgrass" (includes grass, fern, and double tallgrass).
"block_object": {
"block": "minecraft:tallgrass"
}The state object contains a list of custom keys, much like criteria does. The names for these keys will correspond to the blockstate name you want to detect, and the value corresponds to possible values for that blockstate. For "minecraft:tallgrass", the type blockstate specifies which of the tallgrass blocks it is. The block string must be specified to use this condition. The following checks if the tallgrass is a fern.
"block_object": {
"block": "minecraft:tallgrass",
"state": {
"type": "fern"
}
}A damage object contains a large amount of information about the incoming or outgoing damage. All options are available anywhere that this damage object is used.
A range checking the raw incoming damage before damage reduction. For example, the following checks the damage of an un-owned arrow (via /summon) before that damage was either reduced or blocked with a shield entirely.
"damage_object": {
"dealt": {
"min": 4.0
},
"source_entity": {
"type": "minecraft:arrow"
}
}A range checking the incoming damage after damage reduction. For example, the following checks if the resulting damage after reductions was at least 5.0.
"damage_object": {
"taken": {
"min": 5.0
}
}Checks if the incoming damage was successfully blocked, provided that the damage_flags_object.bypasses_armor ("unblockable") flag isn't true. The following checks if the player failed to block a skeleton's attack (either by an arrow or melee weapon).
"damage_object": {
"blocked": false,
"source_entity": {
"type": "minecraft:skeleton"
}
}A damage flags object that checks various flags about the damage. The following checks if the damage was a projectile caused by a skeleton (though does not necessarily mean the direct cause of the damage was an arrow).
"damage_object": {
"type": {
"is_projectile": true
},
"source_entity": {
"type": "minecraft:skeleton"
}
}An enity object that checks information about either the entity hit or the entity dealing the damage. Note that for players being the source entity, the nested type string can essentially only be "minecraft:player". The following checks if a skeleton was at least 10 blocks away when it hit the player.
"damage_object": {
"source_entity": {
"type": "minecraft:skeleton",
"distance": {
"min": 10
}
}
}A damage flags object checks different flags concerning the incoming or outgoing damage. All options are available anywhere that this damage flags object is used.
Checks the "unblockable" flag for the incoming damage. This is true for: fire, suffocation (blocks & world border), entity cramming, drowning, starving, falling, flying into a wall, void (the Void & /kill), health recalcuation, magic damage, and wither effect damage. The following checks if the damage is caused by any damage that cannot be blocked.
"damage_object": {
"bypasses_armor": true
}Checks if the damage source can inflict damage on creative mode players. This is true for: void damage. The following checks if the incoming damage is not caused by the Void or /kill.
"damage_object": {
"bypasses_invulnerability": false
}Checks the "damageIsAbsolute" flag for the incoming damage. This is true for: starvation. The following checks if the player is taking starvation damage.
"damage_object": {
"bypasses_magic": true
}Checks the "explosion" flag for the incoming damage. This is true for: creepers, ender crystals, TNT, Minecart TNT, ghast fireballs, beds, the wither, and wither skulls. The following checks if the "explosion" flag is true.
"damage_object": {
"is_explosion": true
}Checks the "fire" flag for the incoming damage. This is true for: standing in a fire block, being on fire, standing on magma, standing in lava, ghast fireballs, and blaze fireballs. The following checks if the player is not taking damage from fire sources.
"damage_object": {
"is_fire": false
}Checks the "magicDamage" flag for the incoming damage. This is true for: thorns, Instant Damage effect, Poison effect, part of Guardian laser damage, evocation fangs, and un-owned wither skulls (via /summon). The following checks if the incoming damage is flagged as magic damage.
"damage": {
"is_magic": true
}Checks the "projectile" flag for the incoming damage. This is true for: arrows, ghast fireballs, blaze fireballs, enderpearls, eggs, snowballs, shulker bullets, and llama spit. The following checks if the incoming damage is specifically not a projectile.
"damage": {
"is_projectile": false
}Checks the "lightning" flag for the incoming damage. This is true for: lightning bolts. The following checks if the incoming damage is specifically not from a lightning bolt.
"damage": {
"is_lightning": false
}An enity object that specifies the "owner" of the damage. For example, if the player was hit by an arrow shot by a skeleton, the skeleton would be the "source entity". The damage object already makes use of this check, so it is pointless to specify a source entity twice. This particular check is still useful for triggers that only use a damage flags object rather than a damage object.
"damage": {
"source_entity": {
"type": "minecraft:skeleton"
}
}An enity object that specifies the direct cause of the damage. For example, if the player was hit by an arrow shot by a skeleton, the arrow would be the "direct entity". The following ensures the player was hit by an arrow shot by a skeleton.
"damage": {
"direct_entity": {
"type": "minecraft:arrow"
},
"source_entity": {
"type": "minecraft:skeleton"
}
}The death object contains information about both the killer/killed entity (changing depending on the trigger) and the killing blow. All options are available anywhere that this death object is used.
An enity object that will either describe the entity that was killed or the killer itself, depending on the trigger being used; see each trigger that uses this for specific information. To be clear: this does not always describe the entity that died. The following checks if the killed entity or killer was a creeper.
"death_object": {
"entity": {
"type": "minecraft:creeper"
}
}A damage flags object that contains damage flags about the killing blow against the dead entity. Be aware that this is not the damage object, so the options from that object are unavailable. The following checks if the entity had died due to an explosion.
"death_object": {
"killing_blow": {
"is_explosion": true
}
}