Tag

Tags in data packs allow players to group items, blocks, fluids, entity types or functions together using JSON files.

Usage
To utilize block, item, or function tags the JSON files must be placed in a data pack inside the,  ,   or   folder respectively.

Minecraft itself also uses tags. For example, vanilla block tags are used for various block properties, vanilla item tags are used for various item properties, vanilla advancement files and vanilla recipe files, and vanilla entity type tags are used for various mob properties. See section for their usages.

There are no vanilla function tags since there are no vanilla functions, but the game reads from certain function tags under the  namespace.

Block tags
Block tags can be called when testing for block arguments in commands with, which succeeds if the block matches any of the blocks specified in the tag.

Item tags
Item tags can be called when testing for item arguments in commands with  or in recipes and advancements using , which succeeds if the item matches any of the items specified in the tag. They can also be searched in the creative inventory by searching.

Entity type tags
Entity type tags can be called in  target selector argument and loot table conditions with , which checks if the entity's type matches any of the entity types specified in the tag.

Function tags
Function tags can be called in the command with , which runs all the functions specified in the tag in the order of their first appearance in a tag. If a function is referenced multiple times in a tag and its sub-tags, it is run once.

Moreover, functions tagged in the  tag runs every tick at the start of the tick and functions tagged in   runs once at the start of the tick after a server (re)load.

JSON format

 * The root object.
 * Optional. Whether or not contents of this tag should completely replace tag contents from different lower priority data packs with the same namespaced ID. When  the tag's content is appended to the contents of the higher priority data packs, instead. Defaults to.
 * : A list of mix and match of object names and tag names. For tags, recursive reference is possible, but a circular reference causes a loading failure.
 * An object's namespaced ID in the form.
 * : ID of another tag of the same type in the form.
 * : An entry with additional options. (1.16.2+)
 * : A string in one of the string formats above.
 * : Whether or not loading this tag should fail if this entry is not found, true by default (also for the string entries). A tag that fails to load can still be referenced in any data pack and be (re)defined in other data packs. In other words, only the entries in this JSON file is ignored if this entry cannot be found.

Game events
Game event tags are.

History
{{History|||snap=1.17 pre-1|Added the {{cd|geode_invalid_blocks|lava_pool_stone_replacealbe}} block tags. {{History|foot}}
 * Added flowering azaleas and flowering azalea leaves to the {{cd|flowers}} block and item tags.
 * Removed flowering azaleas and flowering azalea leaves from the {{cd|small_flowers}} block and item tags.
 * Added potted azaleas and potted flowering azaleas to the {{cd|flower_pots}} block tag.
 * Added non-waxed oxidized copper variants to the {{cd|needs_stone_tool}} block tag.
 * Removed moss carpet from the {{cd|mineable/axe}} block tag.

Issues
Aliasdaten Tag_(Pack_de_données) タグ Marcação Тег 标签