Identifier

Identifiers (also known as resource locations, namespaced IDs, namespaced identifiers, resource identifiers,^[1] or namespaced strings^[2]) 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.

Identifiers are used as plain strings to reference blocks, 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.

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.

.. is not a valid namespace.

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.

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

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 Java Edition, and in some cases in Bedrock Edition, 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	minecraft‌[Java Edition only] None‌[Bedrock Edition only]	diamond	minecraft:diamond‌[Java Edition only] diamond‌[Bedrock Edition only]
:dirt	minecraft	dirt	minecraft:dirt[needs testing in Bedrock Edition]
minecraft:	minecraft	None	minecraft:[needs testing in Bedrock Edition]
:	minecraft	None	minecraft:[needs testing in Bedrock Edition]
Empty String	minecraft	None	minecraft:[needs testing in Bedrock Edition]
foo/bar:coal	Invalid character /
minecraft/villager	minecraft‌[Java Edition only] None‌[Bedrock Edition only]	minecraft/villager	minecraft:minecraft/villager‌[Java Edition only] minecraft/villager‌[Bedrock Edition only]
mymap:schrödingers_var	mymap	Invalid character ö‌[Java Edition only] schrödingers_var‌[Bedrock Edition only]	mymap:schrödingers_var‌[Bedrock Edition only]
custom_pack:Capital	custom_pack	Invalid character C‌[Java Edition only] Capital‌[Bedrock Edition only]	custom_pack:Capital‌[Bedrock Edition only]

In Java Edition, 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.

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

Given that objects in resource packs and data packs are files, the identifiers are constructed from their path relative to the data or assets 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 pack_type, object_type, and suffix. Then, we can substitute in and find out the final file location of the content.

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.

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)

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.^[3]

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

• 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

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.

• Structures saved from a structure block

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

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 start. Without namespaces, these two functions would clash and the minigames would be broken. When they have different namespaces of minigame_one and minigame_two, the functions would become minigame_one:start and minigame_two:start, which no longer conflict.

Minecraft reserves the minecraft namespace. When a namespace is not specified, an identifier falls back to minecraft‌^{[Java Edition only]}. As a result, the minecraft 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 minecraft:load function tag.

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 nc, as this is too ambiguous.
• Avoid words that are too vague. battle_royale would not be informative to look up as well, but player_name_battle_royale would be much better.
• For add-ons, use a shortened creator name followed by the name of the project in a format like creatorname_packname.^[3]

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.

In Java Edition, the vanilla Minecraft resource pack declares Realms-oriented language files in the realms namespace (located at assets/realms/lang/.json) and game-related language files in the minecraft 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 realms namespace.

In the IDs of command argument types, a brigadier namespace also appears for command argument types that are native to Brigadier.

In Bedrock Edition, the internal resource and behavior packs for Bedrock Editor contain some entities and items namespaced with editor.

