newaminjewellery.com → gas → 2027 steel stainless → minecraft block id
Posted on by Miller Watts

Minecraft block ID

Close-up of a Minecraft block ID label on a stone block in a creative mode inventory screen

Minecraft block ID is a unique numeric identifier assigned to every block in the game's internal code. These IDs define which block appears when placed, how it behaves, and whether it can be referenced in commands or mods. They are essential for game mechanics, custom content creation, and server management.

Block IDs originated in early versions of Minecraft, particularly in the Java Edition before 1.13. At that time, each block was assigned a number-like 1 for grass, 12 for stone-and these numbers were hardcoded into the game's logic. Players and modders used these IDs to spawn blocks via commands, build redstone circuits, or create custom maps.

With the 1.13 update, Mojang replaced numeric IDs with string-based identifiers called "namespaces" and "registry keys." Now, blocks are referenced by names like minecraft:stone rather than numbers. Despite this change, the old numeric system still exists under the hood for backward compatibility, and many tools, scripts, and older mods still rely on the original IDs.

How block IDs function in gameplay

In older versions of Minecraft (pre-1.13), block IDs were used directly in commands and data files. For example, the command /give @p minecraft:stone 64 would give a player 64 stone blocks-but only if the game recognized the namespace format. Before 1.13, the same command would have used the numeric ID: /give @p 1 64.

The shift to namespaces improved clarity and consistency. Instead of remembering that ID 12 is stone, players now use minecraft:stone. This prevents confusion-especially when multiple mods add blocks with similar names. A block named modname:obsidian_lantern belongs to a specific mod, avoiding conflicts with vanilla blocks.

Despite the move to strings, some tools still reference numeric IDs. The NBT editor MCA Selector uses old-style IDs to filter chunks. Server administrators using plugins like WorldEdit may see logs referencing block IDs as integers. These systems haven't fully transitioned, so understanding both formats remains necessary.

Types of block identifiers and their differences

There are three main types of block references in Minecraft: legacy numeric IDs, modern namespace strings, and internal registry indices. Each serves a different purpose and operates differently.

Type Format Use Case Example
Legacy ID Integer (e.g., 12) Older versions, modding tools, command syntax in pre-1.13 worlds 12 = stone
Namespace ID String (e.g., minecraft:stone) Current game version, commands, datapacks, modding frameworks minecraft:stone
Registry Index Integer (e.g., 112) Internal game data, debugging, mod development 112 = stone in the current registry

Namespace IDs are the standard today. They follow the pattern [namespace]:[path]. The namespace identifies the source-minecraft for default blocks, create for the Create mod. The path describes the block's location in the registry hierarchy. For example, minecraft:oak_log is the log from an oak tree.

A common mistake is assuming all IDs are interchangeable. They are not. Using 12 in a 1.20.4 world will fail because the game expects minecraft:stone. Conversely, trying to use minecraft:stone in a 1.12.2 world with a command that requires a number will cause errors. Always verify the version context.

Common confusions and corrections

Many players assume that block IDs are static across all versions. They are not. The numeric ID for a block can change between versions due to updates, new features, or registry reorganization. For example, in 1.12.2, the ID for a furnace was 61. In 1.13+, it became minecraft:furnace. The number 61 still exists in the game's internal list but now refers to a different block.

Another misconception is that block IDs are the same as item IDs. They are not. While some blocks and items share the same ID (e.g., dirt block and dirt item), others do not. A torch is ID 50 as an item, but as a block, it's ID 50 too-but only in the old system. In modern versions, torches are minecraft:torch and minecraft:torch respectively, but they're treated as distinct entities in the game engine.

One non-obvious fact: the registry index (used internally by the game) is not the same as the legacy ID. In 1.20.4, the stone block has a registry index of 112, but its legacy ID was 12. The registry index is assigned during startup based on the order blocks are loaded. It's not meant for user interaction-it's for the game's internal tracking.

Real-world application: building a custom structure

Suppose you want to build a 5x5x5 cube of obsidian using a command in Minecraft 1.20.4. You'd use the /fill command with the namespace format:

/fill ~-2 ~-2 ~-2 ~2 ~2 ~2 minecraft:obsidian replace

If you tried this in 1.12.2, the command would fail unless you used the numeric ID. In that version, the equivalent command would be:

/fill ~-2 ~-2 ~-2 ~2 ~2 ~2 49 replace

Here, 49 is the legacy ID for obsidian. Using minecraft:obsidian in 1.12.2 results in an error because the game doesn't recognize the namespace format.

I once built a redstone-powered minecart launcher using a command block setup in a 1.12.2 survival map. I had to cross-reference a block ID list from the official Minecraft wiki and test each ID in-game. I discovered that the ID for a redstone lamp was 61-not 60, which I expected. That small mismatch broke the circuit until I corrected it. This taught me that even experienced users can misremember IDs, especially when working across versions.

Where to find accurate block ID references

For current versions, the official Minecraft Wiki (https://minecraft.wiki) provides the most accurate namespace-based block references. Search for a block like "stone," and the page shows minecraft:stone as the identifier. It also lists the block's properties, such as hardness (1.5), light level (0), and whether it can be broken by hand.

For legacy IDs, the Minecraft Data Pack documentation and community archives like the BlockID database (https://blockid.minecrafthelp.com) offer searchable tables. These sites include historical data, including changes between versions. For example, the ID for a water bucket changed from 330 to 331 in 1.13 due to the addition of new fluid types.

When working with mods, always consult the mod's documentation. Some mods use custom namespaces (e.g., quark:blue_rock). Their block IDs won't appear in vanilla lists. Tools like JEI (Just Enough Items) display both the name and the ID when hovering over a block in the inventory.

Understanding Minecraft block ID is critical for anyone creating content, managing servers, or developing mods. Whether you're using minecraft:stone in a command or checking a legacy ID in a 1.12.2 world, accuracy matters. Always verify the version and format.


Related Posts