Loot tables

Loot tables are data-driven JSON files that decide what item stacks a block, entity, chest, fishing rod or command produces — built from pools, weighted entries, item-modifying functions, gating conditions and number providers.

File location

Each loot table is one JSON file under the singular 1.21+ folder:

data/<namespace>/loot_table/<path>.json

data/mypack/loot_table/blocks/lucky_ore.json     → referenced as mypack:blocks/lucky_ore
data/mypack/loot_table/entity/boss_drop.json     → referenced as mypack:entity/boss_drop

The table ID is namespace:path (without the .json). Vanilla tables live in the minecraft namespace and can be overridden by placing a same-named file in your pack.

Top-level schema

data/<namespace>/loot_table/example.json

{
  "type": "minecraft:block",
  "random_sequence": "minecraft:blocks/diamond_ore",
  "modifier": { /* table-wide item modifier applied to every dropped stack; an array is also accepted */ },
  "pools": [ { /* pool */ } ]
}

Loot context type enum

The context determines which parameters (the killed entity, the mined block, the tool, the origin position, etc.) are available to functions and conditions.

Pool schema

One entry in the pools array

{
  "rolls": 1,
  "bonus_rolls": 0.0,
  "condition": { /* ONE condition; the pool is skipped unless it passes. Combine with all_of */ },
  "modifier": { /* applied to every stack from this pool; an array is also accepted */ },
  "entries": [ /* one is chosen per roll (weighted) */ ]
}

Both rolls and bonus_rolls accept the full number-provider syntax — a plain number, a {min,max} uniform shorthand, or an explicit provider object (see below).

Entry types

Common entry fields: type, conditions, functions, plus for weighted (singleton) entries weight (default 1) and quality (default 0).

Loot functions (full catalogue)

Every item-modifier object is {"type": "minecraft:<id>", ...params, "condition": {...}} — condition is optional on any modifier. At 26.3 the discriminator is type, not function, and the field holding them is modifier, not functions: vanilla’s own 1,447 loot tables use type 1,098 times and function never. This catalogue is identical to the standalone item modifier schema (an item-modifier file is just a reusable loot function or array of functions).

exploration_map: destination changed shape at 26.3

destination names a structure tag, and how you write that tag depends on the version. There is no single value that is correct on both sides of 26.3, which makes this the rare field where a pack spanning the two needs an overlay.

Measured, not inferred, and re-checked as 26.3 progressed. The same vanilla file — villager_trade/cartographer/2/emerald_and_compass_village_desert_map.json — reads minecraft:on_desert_village_maps at format 110 and #minecraft:on_desert_village_maps at format 111. Across shipped 26.2 all 10 distinct destination values are bare and none are prefixed. The change has since held through 26.3-pre-1 (format 119), where all 28 occurrences across 23 distinct values are prefixed and none are bare — so it shipped unchanged in the 26.3 release (format 121).

Up to 26.2 — bare, and the tag is implied

{
  "function": "minecraft:exploration_map",
  "destination": "minecraft:on_woodland_explorer_maps",
  "decoration": "woodland_mansion"
}

From 26.3 — the tag is referenced explicitly, and the key is type

{
  "type": "minecraft:exploration_map",
  "destination": "#minecraft:on_woodland_mansion_maps",
  "decoration": "woodland_mansion"
}

Couldn't parse data file 'example:cartographer/dungeon_map':
  Not a valid resource location: #example:on_dungeon_maps
  Non [a-z0-9_.-] character in namespace of identifier

Loot conditions (full list)

Every condition is {"type": "minecraft:<id>", ...}, and it sits in the singular condition field. This is the same system as standalone predicate files — the full field breakdown of each condition lives on that page.

Number providers & ranges

Number providers generate a value for rolls, bonus_rolls, set_count.count, set_damage.damage, enchant levels, value_check, random_chance, and more. The four core providers are universal:

Shorthand forms

• A plain number ("rolls": 3) is treated as a constant.
• An object { "min": x, "max": y } (no type) is treated as uniform.
• Explicit: { "type": "minecraft:uniform", "min": 1, "max": 4 }.

Int / float ranges

Distinct from number providers: a range tests a value rather than generating one. Used by predicate comparisons (count, distance, time_check.value, entity_scores, effects.amplifier, …). A range is a single number (exact match) or an object with optional min and/or max:

"count": { "min": 2, "max": 5 }     // 2..5 inclusive
"count": 3                           // exactly 3
"level": { "min": 10 }               // >= 10 (open upper bound)

"rolls": { "type": "minecraft:binomial", "n": 3, "p": 0.5 }

"count": { "type": "minecraft:score",
           "target": { "type": "context", "target": "this" },
           "score": "kills", "scale": 0.5 }

Examples

Block drop with a fortune bonus

data/mypack/loot_table/blocks/lucky_ore.json

{
  "type": "minecraft:block",
  "pools": [
    {
      "rolls": 1,
      "entries": [
        {
          "type": "minecraft:item",
          "name": "minecraft:diamond",
          "modifier": [
          { "type": "minecraft:apply_bonus",
              "enchantment": "minecraft:fortune",
              "formula": "minecraft:ore_drops"
            },
            { "type": "minecraft:explosion_decay" }
          ]
        }
      ],
      "condition": { "type": "minecraft:survives_explosion" }
    }
  ]
}

Weighted entity drop, gated on a player kill

data/mypack/loot_table/entity/boss_drop.json

{
  "type": "minecraft:entity",
  "pools": [
    {
      "rolls": { "min": 1, "max": 3 },
      "bonus_rolls": 0.5,
      "condition": { "type": "minecraft:killed_by_player" },
      "entries": [
        { "type": "minecraft:item", "name": "minecraft:diamond", "weight": 6,
          "modifier": [
          { "type": "minecraft:set_count",
                           "count": { "type": "minecraft:uniform", "min": 1, "max": 4 } } ] },
        { "type": "minecraft:item", "name": "minecraft:netherite_scrap", "weight": 1, "quality": 2 },
        { "type": "minecraft:empty", "weight": 3 }
      ]
    }
  ]
}

Chest / gift table (generic context)

data/mypack/loot_table/gameplay/enchanted_book_gift.json

{
  "type": "minecraft:generic",
  "pools": [
    {
      "rolls": 1,
      "entries": [
        {
          "type": "minecraft:item",
          "name": "minecraft:enchanted_book",
          "modifier": [
          { "type": "minecraft:enchant_with_levels", "levels": { "min": 20, "max": 39 } }
          ]
        }
      ]
    }
  ]
}

A "custom item" drop via components 1.20.5+

data/mypack/loot_table/entity/starblade_drop.json

{
  "type": "minecraft:entity",
  "pools": [
    {
      "rolls": 1,
      "condition": { "type": "minecraft:killed_by_player" },
      "entries": [
        {
          "type": "minecraft:item",
          "name": "minecraft:netherite_sword",
          "modifier": [
          { "type": "minecraft:set_components",
              "components": {
                "minecraft:custom_name": { "text": "Starblade", "color": "gold" },
                "minecraft:rarity": "epic"
              } },
            { "type": "minecraft:set_custom_data", "tag": "{starblade:1b}" }
          ]
        }
      ]
    }
  ]
}

Tricks & best practices

Version differences

Sources

• Loot table (Java Edition) — Minecraft Wiki
• Loot context (type enum) — Minecraft Wiki
• Item modifier (function catalogue) — Minecraft Wiki
• Pack format — Minecraft Wiki