Presets

Datapack presets

Blaze Emperor fire boss loot preset

The Blaze Emperor preset is the long-command quality gate for this batch. It is not meant to be pasted into chat: the summon line carries a custom name, tags, persistence, a DeathLootTable reference, and held reward context. The gallery therefore shows both the workbench and the Path A command-block delivery chain before the in-game boss result.

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

Preset result

A long-command Blaze Emperor boss preset with visual command-block delivery and a datapack loot-table hook.

Output

Blaze Emperor long summon command

/summon minecraft:blaze ~ ~ ~ {Tags:["nbtforge_boss","blaze_emperor"],CustomName:{text:"Blaze Emperor",color:"yellow",bold:true},CustomNameVisible:1b,PersistenceRequired:1b,DeathLootTable:"nbtforge:entities/blaze_emperor",equipment:{mainhand:{id:"minecraft:diamond_sword",count:1,components:{"minecraft:custom_name":{text:"Ember Overpower Sword",color:"yellow",italic:false},"minecraft:enchantments":{"minecraft:sharpness":6}}}}}
Too long for Minecraft chat

The longest command line is 429 characters, 173 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

The boss starts as a blaze with visible health, name, and weapon context in the workbench.
The reward table belongs beside the summon command so the boss death hook has a real destination.
NBTForge flags the long line so delivery should move to a command block or datapack function.
Path A starts by giving or placing a command block because the summon line is over the chat limit.
The full summon command is stored in the block instead of being pasted into chat.
The activation step runs the stored long command safely in the capture world.
The final result verifies the delivered command spawns the tagged Blaze Emperor boss.

Build the preset

  1. Build the blaze boss in Summon with a custom name, visible nameplate, tags, and persistence.
  2. Add or document the DeathLootTable id that points to the datapack reward table.
  3. Review the output length and treat the over-chat warning as a delivery decision.
  4. Use Path A for a one-off test: place a command block and store the long summon line in it.
  5. Activate the command block with redstone after checking the stored command.
  6. Keep the loot table JSON in the same Project or datapack namespace.
  7. Test the boss in-game, then tune health, damage, and reward output separately.

Why this preset uses Path A

The Blaze Emperor summon is intentionally longer than the chat limit. Pasting it into chat would truncate the command and create a misleading failure. Path A, the command-block path, is the clearest visual delivery method for a one-off boss smoke test.

For production maps, Path B is usually a datapack function: put the slash-free summon line in a `.mcfunction`, run `/reload`, then trigger it with a short `/function` command. The article uses command-block screenshots because they are easier to review visually.

  • Do not paste the full long line into chat.
  • Use a command block for one-off tests.
  • Use a datapack function for reusable boss spawns.

Boss and loot responsibilities

The summon command is responsible for the entity: name, tags, persistence, equipment, and the DeathLootTable reference. The loot table resource is responsible for the actual reward contents after the boss dies.

Keep those responsibilities separate. If the boss spawns but drops nothing, inspect the datapack namespace and loot table path before changing the summon command.

Testing without losing the thread

Long boss commands are easy to break by editing several fields at once. Make one change, save or copy the output, then use the in-game result as proof before adding the next feature.

Tags are especially important for cleanup and follow-up commands. The example tags the boss as both `nbtforge_boss` and `blaze_emperor` so attributes, scoreboards, and cleanup commands can target only this boss.

For the item side of this boss workflow, compare the custom sword preset, Sharpness sword preset, and Minecraft command not working troubleshooting guide.

FAQ

Why not paste the Blaze Emperor command into chat?

The line is over the Java chat limit. Use a command block for a one-off test or put the slash-free line in a datapack function and run it with `/function`.

What does DeathLootTable do?

It points the entity to a loot table resource that Minecraft should use when the boss dies. The datapack must contain that resource at the matching namespace and path.

Can I change the reward sword?

Yes. Edit the held item or loot table reward separately, then recheck the command length and the datapack path before testing again.

Open this workflow

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