Presets

Item presets

How to make a custom sword preset in Minecraft

This preset turns the common "custom sword command" task into a complete Give workflow. It covers the item choice, custom name, lore, enchantment, glint override, output length, and a real in-game held-item screenshot so the result is not just a copied command string.

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

Preset result

A named Raid Blade diamond sword with visible lore, Sharpness V, and forced enchantment glint.

Output

Custom sword give command

/give @p minecraft:diamond_sword[custom_name={text:"Raid Blade",color:"aqua",bold:true,italic:false},lore=[{text:"Boss reward",color:"gray",italic:false}],enchantments={"minecraft:sharpness":5},enchantment_glint_override=true] 1

Preset screenshot

The first workbench shot shows the target selector, item choice, and output panel together.
Names and lore should be edited as components instead of hand-escaped JSON.
The output stays compact enough for chat while still carrying name, lore, enchantment, and glint data.
The capture confirms the same command delivers a visible custom sword to the player.

Build the preset

  1. Open the Give workbench and keep the target as @p for map-friendly testing.
  2. Set the item to Diamond Sword.
  3. Enter Raid Blade as the custom name and choose aqua with bold enabled.
  4. Add a lore line that explains the sword is a boss reward.
  5. Add Sharpness V and force the enchantment glint on.
  6. Copy the final /give command or save it to a Project reward pack.

Why edit text as components

Custom item names and lore often break when quotes are edited by hand. The Give workbench keeps the visible text, color, bold flag, and italic flag in separate controls, then generates the component output for the selected Java version.

That matters for swords because the display text is usually the player-facing part of the reward. A readable name and a short lore line make the item easier to recognize in inventories, loot tables, and command-pack reviews.

Glint and enchantment choices

The example uses Sharpness V because it is a familiar combat upgrade and it proves enchantment output is present. The glint override keeps the sword visually special even if you later change the enchantment list.

If the sword is meant as a cosmetic key or quest prop, remove the combat enchantment but keep a clear name, lore, and custom_data marker so map logic can identify it.

  • Use a short name for inventory readability.
  • Keep lore to one or two useful lines.
  • Save a Project copy before adding custom data or attributes.

Command delivery

This command is below the chat limit, so it can be pasted directly for a quick smoke test. For a real adventure map, save it into a Project or command pack so the reward item stays with the rest of the setup.

When converting it into boss loot, keep the same item component data and place it inside a loot table or item modifier workflow instead of rebuilding the sword from scratch.

For nearby item examples, compare the Sharpness sword preset, adventure map key preset, and Blaze Emperor boss loot preset.

FAQ

Can I change the sword to netherite?

Yes. Change the item field to Netherite Sword and recheck the output. The name, lore, enchantment, and glint settings can stay the same.

Why is italic disabled in the command?

Minecraft item text is often italic by default. Setting italic:false keeps the custom name and lore easier to read.

Can this become a boss drop?

Yes. Save the item command, then reuse the same component data in a loot table or boss reward preset.

Open this workflow

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