Minecraft:Identifier

Identifiers (also known as resource locations, namespaced IDs, namespaced identifiers, resource identifiers,<ref>Template:Snap</ref> or namespaced strings<ref>DataFixerUpper/NamespacedStringType.java at 8b5f82ab78b30ff5813b3a7f3906cd3f4f732acf · Mojang/DataFixerUpper – GitHub</ref>) are a way to declare and specify game objects in Minecraft, which can identify built-in and user-defined objects without potential ambiguity or conflicts.

Introduction

Identifiers are used as plain strings to reference Minecraft:blocks, Minecraft:items, entity types, and various other objects in vanilla Minecraft.

A valid identifier has a format of namespace:path, where only certain characters can be used.

Legal characters

Java Edition

The namespace and the path of an identifier should only contain the following symbols:

• 0123456789 Numbers
• abcdefghijklmnopqrstuvwxyz Lowercase letters
• _ Underscore
• - Hyphen/minus
• . Dot

The following characters are illegal in the namespace, but acceptable in the path:

• / Forward slash (directory separator)

The preferred naming convention for either namespace or path is snake_case.

Bedrock Edition

The namespace and the path of a namespaced ID can contain all symbols with the exception of slashes and colons.

The following characters are illegal in the namespace, but acceptable in the path of loot tables and functions.

• / Forward slash (directory separator)

The preferred naming convention for either namespace or path is snake_case.

Conversion to string

An identifier is converted to a string by concatenating its namespace with a : (colon) and its path.

Examples:

Namespace	Path	String representation
minecraft	diamond	minecraft:diamond
foo	bar.baz	foo:bar.baz
minecraftwiki	commands/minecraft_wiki	minecraftwiki:commands/minecraft_wiki

Conversion from string

All identifiers can be converted to strings; however, not all strings can be converted to identifiers.

For a string to be converted, it must follow these restrictions:

• The string may have at most one : (colon) character
• The rest of the string must fulfill the requirement for legal characters. This includes disallowing / (forward slash) characters before the :, if a : is present

When the : is present, the part of the string before the : becomes the namespace, and the part of the string after the : becomes the path.

in Template:Editions, and in some cases in Template:Editions, when the : is absent, minecraft becomes the namespace and the whole string becomes the path.

It is recommended to always include a : in the string format of identifiers.

Examples

String	Resolved namespace	Resolved path	What the game converts it back to
bar:code	bar	code	bar:code
minecraft:zombie	minecraft	zombie	minecraft:zombie
diamond	minecraftTemplate:Only NoneTemplate:Only	diamond	minecraft:diamondTemplate:Only diamondTemplate:Only
:dirt	minecraft	dirt	minecraft:dirt<needs testing in Bedrock Edition></needs testing in Bedrock Edition>
minecraft:	minecraft	None	minecraft:<needs testing in Bedrock Edition></needs testing in Bedrock Edition>
:	minecraft	None	minecraft:<needs testing in Bedrock Edition></needs testing in Bedrock Edition>
Empty String	minecraft	None	minecraft:<needs testing in Bedrock Edition></needs testing in Bedrock Edition>
foo/bar:coal	Invalid character /
minecraft/villager	minecraftTemplate:Only NoneTemplate:Only	minecraft/villager	minecraft:minecraft/villagerTemplate:Only minecraft/villagerTemplate:Only
mymap:schrödingers_var	mymap	Invalid character öTemplate:Only schrödingers_varTemplate:Only	mymap:schrödingers_varTemplate:Only
custom_pack:Capital	custom_pack	Invalid character CTemplate:Only CapitalTemplate:Only	custom_pack:CapitalTemplate:Only

Java Edition usage

1. REDIRECT Template:Work in progress

in Template:Editions, identifiers act mainly as main keys of objects in registries or file paths of contents in data packs and resource packs. Some non-customizable contents also use identifiers to identify them.

Registries and registry objects

