Loot table

From Minecraft Wiki
Jump to: navigation, search

Loot tables are technical JSON tables that represent what items should be in naturally generated containers, what items should drop when killing a mob or breaking a block, or what items can be fished.

Usage[edit]

The loot tables are structured as a String tag which determines the table to use, and a Long tag determining the seed. Containers or mobs with the same seed and table will drop the same items. Loot tables do not determine which slot of a container is used; that is randomly determined based on the seed.

For Chests, Trapped Chests, Hoppers, Storage Minecarts, Minecarts with Hoppers, Dispensers, Droppers, and Shulker Boxes:

    •  LootTable: Loot table to be used to fill the container when it is next opened, or the items are otherwise interacted with. When the container is a chest which is part of a double chest, only the half corresponding to the tagged single-chest will be affected.
    •  LootTableSeed: Seed for generating the loot table. Works similarly to the seeds for worlds. 0 or omitted will use a random seed.

These tags will be removed once the items have been interacted with (by opening the container, breaking the container, etc.), and only then will items be put in the container.

For Mobs:

  • The root tag.
    •  DeathLootTable: Loot table to be used for the items that drop when the entity is killed.
    •  DeathLootTableSeed: Seed for generating the loot table. Works similarly to the seeds for worlds. 0 or omitted will use a random seed.

The loot tables of mobs and containers can be altered with /entitydata, /blockdata, /execute store and /data merge. The player could also grant a loot table to an entity or drop it in the world with /loot‌[upcoming] .

Tags[edit]

Loot tables are defined using the JSON format. Below are a list of tags used.

  •  The root tag
    •  pools: A list of all pools for this entity. Each pool used will generate items from its list of items based on the number of rolls. Pools are applied in order.
      •  A pool
        •  conditions: Determines conditions for this pool to be used. If multiple conditions are specified, all must pass.
          •  A condition
            •  condition: Name of condition. Valid conditions are described below.
        •  rolls: Specifies the exact number of rolls on the pool.
        •  rolls: Specifies a random number of rolls within a range.
          •  min: Minimum number of rolls. Inclusive.
          •  max: Maximum number of rolls. Inclusive.
        •  bonus_rolls: Specifies the exact number of bonus rolls on the pool per point of luck. Rounded down after multiplying.
        •  bonus_rolls: Specifies a random number of bonus rolls within a range. Rounded down after multiplying.
          •  min: Minimum number of bonus rolls. Inclusive.
          •  max: Maximum number of bonus rolls. Inclusive.
        •  entries: A list of all things that can be produced by this pool. One entry is chosen per roll as a weighted random selection from all entries without failing conditions.
          •  An entry
            •  conditions: Determines conditions for this entry to be used. If multiple conditions are specified, all must pass.
              •  A condition
                •  condition: Name of condition. Valid conditions are described below.
            •  type: Type of entry. Can be item for item entries, loot_table to produce items from another loot table, or empty for an entry that generates nothing.
            •  name:
              • For type 'item', ID name of the item to be produced, e.g. minecraft:diamond. The default, if not changed by functions, is a stack of 1 of the default instance of the item.
              • For type 'loot_table', loot table to be used, e.g. minecraft:gameplay/fishing/junk.
            •  functions: For type 'item', applies functions to the item stack being produced. Functions are applied in order, so for example looting_enchant must be after set_count to work correctly.
              •  A function:
                •  function: Name of the function to apply. Valid functions are described below.
                •  conditions: Determines conditions for this function to be applied. If multiple conditions are specified, all must pass.
                  •  A condition
                    •  condition: Name of condition. Valid conditions are described below.
            •  weight: Determines how often this entry will be chosen out of all the entries in the pool. Entries with higher weights will be used more often (chance is this entry's weight⁄total of all considered entries' weights).
            •  quality: Modifies the entry's weight based on the killing/opening/fishing player's luck attribute. Formula is floor( weight + (quality * generic.luck)).

Functions[edit]

