Core
Core command guide: Summon, Give, Item, and Blocks
7 min read · Updated May 15, 2026
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.
Goal
A clean core command workflow for entities, items, and blocks.
Annotated screenshots


Step-by-step guide
- Use Summon when the root of the command is an entity.
- Use Give when the root of the command is an item stack in a player inventory.
- Use Item for slot modification commands after the target already has an inventory.
- Use Blocks for setblock and fill workflows that change the world.
- 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.
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.