Spawning Custom Items in the World

During development, the fastest way to test a custom item is through the `/give` command or the creative inventory. For an item to appear in the creative menu, its behavior pack file must include a `menu_category` object inside the `description` block. If you omit this, or set `is_hidden_in_commands` to true, the item will not appear in the creative tabs and will not autocomplete in the chat window, though `/give` may still function if typed out manually.

Beyond `/give`, you can use `/replaceitem` to force a custom item into a specific slot on an entity or inside a block container, and `/loot` to generate items from a loot table directly into the world or an inventory. Always include your custom namespace when referencing the item in any command.

{
  "format_version": "1.20.50",
  "minecraft:item": {
    "description": {
      "identifier": "my_pack:copper_coin",
      "menu_category": {
        "category": "items",
        "group": "itemGroup.name.ingot",
        "is_hidden_in_commands": false
      }
    },
    "components": {
      "minecraft:icon": {
        "texture": "copper_coin"
      },
      "minecraft:max_stack_size": 64
    }
  }
}

For survival gameplay, custom items are most commonly spawned through loot tables. Mob deaths, chest generation, block destruction (when paired with the `minecraft:loot` block component), and fishing all pull from JSON files inside the `BP/loot_tables/` directory. To spawn your item, set an entry's `type` to `item` and its `name` to your full custom identifier.

Standard loot functions work on custom items just as they do on vanilla ones. You can use `set_count` to randomize the stack size, `set_damage` for items that have a `minecraft:durability` component, and `set_name` or `set_lore` to customize the tooltip on the spawned stack.

{
  "pools": [
    {
      "rolls": 1,
      "entries": [
        {
          "type": "item",
          "name": "my_pack:copper_coin",
          "weight": 3,
          "functions": [
            {
              "function": "set_count",
              "count": {
                "min": 1,
                "max": 5
              }
            }
          ]
        },
        {
          "type": "empty",
          "weight": 1
        }
      ]
    }
  ]
}

When you need precise control over where an item appears in the physical world, the `@minecraft/server` Script API provides the `Dimension.spawnItem` method. This creates a floating `minecraft:item` entity at any `Vector3` location in the chosen dimension. You must first construct an `ItemStack` instance using your custom item's identifier and the desired stack size.

Because `spawnItem` returns the newly created `Entity` object, you can immediately call entity methods on the dropped item—such as `applyImpulse` or `clearVelocity`—to control how it scatters. Remember that calls which modify the world state cannot run inside read-only ”before” event callbacks; wrap them in `system.run` if triggered from a restricted context.

import { world, ItemStack } from "@minecraft/server";

world.afterEvents.playerBreakBlock.subscribe((event) => {
  const { block, dimension } = event;

  if (block.typeId === "minecraft:clay") {
    const coinStack = new ItemStack("my_pack:copper_coin", 2);
    const spawnPos = {
      x: block.location.x + 0.5,
      y: block.location.y + 0.5,
      z: block.location.z + 0.5
    };

    const itemEntity = dimension.spawnItem(coinStack, spawnPos);
    itemEntity.applyImpulse({ x: 0, y: 0.2, z: 0 });
  }
});

The phrase ”spawning items” can also refer to items whose purpose is to spawn entities, similar to vanilla spawn eggs or boats. In Bedrock Edition, this is handled by attaching the `minecraft:entity_placer` component to your custom item. When the player uses the item on a block, the component spawns the specified entity at the clicked face and consumes one item from the stack (unless the player is in creative mode).

You can restrict which blocks the item works on by populating the `use_on` list with block identifiers, and which blocks it can be dispensed onto from a dispenser using `dispense_on`. If both lists are omitted, the item can place the entity on any solid surface.

{
  "format_version": "1.20.50",
  "minecraft:item": {
    "description": {
      "identifier": "my_pack:golem_totem",
      "menu_category": {
        "category": "nature",
        "group": "itemGroup.name.mobEgg"
      }
    },
    "components": {
      "minecraft:icon": {
        "texture": "golem_totem"
      },
      "minecraft:max_stack_size": 16,
      "minecraft:entity_placer": {
        "entity": "minecraft:iron_golem",
        "use_on": [
          "minecraft:iron_block",
          "minecraft:stone"
        ],
        "dispense_on": [
          "minecraft:iron_block"
        ]
      }
    }
  }
}

Applies to Bedrock Edition 1.20.50 and newer. No experimental toggles are required for custom items, loot tables, `minecraft:entity_placer`, or `Dimension.spawnItem` in the stable `@minecraft/server` module (1.8.0 and above).

Read out of the game itself, so the ids match the version you are building for.