Loot tables use various functions to change the item stack being produced, such as adjusting the stack size or adding enchantments. Below are a list of valid functions, and the tags used by them. The tags are placed in the same function object as  function:.

  • A function
    •  function: "enchant_randomly" - Enchants the item with one randomly-selected enchantment. The level of the enchantment, if applicable, will be random.
    •  enchantments: List of enchantment names to choose from. If omitted, all enchantments applicable to the item will be possible.
  • A function.
    •  function: "enchant_with_levels" - Enchants the item, with the specified enchantment level (roughly equivalent to using an enchantment table at that level).
    •  treasure: Determines whether treasure enchantments are allowed on this item.
    •  levels: Specifies the exact enchantment level to use.
    •  levels: Specifies a random enchantment level within a range.
      •  min: Minimum level to use.
      •  max: Maximum level to use.
  • A function.
    •  function: "exploration_map" - Converts an empty map into an explorer map leading to a nearby generated structure.
    •  destination: The type of generated structure to locate. Accepts any of the StructureTypes used by the /locate command (case insensitive).
    •  decoration: The icon used to mark the destination on the map. Accepts any of the map icon text IDs (case insensitive). If mansion or monument is used, the color of the lines on the item texture will change to match the corresponding explorer map.
    •  zoom: The zoom level of the resulting map. Defaults to 2.
    •  search_radius: The size, in chunks, of the area to search for structures. The area checked is square, not circular. Radius 0 causes only the current chunk to be searched, radius 1 causes the current chunk and eight adjacent chunks to be searched, and so on. Defaults to 50.
    •  skip_existing_chunks: Don't search in chunks that have already been generated. Defaults to true.
  • A function.
    •  function: "furnace_smelt" - Smelts the item as it would be in a furnace. Used in combination with the entity_properties condition to cook food from animals on death.
  • A function.
    •  function: "looting_enchant" - Adjusts the stack size based on the level of the Looting enchantment on the killer entity.
    •  count: Specifies an exact number of additional items per level of looting.
    •  count: Specifies a random number (within a range) of additional items per level of looting. Note the random number generated may be fractional, and will be rounded after multiplying by the looting level.
      •  min: Minimum increase.
      •  max: Maximum increase.
    •  limit: Specifies the maximum amount of items in the stack after the looting calculation. If the value is 0, no limit is applied.
  • A function.
    •  function: "set_attributes" - Add attribute modifiers to the item.
    •  modifiers
      •  A modifier
        •  name: Name of the modifier.
        •  attribute: The name of the attribute this modifier is to act upon.
        •  operation: Must be either "addition", "multiply_base" or "multiply_total".
        •  amount: Specifies the exact amount of change of the modifier.
        •  amount: Specifies a random amount within a range.
          •  min: Minimum amount.
          •  max: Maximum amount.
        •  id: Optional : UUID of the modifier following. If none specified, a new UUID will be generated.
        •  slot: Slots the item must be in for the modifier to take effect, this value can be one of the following : "mainhand", "offhand", "feet", "legs", "chest", or "head".
        •  slot: One of the listed slots will be chosen randomly.
  • A function.
    •  function: "set_count" - Sets the stack size.
    •  count: Specifies the exact stack size to set.
    •  count: Specifies a random stack size within a range.
      •  min: Minimum stack size.
      •  max: Maximum stack size.
  • A function.
    •  function: "set_damage" - Sets the item's damage value (durability) for tools.
    •  damage: Specifies the damage fraction to set (1.0 is undamaged, 0.0 is zero durability left).
    •  damage: Specifies a random damage fraction within a range.
      •  min: Minimum value.
      •  max: Maximum value.
  • A function.
    •  function: "set_name" - Adds display name of the item.
    •  name: A simple name like with an anvil.
    •  name: A JSON text component name, allowing color, translations, etc.
  • A function.
    •  function: "set_nbt" - Adds NBT data to the item.
    •  tag: Tag string to add, similar to those used by commands. Note that the first bracket is required and quotation marks need to be escaped using a backslash (\).

Conditions[edit]

