Minecraft Item IDs After 1.13 (Namespaced Names)

Since the 1.13 “flattening”, Minecraft items use string IDs like minecraft:diamond_sword instead of numeric IDs and data values. Plugin configs, give commands, recipes, and shop plugins all expect these modern names.

Section 01

Namespaced IDs explained

A namespaced ID has two parts: namespace:path.

• Namespace — usually minecraft for vanilla items; mods and datapacks use their own.
• Path — the item key, e.g. oak_planks, netherite_ingot.

Many plugins also accept the short form without the namespace (diamond_sword) and assume minecraft.

/give @p minecraft:diamond_sword 1
# or short form in many plugin configs:
material: diamond_sword

Section 02

Bukkit / Spigot material names

Paper and Spigot plugins often use the Bukkit Material enum — uppercase with underscores, e.g. DIAMOND_SWORD. That usually matches the path in uppercase, but renames across versions can diverge.

1. Pick your server’s Minecraft version in the Item IDs tool.
2. Search the display name or a fragment of the ID.
3. Copy the format your plugin expects (namespaced, short, or Bukkit).
4. Paste into the config and reload — verify with an in-game give or menu open.

Section 03

Version differences

New releases add items (and occasionally rename them). A material that exists on 1.21 may be missing on 1.16. Always match the ID list to the version your server runs.

• Shop / crate plugins with hard-coded materials break after upgrades if an item was renamed.
• Cross-version resource or config packs should avoid items that do not exist on the oldest supported release.
• Spawn eggs and variants are separate IDs post-flattening (no more a single egg + data value).

Section 04

Where item IDs show up

• Give / kit plugins — material keys in kits and starter items.
• GUI menus — icon materials; pair with slot indexes for placement.
• Economy shops — buy/sell definitions keyed by material.
• Custom recipes / datapacks — ingredient and result IDs.

FAQ

Frequently asked questions