All registries and objects therein have identifiers to represent them. At the root of all registries is a registry with the identifier of

1. REDIRECT Template:Code

Template:Redr into which all other registries are registered. Most registries are intended only for use internally by the game and by extension by mods, but some dynamic registries can have content added to them through data packs, marked in the list below with an asterisk (*).

• Template:File: Root registry.
  • Template:File: Attributes.
  • Template:File: Blocks.
  • Template:File: Block entity types.
  • Template:File: Chunk status.
  • Template:File: Command argument types.
  • Template:File*: Dimensions and level stems.
  • Template:File*: Dimension types.
  • Template:File*: Enchantments.
  • Template:File: Entity types.
  • Template:File: Fluids.
  • Template:File: Game events.
  • Template:File: Position source types (used by game events).
  • Template:File: Items.
  • Template:File*: Menu types.
  • Template:File: Mob effects.
  • Template:File: Particle types.
  • Template:File: Potions.
  • Template:File: Recipe serializers.
  • Template:File: Recipe types.
  • Template:File: Sound events.
  • Template:File: Statistics types.
  • Template:File: Custom Statistics.
  • Template:File: World clocks.
  • Template:File Timelines for world clocks.
  • Template:File Entity data registries:
    • Template:File: Entity schedule activitys.
    • Template:File: Entity memory module types.
    • Template:File: Entity schedules.
    • Template:File: Entity AI sensor types.
    • Template:File*: Painting motives.
    • Template:File: Villager professions.
    • Template:File: Villager types.
    • Template:File: Villager trade definition.
    • Template:File: Poi types.
  • Template:File Loot table serializers:
    • Template:File: Loot condition types.
    • Template:File: Loot function types.
    • Template:File: Loot nbt provider types.
    • Template:File: Loot number provider types.
    • Template:File: Loot pool entry types.
    • Template:File: Loot score provider types.
  • Template:File JSON file value providers:
    • Template:File: Float provider types.
    • Template:File: Int provider types.
    • Template:File: Height provider types.
  • Template:File World generator registries:
    • Template:File: Block predicate types.
    • Template:File: Structure feature rule test types.
    • Template:File: Structure feature position rule test types.
    • Template:File: World carvers.
    • Template:File*: Configured world carvers.
    • Template:File: Features.
    • Template:File*: Configured features.
    • Template:File: Structure sets.
    • Template:File: Structure processor types.
    • Template:File*: Structure processor lists.
    • Template:File: Structure pool element types.
    • Template:File*: Structure template pools.
    • Template:File: Structure piece types.
    • Template:File: Structure features.
    • Template:File*: Configured structure features.
    • Template:File: Structure placement types.
    • Template:File: Placement modifier types.
    • Template:File*: Placed features.
    • Template:File*: Biomes.
    • Template:File: Biome sources.
    • Template:File*: Normal noise.
    • Template:File*: Noise generator settings.
    • Template:File: Density functions.
    • Template:File: Density function types.
    • Template:File: World presets.
    • Template:File: Flat world generator presets.
    • Template:File: Chunk generators.
    • Template:File: Surface condition sources.
    • Template:File: Surface rule sources.
    • Template:File: Block state provider types.
    • Template:File: Foliage placer types.
    • Template:File: Trunk placer types.
    • Template:File: Tree decorator types.
    • Template:File: Feature size types.

Pack contents

Identifiers are also used to represent file paths in data packs or resource packs.

Data pack

• Tags
• Advancements
• Recipes
• Predicates
• Loot tables
• Item modifier
• Functions
• Structure files
• Dimensions
• Dimension types
• World generator contents
  • Biomes
  • Configured carvers
  • Configured features
  • Configured structure features
  • Placed features
  • Structures
  • Structure sets
  • Processor lists
  • Template pools
  • Noise
  • Noise generator settings
  • Density functions
  • Flat level generator presets
  • World presets

Resource pack

