Datageneration/Loot Tables - Revision history

Nexus-Dino at 17:57, 20 September 2022

2022-09-20T17:57:56Z

Random832: Change to a different approach that is easier to use and works with current versions of Minecraft.

2022-06-28T10:55:52Z

Change to a different approach that is easier to use and works with current versions of Minecraft.

Show changes

ChampionAsh5357: Update to 1.17, needs major rewrite

2021-07-31T23:18:27Z

Update to 1.17, needs major rewrite

Ferri Arnus: /* The LootPool Builder */

2021-07-16T14:45:10Z

The LootPool Builder

Ferri Arnus: /* The LootPool Builder */

2021-07-16T14:39:14Z

The LootPool Builder

Ferri Arnus: /* The LootPool Builder */

2021-07-16T14:34:50Z

The LootPool Builder

Ferri Arnus: /* The LootPool Builder */

2021-07-16T14:21:22Z

The LootPool Builder

Ferri Arnus: /* Preperation */

2021-07-16T14:20:15Z

Preperation

Ferri Arnus: /* Preperation */

2021-07-16T14:18:51Z

Preperation

Ferri Arnus: /* The LootPool Builder */

2021-07-16T14:17:18Z

The LootPool Builder

@@ Line 1: / Line 1: @@
 ==The LootTableProvider class==
 First you would need a new class that extends <code>LootTableProvider</code>. In this class you will override the <code>getTables</code> and <code>validate</code> methods.
