Tutorials

Getting started

How to create a Minecraft command with NBTForge

6 min read

This guide shows the shortest reliable path from opening NBTForge to copying a tested command. It uses the real workbench UI, the global import bar, version selector, output panel, and project tools.

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

Goal

A copied command plus a reusable project entry.

Annotated screenshots

Start on the Home workbench, choose a module, then confirm Edition and Version before trusting output.
Copy the command for immediate use, or add it to Project when building a multi-command workflow.

Step-by-step guide

  1. Open Home and pick the module that matches the command family you need.
  2. Set Edition and Version before changing advanced fields, because Java and Bedrock syntax can diverge.
  3. Use the preview and warnings to check whether the visible command matches the intended target.
  4. Copy a single command from Output, or add it to Project when you need multiple commands together.
  5. Use Share for a URL state snapshot when another creator needs to review the same builder state.

When to use the import bar

Paste an existing command or a small .mcfunction block into the import bar when you want NBTForge to rebuild the matching visual editor. This is the fastest way to audit old commands without manually re-entering every selector and NBT field.

Bulk import is best for reviewing command packs, while a single command import is best for converting one copied command into an editable builder state.

How to avoid wrong-version output

Always check the Version field before copying. Java 1.20.4, Java 1.20.5+, snapshots, and Bedrock Stable can produce different item and entity syntax.

NBTForge surfaces warnings beside the output when a selected edition cannot represent a Java-only feature.

  • Use Java for full NBT-heavy commands.
  • Use Bedrock Stable only when the target world is Bedrock and the output warning still matches your plan.
  • Save complex commands to Project so you can return to them after switching modules.

Publish-ready check

Use this getting started 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

Can NBTForge edit commands copied from another generator?

Yes. Paste the command into the import bar. Supported command families reload into their visual editor, while unsupported lines remain safe to keep in a command pack.

Should I copy from Output or from Project?

Copy from Output for one command. Use Project when a setup needs several commands, reusable entries, or a .mcfunction-style block.

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.