• Block state model definitions
• Models
• Textures
• Sounds
• Fonts
• Font resource files
• Particles
• Shaders

Locating contents in packs

Given that objects in resource packs and data packs are files, the identifiers are constructed from their path relative to the

1. REDIRECT Template:Code

Template:Redr or

1. REDIRECT Template:Code

Template:Redr folder.

Though the locations vary by object type and the pack type the object type belongs to, there is a pattern to follow. In general, the location is in the fashion of pack_type/namespace/object_type/name.suffix, where all the / (forward slash) symbol (may be part of object_type or name) is replaced by operating system-dependent directory separator.

Given the type of content we want to locate, we can find out the corresponding

1. REDIRECT Template:Code

Template:Redr,

1. REDIRECT Template:Code

Template:Redr, and

1. REDIRECT Template:Code

Template:Redr. Then, we can substitute in and find out the final file location of the content.

Examples

Identifier	Content Type	REDIRECT Template:Code Template:Redr !! REDIRECT Template:Code Template:Redr !! REDIRECT Template:Code Template:Redr !! Final Location
REDIRECT Template:Code Template:Redr || Texture || REDIRECT Template:Code Template:Redr || REDIRECT Template:Code Template:Redr || REDIRECT Template:Code Template:Redr || REDIRECT Template:Code
REDIRECT Template:Code Template:Redr || Function || REDIRECT Template:Code Template:Redr || REDIRECT Template:Code Template:Redr || REDIRECT Template:Code Template:Redr || REDIRECT Template:Code
REDIRECT Template:Code Template:Redr (same as REDIRECT Template:Code Template:Redr) || Model || REDIRECT Template:Code Template:Redr || REDIRECT Template:Code Template:Redr || REDIRECT Template:Code Template:Redr || REDIRECT Template:Code
REDIRECT Template:Code Template:Redr (same as REDIRECT Template:Code Template:Redr) || Function Tag || REDIRECT Template:Code Template:Redr || REDIRECT Template:Code Template:Redr || REDIRECT Template:Code Template:Redr || REDIRECT Template:Code
REDIRECT Template:Code Template:Redr || Advancement || REDIRECT Template:Code Template:Redr || REDIRECT Template:Code Template:Redr || REDIRECT Template:Code Template:Redr || REDIRECT Template:Code

Registered pack contents

A registried pack content refers to pack content that is registered into a registry when the pack is loaded. For a registried pack content, its identifier works as both main key of registry entry and path of its resource file.

List of registered pack contents

Other contents

Customizable contents

• Boss bars
• Command storages

Hardcoded contents

• Cat types for predicates (e.g. textures/entity/cat/tabby.png, textures/entity/cat/jellie.png)
• Criteria triggers
• Item properties (i.e. item predicates in models. e.g. angle, custom_model_data)
• Loot context param sets (i.e. types of loot table. e.g. barter, generic)
• Unaccessible contents:
  • Suggestion providers for autocompletion of commands (e.g. summonable_entities, all_recipes)
  • Entity models
  • Loot context params (e.g. this_entity, origin, tool)

Bedrock Edition usage

Unlike Java Edition, where there is a unified standard and handling methods of them, namespaced identifiers are usually treated as normal strings in Bedrock Edition. Moreover, some objects are identified based on their path (e.g. the identifier for recipes and trades) rather than what was defined in their file. In these cases, it is recommended that a folder named after the namespace is parented before the file at hand.<ref name="cooperative">Template:Citation</ref>

The following is a list of all places that use namespaced identifiers:

Built-in contents

• Blocks
• Block traits
• Block entities
• Items
• Entities
• Status effects
• Dimensions
• Biomes
• Structures
• Features
• Entity attributes
• Item NBT components
• Item components
• Block components
• Entity components
• JSON schemas
• GameTest script-enabled components

Registried add-on entries

A registried add-on entry refers to any add-on content that is registered with an identifier declared within the content's file definition. Custom content under these types are able to be created.