@@ Line 22: / Line 20: @@
      @Override
      protected void validate(Map<ResourceLocation, LootTable> map, ValidationContext validationtracker) {
-         for (Map.Entry<ResourceLocation, LootTable> entry : map.entrySet())
+         map.forEach((location, lootTable) -> LootTables.validate(validationtracker, location, lootTable);
+     }
 </syntaxhighlight>
@@ Line 62: / Line 59: @@
 ===The LootTable Builder===
-This is where you actually make a loottable. You start with an empty <code>LootPool.Builder</code> and add the necessary attributes to it.
+This is where you actually make a loot table. You start with an empty <code>LootPool.Builder</code> and add the necessary attributes to it.
 * <code>.name</code> is used for the pool name.
 * <code>.setRolls</code> is used for the amount.

@@ Line 21: / Line 21: @@
 Also you would need a Function to save the Tables
 <syntaxhighlight lang="java">
-   private void writeTables(DirectoryCache cache, Map<ResourceLocation, LootTable> tables) {
+   private void writeTables(HashCache cache, Map<ResourceLocation, LootTable> tables) {
      Path outputFolder = this.generator.getOutputFolder();
      tables.forEach((key, lootTable) -> {
        Path path = outputFolder.resolve("data/" + key.getNamespace() + "/loot_tables/" + key.getPath() + ".json");
        try {
-         IDataProvider.save(GSON, cache, LootTableManager.serialize(lootTable), path);
+         DataProvider.save(GSON, cache, LootTables.serialize(lootTable), path);
        } catch (IOException e) {
          LOGGER.error("Couldn't write loot table {}", path, (Object) e);
@@ Line 53: / Line 53: @@
 * <code>.name</code> is used for the pool name.
 * <code>.setRolls</code> is used for the amount.
-* <code>.add</code> is used to add an <code>ItemLootEntry</code>. You can have multiple entries.
+* <code>.add</code> is used to add an <code>LootPoolEntryContainer$Builder</code>. You can have multiple entries.
-An <code>ItemLootEntry</code> defines what item is returned, and which functions and/or conditions are applied (see [https://minecraft.fandom.com/wiki/Loot_table Loot table] for the vanilla functions and conditions).
+A <code>LootPoolEntryContainer$Builder</code> defines what entry container is returned, and which functions and/or conditions are applied (see [https://minecraft.fandom.com/wiki/Loot_table Loot table] for the vanilla functions and conditions).
-* <code>.lootTableItem</code> is used to define which item is returned.
+* <code>.when</code> is used to apply a condition. These themselves can have multiple operations.
-After all attributes have been added the <code>LootPool.Builder</code> can be used to make a <code>LootTable.Builder</code> of the proper <code>LootParameterSets</code>. This builder can then be added to an entry in the <code>lootTables</code> map made in the previous section (you should do this in the overwritten abstract method).
+After all attributes have been added the <code>LootPool.Builder</code> can be used to make a <code>LootTable.Builder</code> of the proper <code>LootContextParamSet</code>. This builder can then be added to an entry in the <code>lootTables</code> map made in the previous section (you should do this in the overwritten abstract method).
 <syntaxhighlight lang="java">
 LootPool.Builder builder = LootPool.lootPool()
      .name(...)
      .setRolls(...)
-     .add(ItemLootEntry.lootTableItem(...)
+     .add(LootItem.lootTableItem(...)
-         .apply(Function1)
+         .apply(function1)
-         .apply(Function2
+         .apply(function2)
-             .operation(operation1)
+             .when(condition1)
-             .operation(operation2))
+             .when(condition2))
      );
 LootTable.lootTable().withPool(builder).setParamSet(...);
 </syntaxhighlight>[[Category:Data Generation]]

@@ Line 59: / Line 59: @@
 * <code>.apply</code> is used to apply a function or condition. These themselves can have multiple operations.
-After all attributes have been added the <code>LootPool.Builder</code> can be used to make a <code>LootTable.Builder</code> of the proper <code>LootParameterSets</code>. This builder can then be added to the <code>lootTables</code> map made in the previous section (in the overwritten abstract method).
+After all attributes have been added the <code>LootPool.Builder</code> can be used to make a <code>LootTable.Builder</code> of the proper <code>LootParameterSets</code>. This builder can then be added to an entry in the <code>lootTables</code> map made in the previous section (you should do this in the overwritten abstract method).
 <syntaxhighlight lang="java">
 LootPool.Builder builder = LootPool.lootPool()

@@ Line 50: / Line 50: @@
 ===The LootPool Builder===
-This is where you actually make a loottable. You start with an empty<code>LootPool</code>and add the necessary attributes to it.
+This is where you actually make a loottable. You start with an empty <code>LootPool</code> and add the necessary attributes to it.
 * <code>.name</code> is used for the pool name.
 * <code>.setRolls</code> is used for the amount.
-* <code>.add</code> is used to add an <code>ItemLootEntry</code>.
+* <code>.add</code> is used to add an <code>ItemLootEntry</code>. You can have multiple entries.
-An <code>ItemLootEntry</code> defines what is returned, and which functions and/or conditions are applied (see [https://minecraft.fandom.com/wiki/Loot_table Loot table] for the vanilla functions and conditions).
+An <code>ItemLootEntry</code> defines what item is returned, and which functions and/or conditions are applied (see [https://minecraft.fandom.com/wiki/Loot_table Loot table] for the vanilla functions and conditions).
 * <code>.lootTableItem</code> is used to define which item is returned.
-* <code>.apply</code> is used to apply a function or condition
+* <code>.apply</code> is used to apply a function or condition. These themselves can have multiple operations.
 After all attributes have been added the <code>LootPool.Builder</code> can be used to make a <code>LootTable.Builder</code> of the proper <code>LootParameterSets</code>. This builder can then be added to the <code>lootTables</code> map made in the previous section (in the overwritten abstract method).
 <syntaxhighlight lang="java">
 LootPool.Builder builder = LootPool.lootPool()
-                .name(...)
+    .name(...)
-                .setRolls(...)
+    .setRolls(...)
-                .add(ItemLootEntry.lootTableItem(...)
+    .add(ItemLootEntry.lootTableItem(...)
-                        .apply(Function1)
+        .apply(Function1)
-                        .apply(Function2
+        .apply(Function2
-                                .options(option1)
+            .operation(operation1)
-                                .options(option2))
+            .operation(operation2))
-                );
+    );
-        LootTable.lootTable().withPool(builder).setParamSet(...);
+LootTable.lootTable().withPool(builder).setParamSet(...);
 </syntaxhighlight>[[Category:Data Generation]]

@@ Line 50: / Line 50: @@
 ===The LootPool Builder===
-This is where you actually make a loottable. You start with a an empty<code>LootPool</code>and add the necessary attributes to it.
+This is where you actually make a loottable. You start with an empty<code>LootPool</code>and add the necessary attributes to it.
 * <code>.name</code> is used for the pool name.
 * <code>.setRolls</code> is used for the amount.

@@ Line 43: / Line 43: @@
 </syntaxhighlight>
-in the act Method you would then first call the Method where you create the tables or just create them in there (if you do you can ignore the next section), then you would convert the Tables and at last you would save the loottables.
+in the <code>run</code> method you would then first call the method where you create the tables or just create them in there (if you do you can ignore the next section), then you would convert the Tables and at last you would save the loottables.
 == The actual Class for Lootables ==

@@ Line 2: / Line 2: @@
 Loot Tables are not so polished like the other Providers. You need need to do some work to get them to a good state.
-== Preperation ==
+==Preperation==
-First you would need a new Class that extend the <code>LootTableProvider</code>. In this class you would override the <code>act</code> and optionally <code>getName</code> Method.
+First you would need a new Class that extend the <code>LootTableProvider</code>. In this class you would override the <code>run</code> and optionally <code>getName</code> Method.
 In the <code>getName</code> you just return the Name shown in the Logs.
 Also you should create a abstract Method which you would override in subclasses but this is not strictly needed.