Presets

Datapack presets

Loot table preset for boss drops

Loot table preset for boss drops is now a complete Data Pack workflow instead of a templated command note. Use this preset when a boss reward should live in a datapack resource instead of a one-off `/give` line. The loot table keeps the reward tied to the entity death path, which is easier to reuse across arenas and easier to review before shipping a map. The article keeps the setup fields, output review, Project placement, and result capture together so the command is easy to audit before it becomes part of a map setup, event trigger, or reusable command pack. The Data Pack workbench keeps namespace, resource path, rolls, conditions, and reward entries visible beside the generated JSON. That is the important review point because a boss summon can point at this file with `DeathLootTable`, but the drop behavior still depends on the JSON being valid and placed under the expected path.

Read inENRUDEESPT中文日本語VIFR한국어IDPLTR

Preset result

A datapack loot table that drops the Ashen Warlord Blade only when the boss is killed by a player.

Output

Boss loot table JSON

data/nbtforge/loot_table/entities/ashen_warlord.json
{
  "type": "minecraft:entity",
  "pools": [
    {
      "rolls": 1,
      "conditions": [
        {
          "condition": "minecraft:killed_by_player"
        }
      ],
      "entries": [
        {
          "type": "minecraft:item",
          "name": "minecraft:netherite_sword",
          "functions": [
            {
              "function": "minecraft:set_components",
              "components": {
                "minecraft:custom_name": {
                  "text": "Ashen Warlord Blade",
                  "color": "red",
                  "italic": false
                },
                "minecraft:enchantment_glint_override": true,
                "minecraft:custom_data": {
                  "boss_drop": "ashen_warlord"
                }
              }
            }
          ]
        }
      ]
    }
  ]
}

Preset screenshot

Start with the Data Pack controls that define the preset state.
The second shot highlights the setting or companion command that changes player-facing behavior.
The output shot keeps the final command or command pair visible before it enters Project.

Build the preset

  1. Open the Data Pack workbench.
  2. Set Generator to Loot Table.
  3. Set namespace to `nbtforge` and resource path to `entities/ashen_warlord`.
  4. Set table type to `minecraft:entity`.
  5. Use one roll and add a `killed_by_player` pool condition.
  6. Set the reward entry to the boss item or item modifier target.
  7. Copy the JSON path and save it with the matching boss summon in Project.
  8. Smoke test the file with `/loot spawn` before attaching it to the final boss.

Why this Data Pack preset belongs in Project

Use this preset when a boss reward should live in a datapack resource instead of a one-off `/give` line. The loot table keeps the reward tied to the entity death path, which is easier to reuse across arenas and easier to review before shipping a map.

The Data Pack workbench keeps namespace, resource path, rolls, conditions, and reward entries visible beside the generated JSON. That is the important review point because a boss summon can point at this file with `DeathLootTable`, but the drop behavior still depends on the JSON being valid and placed under the expected path. A copied command is only useful when the surrounding assumptions are visible: selector scope, world state, order inside the pack, and the exact output that will be pasted into Minecraft. Treat this preset as a checkpoint where those details can be reviewed before the command leaves NBTForge.

The gallery is structured around that review. The first shot shows the workbench state, the second shot calls out the field or companion module that changes player-facing behavior, and the output shot keeps the command or command pair visible. When the preset has a visible result, the in-game capture confirms the same idea in a restored test world rather than relying on a generic overlay.

Testing and scope checks

Do not test the reward only with `/loot give` and assume the boss is wired. Test both pieces: the loot table JSON and the summon command that references `nbtforge:entities/ashen_warlord` as its death loot table.

Run the first smoke test with a narrow selector and a clean world state. Environment, utility, routing, and feedback commands can look harmless, but they often affect every player or the whole world. Confirm the command changes only the intended state, then save the exact output beside the setup or follow-up lines that explain why it exists.

If the command becomes part of a function file or command-block chain, test the copied artifact, not only the live workbench state. That catches stale selectors, wrong command order, missing setup lines, and effects that only appeared to work because a previous test left state behind.

  • Keep selectors narrow until the full pack is reviewed.
  • Place world setup before encounter-specific overrides.
  • Save feedback commands next to the state change that triggers them.

Where to go next

After the table is saved, connect it to a boss summon, an item modifier, and a Project entry that records where the datapack file belongs.

For the encounter side, pair this with the Blaze Emperor boss loot preset or the item modifier custom reward preset.

FAQ

Can I paste this Data Pack command into chat?

Usually yes for a one-command smoke test if the selector is safe and the line is short. For repeatable map behavior, save it to Project and copy the ordered pack or function-style output.

Why is this gallery UI-only?

This preset produces JSON, project organization, or review workflow rather than a visible in-world object. The useful proof is the workbench state, output, and Project placement.

What should I check before sharing this preset?

Check selector scope, command order, target version, and whether the command belongs in setup, encounter logic, feedback, or cleanup. Those categories decide where it should sit in a Project pack.

Open this workflow

Start from the related Data Pack workbench, then adjust the preset fields for your world.