The below example will only trigger if the entity calling it was killed by a skeleton resulting in either a diamond or piece of coal. You can also apply conditions to specific entries within the roll. You can name items and give them lore, drop resource crates full of supplies, and even create written books for instructions or information. There are plenty of other functions that can modify the selected item.
The next tutorial will go over them. Loot and Trade Table Functions. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Loot tables are technical JSON files that are used to dictate what items should generate in various situations, such as what items should be in naturally generated containers , what items should drop when breaking a block or killing a mob , what items can be fished , and more.
It does not affect dropped experience , or dropped non-item entities such as slimes from larger slimes or silverfish from infested blocks. The loot tables are structured as a String tag that determines the table to use, and a Long tag determining the seed. Containers or mobs with the same seed and table drop the same items. Loot tables do not determine the container's slot to be used; that is randomly determined based on the seed.
For chests , trapped chests , hoppers , storage minecarts , minecarts with hoppers , dispensers , droppers , shulker boxes and barrels :. These tags are removed once the items have been interacted with by opening the container, breaking the container, etc. Loot tables are defined using the JSON format. Below are a list of tags used. Loot functions are used within loot tables to apply modifications to the item stack being produced, such as adjusting the stack size or adding enchantments.
They can also be used in standalone files called Item modifiers , where they can be called upon to modify items in an already existing item slot within a block or entity's inventory. The specific structure of a loot function is shown on the Item modifiers page. Loot conditions are JSON structures that are used within loot tables to add requirements to a drop, pool, or function. They can also be used in standalone files called predicate , where they can be called upon from multiple different contexts.
The specific structure of a loot condition is shown on the Predicates page. Loot tables use number providers in some places that accept an int or float. They can either be defined as a constant value or as an object.
The possible values for type and associated extra contents:. 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. Note that some blocks, such as bedrock, end portals and other blocks unbreakable in survival do not have loot tables, some blocks share loot tables namely wall and floor variants of blocks and that certain drops, namely head drops from charged creepers and the wither's nether star, are currently not covered by loot tables.
Custom data packs use loot tables to change what loot can spawn in containers or drop by mobs. They can either change existing loot tables or create new ones. This is the file structure:. The JSON files go in this folder. On Hard difficulty, a chance of 1.
Increasing chance to a number higher than 1. For example, setting chance to 2. Generates a random enchantment that is compatible with the item. Treasure enchantments are enchantments that cannot be obtained through the enchanting table, including Frost Walker, Mending, Soul Speed, Curse of Binding, and Curse of Vanishing.
Applies an enchantment as if it were enchanted through an enchanting table using a minimum and maximum XP level defined through the levels parameter. This function allows you to set a list of specific enchantments on an item. It also allows you to apply enchantments to items that wouldn't normally be enchantable in-game. You can also define the enchantments as objects to specifically define an enchantment level.
Max enchantment levels are hard-coded and can't be overwritten. The following set of functions allow you to modify the results in different ways, such as setting how many of an item is returned, setting its data value, or even setting the name and lore of an item.
This function allows you to modify the count of how many items are returned when an entity is killed by an item with the looting enchantment. Due to that, it only works with loot tables, and only if that loot table is called by the death of an entity.
This allows you to randomize the block state of the resulting item. For instance, the following example code can drop stone 0 , granite 1 , polished granite 2 , diorite 3 , polished diorite 4 , or andesite 5. X Mob in fire Only if the entity is in fire The mob itself The mob killer The mob killer, only if it's a player Which entity must be in fire? Score Which score s must have the entity? The mob itself The mob killer The mob killer, only if it's a player Which entity affect the score?
Add a score. Chance Define percentage chance. Chance with the Looting Enchantment What's the chance to add for each looting enchantment level?
0コメント