Datapack presets

Warden Echo boss ancient city loot preset

Warden Echo boss ancient city loot preset is now a complete boss-loot workflow instead of a thin generated note. It shows the warden boss, the DeathLootTable path, the datapack reward JSON, and the tested in-game boss result together so the encounter can be reviewed before it becomes a map fight. Use it when you need an ancient-city superboss with a rare echo-themed sword reward and want the summon command and reward table to stay in the same Project context.

Read inEN RU DE ES PT 中文日本語 VI FR 한국어 ID PL TR

Preset result

Warden Echo is wired to nbtforge:entities/warden_echo and rewards Echo Overpower Sword.

Output

Warden Echo boss and loot bundle

# 1) Summon the boss. This entity points at the custom loot table.
/summon minecraft:warden ~ ~ ~ {Tags:["nbtforge_boss","warden_echo"],CustomName:{text:"Warden Echo",color:"dark_aqua",bold:true},CustomNameVisible:1b,PersistenceRequired:1b,DeathLootTable:"nbtforge:entities/warden_echo",equipment:{mainhand:{id:"minecraft:netherite_sword",count:1,components:{"minecraft:custom_name":{text:"Echo Overpower Sword",color:"dark_aqua",italic:false},"minecraft:enchantments":{"minecraft:sharpness":6}}}}}
/attribute @e[tag=warden_echo,limit=1,sort=nearest] minecraft:max_health base set 260
/attribute @e[tag=warden_echo,limit=1,sort=nearest] minecraft:attack_damage base set 22
/data merge entity @e[tag=warden_echo,limit=1,sort=nearest] {Health:260f}

# 2) Save this datapack file as data/nbtforge/loot_table/entities/warden_echo.json
{
  "type": "minecraft:entity",
  "pools": [
    {
      "rolls": 1,
      "entries": [
        {
          "type": "minecraft:item",
          "name": "minecraft:netherite_sword",
          "weight": 1,
          "functions": [
            {
              "function": "minecraft:set_count",
              "count": 1
            },
            {
              "function": "minecraft:set_components",
              "components": {
                "minecraft:custom_name": {
                  "text": "Echo Overpower Sword",
                  "color": "dark_aqua",
                  "italic": false
                },
                "minecraft:lore": [
                  {
                    "text": "Dropped by Warden Echo",
                    "color": "gray",
                    "italic": false
                  },
                  {
                    "text": "Overpowered boss reward from NBTForge",
                    "color": "gold",
                    "italic": false
                  }
                ],
                "minecraft:enchantments": {
                  "minecraft:sharpness": 10,
                  "minecraft:unbreaking": 5,
                  "minecraft:fire_aspect": 2,
                  "minecraft:sweeping_edge": 3
                },
                "minecraft:attribute_modifiers": [
                  {
                    "id": "nbtforge:warden_echo_power",
                    "type": "minecraft:attack_damage",
                    "amount": 12,
                    "operation": "add_value",
                    "slot": "mainhand"
                  }
                ],
                "minecraft:rarity": "epic",
                "minecraft:enchantment_glint_override": true,
                "minecraft:custom_data": {
                  "nbtforge_boss_drop": "warden_echo",
                  "overpower": 1
                }
              }
            }
          ]
        }
      ]
    }
  ]
}

# 3) Optional quick test after /reload: spawn the reward without killing the boss.
/loot spawn ~ ~1 ~ loot nbtforge:entities/warden_echo

Too long for Minecraft chat

The longest command line is 431 characters, 175 over the 256-character chat input limit. Pasting it into chat can truncate the line and make Minecraft report a syntax error even when the generated command is valid.

Use a Command Block: run /give @s command_block, place it, then paste this command into the block command field.
Use a .mcfunction for a reusable datapack: save the line without the leading slash at saves/<world>/datapacks/<pack>/data/<ns>/function/<name>.mcfunction with a minimal pack.mcmeta, run /reload, then run /function <ns>:<name>. Do not paste .mcfunction content into chat.

