Presets

Summon presets

Item frame item preset workflow

Item frame item preset workflow is now a full Summon workflow with the root entity, passenger relationship, output review, and in-game result shown together. Use this when an item should be visible in the world as a display prop instead of delivered to the player inventory. The page treats the summon line as encounter data that needs visual review, not only syntax validation. The gallery keeps the workbench state beside the spawned result so the root entity, passenger stack, equipment, and final output can be inspected before the command becomes an encounter trigger.

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

Preset result

An item frame entity holding a named sword for reward displays and map showcases.

Output

Item frame item display command

/summon minecraft:item_frame ~ ~ ~ {Facing:2b,Fixed:1b,Item:{id:"minecraft:diamond_sword",Count:1b,components:{"minecraft:custom_name":{text:"Display Blade",color:"aqua",italic:false}}},Tags:["display_frame"]}

Preset screenshot

Start with item_frame as the root entity so the preview and output agree.
The second shot shows the embedded item NBT and fixed-frame detail.
The output shot keeps the final /summon command and copy controls visible before testing.
The in-game result confirms item frame display with a custom sword renders as intended in a clean capture world.

Build the preset

  1. Open the Summon workbench and set the root entity to item_frame.
  2. Add or review the passenger and equipment details that make the item frame display with a custom sword readable in-game.
  3. Check the preview and passenger tree before copying the command.
  4. Review the output panel for the final /summon line and command length.
  5. Copy the command for a smoke test, or save it to Project before adding follow-up commands.
  6. Run the command in a clean test world and confirm the in-game result matches the workbench tree.

Why item frame display with a custom sword needs a preset

Use this when an item should be visible in the world as a display prop instead of delivered to the player inventory.

The useful part is the structure: item_frame owns the summon position, while the visible passenger, equipment, or display data gives the preset its encounter identity. Keeping that tree visible prevents bracket mistakes before the command leaves the workbench.

Use the preset when the encounter should be easy to audit later. The workbench screenshot records which entity owns movement and collision, the second screenshot records the passenger or gear detail, and the output screenshot keeps the generated /summon line visible. The in-game capture then confirms Minecraft renders the same relationship, which is the check that a text-only example cannot provide.

Testing and version details

Item frames need placement context and direction. Test the frame against the intended block face before using it in a decorated room or reward wall.

Run the first test in an open Java world and watch the command length warning. Compact rider presets can be pasted directly, while longer boss or equipment variants should move into command blocks or datapack functions.

Keep the first smoke test small before attaching effects, loot, sounds, or scoreboards. Hostile passengers may move, burn, despawn, or behave differently by dimension and difficulty, so confirm the basic rider or equipment stack under controlled conditions. Once the visual result is stable, add tags and follow-up commands that target those tags rather than relying on display names or nearby selectors.

  • Keep the root entity and passenger roles distinct.
  • Use tags before adding cleanup or follow-up commands.
  • Test difficulty and dimension behavior before publishing the encounter.

Where to go next

Pair the frame with display entity labels, particles, or a nearby reward command when building a showcase.

For related display options, compare the item display showcase preset and glow item frame preset.

FAQ

Can I paste this item frame display with a custom sword command into chat?

Use the command length warning as the decision point. If the generated line is under the chat limit, a quick chat test is fine; otherwise move it to a command block or datapack function.

Does this work in Bedrock Edition?

Not as a Java Passengers command. Bedrock needs a separate ride workflow because it cannot embed the same recursive Java passenger NBT.

Why include an in-game screenshot?

The screenshot confirms the passenger tree or entity setup renders correctly in Minecraft, not only in the workbench preview.

Open this workflow

Start from the related Summon workbench, then adjust the preset fields for your world.