Tutorials

Core

Core command guide: Summon, Give, Item, and Blocks

7 min read

Core modules cover the commands most creators use every day: summoning entities, giving items, replacing slots, setting blocks, and filling areas. This guide explains how to move between them without losing output clarity.

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

Goal

A clean core command workflow for entities, items, and blocks.

Annotated screenshots

The Core category keeps the highest-frequency command builders together.
Give commands are version-aware, so item components and legacy item syntax stay separated.

Step-by-step guide

  1. Use Summon when the root of the command is an entity.
  2. Use Give when the root of the command is an item stack in a player inventory.
  3. Use Item for slot modification commands after the target already has an inventory.
  4. Use Blocks for setblock and fill workflows that change the world.
  5. Copy output only after the module label, target, and version all match your use case.

Summon versus Give

Summon writes entity data, including equipment and passengers. Give writes item stack data, including names, lore, enchantments, attributes, books, and component-era item data.

If your command starts with an item and later affects an entity, build the item in Give first, save it, then reuse the output or item data in the entity workflow.

Core workflow checklist

Before copying, verify the visible command family. The Output panel should begin with the same command you intended to build.

For Java 1.20.5+ item syntax, check components carefully. For older Java versions, expect legacy NBT and item damage syntax.

  • Confirm target selector.
  • Confirm Java or Bedrock target.
  • Use Diff before replacing an existing command.
  • Save important commands to Project.

Publish-ready check

Use this core 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

Why does the same item command change between versions?

Minecraft Java moved many item NBT fields into component syntax in 1.20.5+. NBTForge keeps those syntax families separate.

Can Core commands be chained together?

Yes. Add each command to Project, then copy the command pack when the setup needs multiple lines.

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.