Loot tables use various conditions which add requirements to a drop, pool, or function. Below are a list of valid conditions, and the tags used by them. The tags are placed in the same condition object as  condition:.

  • alternative - Joins conditions from parameter terms with "or". ‌[upcoming 1.14]
  • block_state_property - Check properties of block state. ‌[upcoming 1.14]
    •  block: id of block;test will fail if broken block doesn't match.
    •  properties: map of property:value pairs.
  • entity_present - Returns true if entity is set. ‌[upcoming 1.14]
  • entity_properties - Test properties of an entity.
    •  entity: Specifies the entity to check for the condition. Set to this to use the entity that died, killer for the killer, or killer_player for a killer that is a player.
    •  properties: Properties to be checked.
      •  on_fire: Test whether the entity is or is not on fire.
  • entity_scores - Test the scoreboard scores of an entity.
    •  entity: Specifies the entity to check for the condition. Set to this to use the entity that died, killer for the killer, or killer_player for a killer that is a player.
    •  scores: Scores to check. All specified scores must pass for the condition to pass.
      •  A score: Key name is the objective while the value is the exact score value required for the condition to pass.
      •  A score: Key name is the objective while the value specifies a range of score values required for the condition to pass.
        •  min: Minimum score.
        •  max: Maximum score.
  • inverted - Inverts condition from parameter term. ‌[upcoming 1.14]
  • killed_by_player - Test if a killer_player entity is available.
    •  inverse: If true, the condition passes if killer_player is not available.
  • match_tool - Checks tool. ‌[upcoming 1.14]
    •  predicate: Predicate applied to item, uses same structure as advancements.
  • random_chance - Test if a random number 0.0–1.0 is less than a specified value.
    •  chance: Success rate as a number 0.0–1.0.
  • random_chance_with_looting - Test if a random number 0.0–1.0 is less than a specified value, affected by the level of Looting on the killer entity.
    •  chance: Base success rate.
    •  looting_multiplier: Looting adjustment to the base success rate. Formula is chance + (looting_level * looting_multiplier).
  • survives_explosion - Returns true with 1/explosion radius probability. ‌[upcoming 1.14]
  • table_bonus - Passes with probability picked from table, indexed by enchantment level. ‌[upcoming 1.14]
    •  enchantment: Id of enchantment.
    •  chances: List of probabilities for enchantment level, indexed from 0.
  • tool_enchantment ‌[upcoming 1.14]

List of loot tables[edit]

Below is a list of all loot tables that exist by default. More tables can be added in the world save for use with custom maps.

Data packs[edit]

Main article: data packs

Custom data packs use loot tables to change what loot will spawn in containers or drop by mobs. They can either change existing loot tables or create new ones. This is the file structure:

  • world save folder
    • datapacks
      • data pack
        • data
          • minecraft
            • loot_tables
              • loot table name.json
          • custom directory
            • loot_tables
              • loot table name.json

The JSON files go in this folder. For example, the file for zombies would go in datapacks/pack name/data/minecraft/loot_tables/entities/zombie.json. This will make every zombie in that world use the datapack's loot table rather than the default zombie loot table. To add custom loot tables, create a new file in a new directory. Then, summon the mob with the data tag DeathLootTable set to the name of the directory and file (without the .json extension), such as DeathLootTable:"customdirectory:path/to/table".

History[edit]

Java Edition
1.9 October 19, 2015Dinnerbone announces loot tables.
15w43a Added loot tables.
15w43b Added condition entity_scores.
15w43c Renamed "villager_golem.json" to "iron_golem.json"
Added fishing loot tables, sheep without wool, and zombie and skeleton horses.
Renamed the tag  item: to  name:, and the tag  items: to  entries:
Added the tag  type: and support to load a loot table instead of an item.
Added the tag  luck: to default files, though it currently does nothing in the code.
Added the function set_damage
15w44a Added the function enchant_randomly and set_attributes.
15w44b Added the  quality tag.
Removed  luck and  luck_multiplier tags.
Added the  bonus_rolls tag.
15w51a A player in spectator mode will no longer trigger a container to use its loot table to generate loot.
1.9.1 pre1 Loot tables now work with dispensers and droppers.
Added default table chests/jungle_temple_dispenser.
1.11 16w32a Donkey, mule, husk and zombie villager now each draw from their own loot tables, rather than drawing from the horse and zombie loot tables, respectively
16w43a Villagers, vexes and ender dragons are now able to draw from their own loot tables
1.13 17w43a Custom loot tables have been moved into data packs.
Upcoming Java Edition
1.14 18w43a Block drops changed to use loot tables too.
18w44a Added loot tables for cat, cat_morning_gift, player, wither.
Added loot tables for new blocks.
18w46a Added loot table for illusioners.
18w48a Added more loot tables for villages, some of which are currently unused.
Removed loot table: village_blacksmith
18w49a village_savanna_house and village_snowy_house loot tables are now used.
Added more loot tables for villages.
18w50a
village_desert house and village_taiga_house loot tables are now used, making all previously unused loot tables no longer unused.

Issues[edit]

Issues relating to "Loot table" are maintained on the bug tracker. Report issues there.

Minecraft data packs
Components
Other
Retrieved from "https://minecraft.gamepedia.com/index.php?title=Loot_table&oldid=1299111"