/summon
op 2Entities/summon spawns an entity at a position, and everything interesting about it lives in the NBT tag that follows: health, equipment, custom names, AI flags and riders. That tag has to be valid SNBT on a single line, which is where most /summon commands go wrong.
- Entity is required.
- Where cannot be used without Entity, because the game reads these in order.
Entity is required.
~ ~ ~
Where cannot be used without Entity, because the game reads these in order.
Health, equipment, custom name, AI flags — anything the entity stores
Examples
- Simple mob
/summon zombie ~ ~ ~ - Named, still armour stand
/summon armor_stand ~ ~ ~ {NoGravity:1b,Invisible:1b} - Lightning
/summon lightning_bolt ~ ~ ~
Common questions about /summon
›How do I summon a mob that does not move or make noise?
Add {NoAI:1b,Silent:1b} to the entity data. NoAI freezes the mob in place while keeping it rendered and hittable.
›How do I stack mobs on top of each other?
Nest a Passengers list: {Passengers:[{id:"minecraft:skeleton"}]}. Each rider is a full entity object, so it can carry its own Passengers in turn.
›Why does my summoned mob disappear?
Mobs despawn when far from a player unless they are marked persistent. Add {PersistenceRequired:1b}, or give it a custom name, which has the same effect.
›Does /summon accept item components for equipment?
From 1.20.5, gear inside an entity uses the component format — {ArmorItems:[{},{},{},{id:"minecraft:diamond_helmet",count:1,components:{…}}]}. Before then it used the old tag NBT.