Loot Table Generation 1.21.1

A guide to setting up loot table generation with datagen.

WARNING

This page is written for version 1.21.1. Documentation for older versions may be incomplete.

PREREQUISITES

Make sure you've completed the datagen setup process first.

You will need different providers (classes) for blocks, chests, and entities. Remember to add them all to your pack in your DataGeneratorEntrypoint within the onInitializeDataGenerator method.

pack.addProvider(ExampleModDamageTypesProvider.TaterDamageTypesGenerator::new);

Loot Tables Explained

Loot tables define what you get from breaking a block (not including contents, like in chests), killing an entity, or opening a newly-generated container. Each loot table has pools from which items are selected. Loot tables also have functions, which modify the resulting loot in some way.

Loot pools have entries, conditions, functions, rolls, and bonus rolls. Entries are groups, sequences, or possibilities of items, or just items. Conditions are things that are tested for in the world, such as enchantments on a tool or a random chance. The minimum number of entries chosen by a pool are called rolls, and anything over that is called a bonus roll.

Blocks

In order for blocks to drop items - including itself - we need to make a loot table. Create a class that extends FabricBlockLootTableProvider:

public class ExampleModBlockLootTableProvider extends FabricBlockLootTableProvider {
	protected ExampleModBlockLootTableProvider(FabricDataOutput dataOutput, CompletableFuture<HolderLookup.Provider> registryLookup) {
		super(dataOutput, registryLookup);
	}

	@Override
	public void generate() {
	}
}

Make sure to add this provider to your pack!

There's a lot of helper methods available to help you build your loot tables. We won't go over all of them, so make sure to check them out in your IDE.

Let's add a few drops in the generate method:

// Make condensed dirt drop its block item.
// Also adds the condition that it survives the explosion that broke it, if applicable,
dropSelf(ModBlocks.CONDENSED_DIRT);
// Make prismarine lamps drop themselves with silk touch only
dropWhenSilkTouch(ModBlocks.PRISMARINE_LAMP);
// Make condensed oak logs drop between 7 and 9 oak logs
add(ModBlocks.CONDENSED_OAK_LOG, LootTable.lootTable().withPool(applyExplosionCondition(Items.OAK_LOG, LootPool.lootPool()
		.setRolls(new UniformGenerator(new ConstantValue(7), new ConstantValue(9)))
		.add(LootItem.lootTableItem(Items.OAK_LOG))))
);

Chests

Chest loot is a little bit tricker than block loot. Create a class that extends SimpleFabricLootTableProvider similar to the example below and add it to your pack.

public class ExampleModChestLootTableProvider extends SimpleFabricLootTableProvider {
	public ExampleModChestLootTableProvider(FabricDataOutput output, CompletableFuture<HolderLookup.Provider> registryLookup) {
		super(output, registryLookup, LootContextParamSets.CHEST);
	}

	@Override
	public void generate(BiConsumer<ResourceKey<LootTable>, LootTable.Builder> lootTableBiConsumer) {
	}
}

We'll need a ResourceKey<LootTable> for our loot table. Let's put that in a new class called ModLootTables. Make sure this is in your main source set if you're using split sources.

public class ModLootTables {
	public static ResourceKey<LootTable> TEST_CHEST_LOOT = ResourceKey.create(Registries.LOOT_TABLE, ResourceLocation.fromNamespaceAndPath(ExampleMod.MOD_ID, "chests/test_loot"));
}

Then, we can generate a loot table inside the generate method of your provider.

lootTableBiConsumer.accept(ModLootTables.TEST_CHEST_LOOT, LootTable.lootTable()
		.withPool(LootPool.lootPool() // One pool
				.setRolls(ConstantValue.exactly(2.0f)) // That has two rolls
				.add(LootItem.lootTableItem(Items.DIAMOND) // With an entry that has diamond(s)
						.apply(SetItemCountFunction.setCount(ConstantValue.exactly(1.0f)))) // One diamond
				.add(LootItem.lootTableItem(Items.DIAMOND_SWORD) // With an entry that has a plain diamond sword
				)
		));