Tutorials

Advanced

Advanced and datapack guide: data merge, loot tables, diff, and project reuse

9 min read

Advanced workflows are where command generators often become hard to reuse. NBTForge keeps datapack JSON, diff review, bulk import, and saved Project entries close to the output panel.

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

Goal

A structured datapack or command-pack workflow with reusable saved entries.

Annotated screenshots

The Data Pack module exposes structured JSON fields and keeps generated output visible.
Project turns one-off generated commands into reusable entries and ordered command packs.

Step-by-step guide

  1. Use Advanced for lower-level command families such as data merge, execute-if, loot, rotate, enchant, damage, and clear.
  2. Use Data Pack when the output is JSON rather than a slash command.
  3. Open Diff before replacing an existing command or JSON resource.
  4. Use bulk import when reviewing a .mcfunction block.
  5. Save reusable entries so future edits start from a known builder state.

Why diff matters

Diff review helps you see what changed between the current output and an imported or previously saved command. This reduces accidental edits when commands become long.

For datapack JSON, diff review is especially useful because a small value change can alter loot, predicates, or item modifiers.

How Project supports reuse

Saved Project entries keep the command, title, module, and state together. That means a future edit can reload the right builder instead of forcing you to parse a long command manually.

Command Pack entries preserve copy order for workflows that must run line by line.

  • Bulk import .mcfunction text.
  • Save reusable entries with clear titles.
  • Use Project search before creating duplicates.
  • Copy the pack only after reviewing order.

Publish-ready check

Use this advanced tutorial as a repeatable workflow, not only as a one-time screen tour. After the command works in the workbench, copy the final Output or Project pack into a clean test world and confirm the copied text behaves the same way.

When a command depends on version syntax, selectors, saved project entries, or datapack resources, write those assumptions into the project title or surrounding notes. That makes the tutorial useful when another creator opens the same workflow later.

  • Test the copied command, not only the visible builder state.
  • Keep the Edition and Version choice attached to the workflow.
  • Use Project for multi-command setups and future edits.
  • Recheck warnings after importing old commands or switching modules.

FAQ

Is the Data Pack module a Misode replacement?

It is moving in that direction. Current coverage focuses on structured JSON editing with typed output, while future work should expand recipes, predicates, and pack export parity.

Should I store every generated command?

Store commands you expect to edit again. Temporary test commands can be copied directly from Output.

When is this workflow ready to share?

Share it after the copied output has been tested in a clean world or command block, and after any required version, selector, datapack, or Project assumptions are written down.