Here is a list of registried add-on entries whose identifiers are namespaced.

Behavior pack contents

• Blocks
• Block states
• Entities
• Entity events
• Items
• Spawn rules
• Biomes
• Features
• Feature rules
• Recipes
• Structures
• GameTests
• Dialog scenes
• Spawn groups
• Structure sets
• Template pools
• Processor lists
• Catalog groups

Resource pack contents

• Attachables
• Cameras
• Entity client definitions
• Particle effects
• Biome client definitions
• Fog settings
• Lighting settings
• Atmosphere settings
• Color grading settings
• Water effect settings

Some custom fields in add-on files can also be namespaced, such as custom block properties and entity component groups, which aren't listed here.

Others

• Structures saved from a structure block

Script-registered entries

Some content may also be registered within the scripts of behavior packs. These are read as the world is generating.

• Block components
• Item components
• Commands

Namespaces

"

This isn't a new concept, but I thought I should reiterate what a "namespace" is. Most things in the game has a namespace, so that if we add

1. REDIRECT Template:Code

Template:Redr and a mod (or map, or whatever) adds

1. REDIRECT Template:Code

Template:Redr, they're both different

1. REDIRECT Template:Code

Template:Redrs. Whenever you're asked to name something, for example a loot table, you're expected to also provide what namespace that thing comes from. If you don't specify the namespace, we default to

1. REDIRECT Template:Code

Template:Redr. This means that

1. REDIRECT Template:Code

Template:Redr and

1. REDIRECT Template:Code

Template:Redr are the same thing.

A namespace is a domain for content. It is to prevent potential content conflicts or unintentional overrides of objects of the same name.

For example, two data packs add two minigame mechanisms to Minecraft; both have a function named

1. REDIRECT Template:Code

Template:Redr. Without namespaces, these two functions would clash and the minigames would be broken. When they have different namespaces of

1. REDIRECT Template:Code

Template:Redr and

1. REDIRECT Template:Code

Template:Redr, the functions would become

1. REDIRECT Template:Code

Template:Redr and

1. REDIRECT Template:Code

Template:Redr, which no longer conflict.

===

1. REDIRECT Template:Code

Template:Redr namespace === Minecraft reserves the

1. REDIRECT Template:Code

Template:Redr namespace. When a namespace is not specified, an identifier falls back to

1. REDIRECT Template:Code

Template:RedrTemplate:Only. As a result, the

1. REDIRECT Template:Code

Template:Redr namespace should only be used by content creators when the content needs to overwrite or modify existing Minecraft data, such as adding a function to the

1. REDIRECT Template:Code

Template:Redr function tag.

Custom namespace

The namespace should be distinct for different projects or content creations (e.g. a data pack, a resource pack, a mod, backing data/resource packs for a custom map, etc.)

To prevent potential clashes, it is recommended that the namespace should be as specific as possible:

• Avoid alphabet soups. For example, a project named "nuclear craft" should not use the namespace

1. REDIRECT Template:Code

Template:Redr, as this is too ambiguous.

• Avoid words that are too vague.

1. REDIRECT Template:Code

Template:Redr would not be informative to look up as well, but

1. REDIRECT Template:Code

Template:Redr would be much better.

• For Minecraft:add-ons, use a shortened creator name followed by the name of the project in a format like

1. REDIRECT Template:Code

Template:Redr.<ref name="cooperative"/>

In either case, these poorly chosen namespaces reduce the exposure of a project and bring difficulties for debugging when there are multiple content creations applied to the game.

Other built-in namespaces

in Template:Editions, the vanilla Minecraft resource pack declares Realms-oriented language files in the

1. REDIRECT Template:Code

Template:Redr namespace (located at assets/realms/lang/.json) and game-related language files in the

1. REDIRECT Template:Code

Template:Redr namespace, even though translation keys are not identifiers. The realms jar itself also declares its en_us.json language file and its various textures in the