Java Edition
1.6.1			13w21a				Added resource locations alongside the minecraft prefix for identifying assets.
1.7.2			13w37a				Commands now accept name IDs aside from numerical IDs.
1.8			14w02a				Item ID format has changed from using numbers (for example, TNT's id was 46) to namespaced IDs of the form minecraft:item_name. (Example: minecraft:tnt)
1.11			16w32a				Resource locations now have a character restriction.
							Disallowed uppercase characters in resource locations.
1.13			17w47a				After the flattening, resource locations are the only accepted form of identifiers.
			pre4				Resource locations are now used to identify plugin message channels.
1.14.4			pre1				The realms namespace is added to the client jar's builtin resource pack.
1.16			20w14a				Attributes are now resource locations.
1.21.11			25w45a				ResourceLocation is renamed to Identifier in the game's code.
26.1			snap6				.. is no longer a valid namespace.

Pocket Edition Alpha
v0.16.0			build 1				Added commands, which supported string IDs. However, these identifiers were not namespaced yet.
			build 4				All entity attributes are now namespaced.
Bedrock Edition
1.6.0			beta 1.6.0.5				In the save files for worlds, items now use namespaced IDs instead of numeric IDs.
1.12.0			beta 1.12.0.2				IDs are now namespaced using the minecraft prefix, to support custom items being added through add-ons.

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

• Namespaces, as explained in "Minecraft Snapshot 17w43a" – Minecraft.net..

v t e Java Edition technical
General Concepts Block entity Coordinates Crashes Loot context Mob AI Point of Interest Identifier Screenshot Statistics Telemetry Tick Random Tick UUID JSON General format Data values Classic Remake Indev Pre-flattening Data component format Predicate Entity format Block entity format Map item format NBT Format Particle format Text component format § Formatting codes Key codes Random sequence Structure file format Schematic file format World Heightmap Seed Anomalous Data version Legacy Spawn chunk Level format Anvil file format Chunk format Player format Point of Interest format raids.dat format Command storage format Scoreboard format Legacy Classic level format Classic server protocol Indev level format Alpha level format Zone file format Region file format server_level.dat format villages.dat format Generated structures format .minecraft client.jar version.json client.json command_history.txt launcher_profiles.json launcher_settings.json options.txt version_manifest.json hotbar.nbt format Server list format Tools F3 Debug screen hotkey renderer Developer Tools GameTest DataFixerUpper Debug properties Legacy Obfuscation map Sound Block sound type Closed captions sounds.json Commands Brigadier Functions All commands Launching Mojang API Microsoft authentication Quick Play Legacy Legacy Minecraft authentication Yggdrasil Protocol Protocol version Packets Data types Encryption Server server.jar server.properties Server requirements Whitelist Operator list Code of conduct Protocols Query RCON Server Management Protocol Legacy al_version Item format
Data pack Components pack.mcmeta Pack format Advancements Functions Item modifier Loot tables Predicate Recipe Damage type Chat type Enchantment Enchantment provider Painting variant Banner pattern Instrument Jukebox song Trial spawner configuration Mob variants Dialog Armor trim Timeline Villager trade Trade set World clock Sulfur cube archetype Slot sources​[upcoming: JE 26.3] Decorated pot pattern​[upcoming: JE 26.3] Number provider Block transformer​[upcoming: JE 26.3] Tag Block Item Function Fluid Entity type Game event Biome Flat level generator preset World preset Structure Point of interest type Painting variant Banner pattern Instrument Damage type Enchantment Dialog Timeline Potion Villager trade Configured feature GameTest Test environment Test instance World generation Dimension Dimension type World preset Biomes Carver Configured feature Tree Placed feature Environment attribute Noise settings Noise router Density function Noises Surface rule Structures Structure set Template pool Processor list Structure templates Removed Configured surface builder Data packs Caves & Cliffs Prototype Data Pack Phantom Frames Tutorials Importing Creating Optimizing Command blocks and functions Repairing a world corrupted by a data pack Content Custom enchantments Custom paintings Custom trims World generation New dimension Custom structures
Resource pack Components pack.mcmeta Pack format Language Models Blockstates Items Sounds (sounds.json) Shaders Textures Atlases Aa Fonts Colormaps Texts Waypoint styles regional_compliancies.json Equipment Debug Missing font character Missing model Missing texture Tools Slicer Legacy Texture Ender Unstitcher Tutorials Creating Loading Models Sound directory

v t e Minecraft: Bedrock Edition
Editions	Merged Pocket Edition Windows 10 Edition Ports to consoles Xbox One Nintendo Switch PS4 PS5 Xbox Series X|S Nintendo Switch 2​[upcoming] Discontinued Gear VR Edition Apple TV Edition Fire TV Edition
Development	Version history Alpha Full release Development versions Minecraft Preview Removed features Unused features Unused textures Parity issue list Mentioned features Super Duper Graphics Pack Planned versions
Technical	Known bugs Minecraft Launcher Quick Play com.mojang options.txt Installation files Cache files Bedrock Dedicated Server server.properties Experiments Commands Functions Identifier Text component format Map item format Coordinates Seed Anomalous Tick Random Tick Ticking area § Formatting codes Simulation distance Screenshot Block sound type RenderDragon Data values Block entity Mob AI Flattening Development resources [NBT Compound / JSON Object] NBT format [NBT Compound / JSON Object] Level format Structure templates Protocol Protocol version RakNet Creator Official documentation Editor Map Marker File extensions GameTest Add-ons Resource packs Sound definitions Fog definition Deferred rendering Client biomes Behavior packs Block definition Block components Biome definition Item components Family Spawn event Tag Block Item Biome Structure set Template pool Processor list Recipe JSON manifest.json UUID [String] Molang Scripting
Multiplayer	Servers Featured servers GenWars Mob Maze SoulSteel Event servers Server list Splitscreen Minecraft Realms Realms Hub Social
Exclusive features	Achievements How to Play Encyclopedia Inbox Marketplace Minecoin Partner Program Add-ons Content bundles Marketplace Pass Mash-up pack Skin packs Texture packs Worlds Character Creator Emote Loading tips Ore UI Ray Tracing Seed Templates Starter Seeds Vibrant Visuals [String] Configurations Blocks Allow Border Deny Mobs Agent NPC Effects Fatal Poison Unused Unknown info_update info_update2 reserved6 tile.client_request_placeholder_block.name Nether Reactor Core Glowing Obsidian Chiseled Purpur tile.deprecated_purpur_block_2.name Deprecated Anvil Old Stonecutter Camera Old Villager Old Zombie Villager Legacy Frozen Ocean Biomes before 1.18
Removed	Crafting descriptions Nether Reactor Old Virtual reality Pocket Edition protocol Legacy