Preset screenshot

Summon workbench configured for Warden Echo. — Warden Echo starts as a named warden with boss tags, persistence, and combat tuning.

Data Pack loot table setup for Warden Echo. — The loot table path is nbtforge:entities/warden_echo, matching the summon command DeathLootTable.

Boss and loot table output bundle for Warden Echo. — The output keeps the summon command, datapack JSON path, and quick loot test together.

In-game screenshot showing Warden Echo spawned from the boss preset. — The capture verifies Warden Echo appears in the restored test world before reward tuning continues.

Build the preset

Open the Summon workbench and choose warden as the boss entity.
Set the visible custom name to Warden Echo and keep it visible for arena QA.
Add stable boss tags so attributes, cleanup, and reward logic can target this entity.
Set max health to 260 and attack damage to 22.
Add DeathLootTable:"nbtforge:entities/warden_echo" to the boss data.
Open Data Pack and create data/nbtforge/loot_table/entities/warden_echo.json.
Configure the loot table to drop Echo Overpower Sword with name, lore, enchantments, rarity, and custom_data.
Save the summon command and loot JSON together in Project before copying either artifact.
Smoke test the boss spawn first, then test the loot table with `/loot spawn` or an arena kill.

Boss entity and reward table

Warden Echo has two separate responsibilities. The summon command creates the warden with name, tags, persistence, health, attack damage, and a DeathLootTable reference. The datapack file at data/nbtforge/loot_table/entities/warden_echo.json defines what the player receives after the boss dies.

Keeping those responsibilities separate makes the preset easier to debug. If the boss does not spawn, inspect the summon output and entity syntax. If the boss spawns but drops nothing, inspect the namespace, resource path, datapack reload, and loot table JSON before changing the entity command.

The workbench gallery is arranged around that split. The first shot checks the boss identity, the second shot checks the reward resource, and the output shot keeps both artifacts close enough that the Project entry can preserve the relationship.

Boss id: warden
Loot path: nbtforge:entities/warden_echo
Reward item: Echo Overpower Sword

Testing the encounter safely

Start with a clean summon test before balancing the full fight. Warden Echo should appear with the expected name and tags in a restored world, and the screenshot should make the boss readable without relying on old mobs or leftover effects from a previous capture.

After the spawn is stable, test the loot table independently. A quick `/loot spawn ~ ~1 ~ loot nbtforge:entities/<id>` check proves the JSON can produce the reward before the fight logic is involved. Then run the final arena path where the actual boss death triggers the same resource.

Do not tune health, damage, effects, bossbars, and loot at the same time. Make one change, update the Project entry, then test the copied artifact. That keeps a broken datapack path from looking like an entity problem and keeps an entity typo from looking like a loot failure.

Spawn test first.
Loot JSON test second.
Full arena kill test last.

Encounter placement

Warden Echo fits best when the arena setup, bossbar, warning feedback, and reward table are saved near the summon command. That gives reviewers one place to check whether the encounter starts, communicates danger, drops the intended item, and cleans up after itself.

When the preset becomes production content, move long commands into a datapack function and keep the loot table under the same namespace. The article output is deliberately explicit so the summon command and JSON path remain easy to audit before being copied into files.

For adjacent boss-loot examples, compare the Blaze Emperor fire boss loot preset, Warden Echo boss loot preset, and loot table boss drop preset.

FAQ

How does Warden Echo drop Echo Overpower Sword?

The summon command sets DeathLootTable to nbtforge:entities/warden_echo. The datapack file at data/nbtforge/loot_table/entities/warden_echo.json defines Echo Overpower Sword as the reward.

Can I paste the boss command into chat?

Only if the generated command stays under the chat limit. Boss commands usually belong in a command block for a one-off test or in a datapack function for reusable map content.

What should I test first if the reward does not drop?

Test the loot table path with `/loot spawn` first, then verify the boss summon still references the same DeathLootTable id. Most failures come from namespace or resource-path mismatches.

Open this workflow

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