1. REDIRECT Template:Code

Template:Redr namespace.

In the IDs of command argument types, a

1. REDIRECT Template:Code

Template:Redr namespace also appears for command argument types that are native to Brigadier.

in Template:Editions, the internal resource and behavior packs for Minecraft:Bedrock Editor contain some entities and items namespaced with editor.

History

See also

• Java Edition data values
• Minecraft:Bedrock Edition data values
• Resource pack
• Data pack
• Minecraft:Add-on

References

<references group="">

 </references>

External links

• Namespaces, as explained in Template:Snap.

Navigation

Concepts Template:BlockLink Template:EnvLink Template:EffectLink Template:Nbt Loot context Template:EntityLink Template:BlockLink Template:File Identifier Template:BlockLink Template:EnvLink Template:ItemLink Template:ItemLink Template:EnvLink Template:BlockLink General format Template:EnvLink Template:LegacyBlockLink Remake Template:EntityLink Template:BlockLink Template:EnvLink Template:BlockLink Template:EnvLink Template:ItemLink Template:Nbt NBT format Template:EffectLink Template:ItemLink § Formatting codes Template:FileLink Template:FileLink Template:BlockLink Template:EnvLink World Template:EnvLink Template:EnvLink Anomalous Template:EnvLink Legacy Template:EnvLink Level format Template:BlockLink Template:EnvLink Template:EntityLink Template:BlockLink Template:EntityLink Template:BlockLink Template:EnvLink Legacy Template:LegacyBlockLink Classic server protocol Template:EntityLink Template:EnvLink Template:LegacyItemLink Template:ItemLink Template:FileLink Template:EnvLink Template:EnvLink .minecraft Template:File client.jar Template:EnvLink Template:ItemLink Template:BlockLink Template:Blocklink Template:FileLink Template:EnvLink Template:ItemLink Template:FileLink Tools Template:Keys Debug screen hotkey renderer Template:FileLink Template:BlockLink Template:FileLink Template:BlockLink Sound Template:BlockLink Template:EnvLink Template:EnvLink Commands Brigadier Template:BlockLink All commands Launching Mojang API Template:FileLink Template:FileLink Legacy Legacy Minecraft authentication Yggdrasil Protocol Template:EnvLink Template:ItemLink Data types Template:BlockLink Server Template:File server.jar Template:BlockLink Template:BlockLink Template:BlockLink Operator list Protocols Query RCON Server Management Protocol Legacy al_version Template:EnvLink

Components Template:Mono Template:EnvLink Template:ItemLink Template:BlockLink Template:BlockLink Template:ItemLink Template:BlockLink Template:BlockLink Template:EffectLink Template:EnvLink Template:ItemLink Template:BlockLink Template:ItemLink Template:BlockLink Template:ItemLink Template:BlockLink Template:BlockLink Template:EntityLink Template:ItemLink Template:ItemLink Template:ItemLink Template:ItemLink Template:EntityLink Trade set World Clock Template:EntityLinkTemplate:Upcoming Tag Template:BlockLink Template:EnvLink Template:BlockLink Template:ItemLink Template:EnvLink Template:BlockLink Template:BiomeLink Template:EnvLink Template:EnvLink Template:EnvLink Template:BlockLink Template:ItemLink Template:BlockLink Template:ItemLink Template:Healthbar Damage type Template:ItemLink Template:ItemLink Template:ItemLink Template:ItemLink Template:EntityLink Template:FileLink GameTest Template:BlockLink Template:BlockLink World generation Dimension Template:EnvLink Template:EnvLink Template:EnvLink Template:EnvLink Template:FileLink Template:EnvLink Template:EnvLink Environment attribute Noise settings Template:EnvLink Template:EnvLink Noises Template:EnvLink Structures Template:EnvLink Template:BlockLink Template:BlockLink Template:EnvLink Removed Template:ItemLink Data packs Template:BlockLink Template:ItemLink Tutorials Template:EnvLink Template:FileLink Optimizing Template:BlockLink Repairing a world corrupted by a data pack Content Template:ItemLink Template:ItemLink Template:ItemLink World generation Template:EnvLink Template:EnvLink

Components Template:Mono Template:EnvLink Template:EnvLink Template:EntityLink Template:BlockLink Template:EnvLink Template:EnvLink (sounds.json) Shaders Template:EnvLink Template:ItemLink Aa Fonts Template:BlockLink Template:File Texts Template:FileLink regional_compliancies.json Template:ItemLink Debug Missing font character Template:BlockLink Template:BlockLink Tools Slicer Legacy Texture Ender Unstitcher Tutorials Template:FileLink Template:FileLink Template:EnvLink Template:EnvLink

Editions	Merged Template:Edition Template:Edition Ports to consoles Template:Wikipedia Template:Wikipedia Template:Wikipedia Template:Wikipedia Template:Wikipedia Discontinued Template:Edition Template:Edition Template:Edition
Development	Version history Template:LegacyBlockLink Template:EntityLink Template:FileLink Template:FileLink Template:EnvLink Template:ItemLink Template:BlockLink Template:InvLink Template:EntityLink Template:FileLink Template:EntityLink
Technical	Template:EffectLink Template:FileLink Template:FileLink Template:File com.mojang Template:FileLink Template:File Installation files Template:FileLink Template:FileLink Template:FileLink Template:FileLink Template:BlockLink Template:File Identifier Template:FileLink Template:ItemLink Template:EnvLink Template:EnvLink Anomalous Template:ItemLink Template:EnvLink § Formatting codes Simulation distance Template:BlockLink Template:FileLink Template:FileLink Template:EnvLink Template:FileLink Template:EntityLink Template:BlockLink Development resources Template:Nbt NBT format Template:Nbt Level format Template:EnvLink Protocol Template:EnvLink RakNet Creator Template:File Official documentation Template:FileLink Template:EntityLink Template:File File extensions Template:FileLink Add-ons Template:ItemLink Template:EnvLink Template:EnvLink Template:EnvLink Template:EnvLink Template:FileLink Template:EnvLink Template:EnvLink Template:BiomeLink Template:EnvLink Family Spawn event Template:ItemLink Template:BlockLink Template:EnvLink Template:BiomeLink Template:EnvLink Template:BlockLink Template:BlockLink Template:BlockLink Template:BlockLink manifest.json Template:EnvLink Template:Nbt Molang Template:BlockLink
Multiplayer	Template:FileLink Featured servers Event servers Server list Template:FileLink Template:FileLink Template:FileLink Template:FileLink
Exclusive features	Template:FileLink Template:FileLink Template:FileLink Template:FileLink Template:FileLink Template:EnvLink Template:EnvLink Template:ItemLink Template:FileLink Template:FileLink Template:EnvLink Template:EnvLink Template:EnvLink Template:PersonaLink Template:EnvLink Loading tips Template:FileLink Ray Tracing Template:BiomeLink Template:EnvLink Blocks Template:BlockLink Template:BlockLink Mobs Template:EntityLink Template:EntityLink Effects Template:EffectLink Unused Template:BlockLink Template:BlockLink Template:BlockLink Template:BlockLink Template:BlockLink Template:BlockLink Template:BlockLink Template:BlockLink Template:BlockLink Template:BlockLink Template:BlockLink Template:BlockLink Template:EntityLink Template:EntityLink Template:BiomeLink Template:EnvLink
Removed	Template:BlockLink Template:EnvLink Template:EnvLink Template:FileLink Pocket Edition protocol Legacy

de:Namensraum es:Ubicación de recurso fr:Identifiant ja:識別子 ko:식별자 pt:Localização de recurso ru:Пространство имён идентификаторов uk:Простір імен ідентифікаторів zh:命名空间ID