Presets

Item presets

Sharpness sword preset with lore and glint

This preset focuses on the exact search intent behind a Sharpness sword command: a weapon that is visibly enchanted, named clearly, and safe to copy. The screenshots show the Give workbench fields, the component output, and the in-game sword so the command is tied to a real result.

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

Preset result

A Sharpness V diamond sword whose custom name, lore, and glint are all visible in the command output and in-game result.

Output

Sharpness sword give command

/give @p minecraft:diamond_sword[custom_name={text:"Sharpness V Blade",color:"gold",italic:false},lore=[{text:"Glint stays visible",color:"gray",italic:false}],enchantments={"minecraft:sharpness":5},enchantment_glint_override=true] 1

Preset screenshot

The setup keeps the sword, target, and output visible while you tune the item.
The name and lore are generated as item components for the selected Java version.
The final command stays under the chat limit and includes the visible enchantment result.
The capture verifies the generated command gives the player the expected sword.

Build the preset

  1. Open the Give workbench and select Diamond Sword.
  2. Set the custom name to Sharpness V Blade.
  3. Use a readable color such as gold and disable italic text.
  4. Add one lore line explaining that the glint stays visible.
  5. Add Sharpness level 5 in the enchantment controls.
  6. Force enchantment glint on and copy the generated command.

Keep the combat intent obvious

A Sharpness sword should communicate its role immediately. The custom name tells the player what the item is, the lore explains why it is special, and the enchantment data makes the weapon actually behave like a combat reward.

The preset avoids overloading the sword with too many fields. That keeps the output short, makes the screenshot easier to inspect, and leaves room for later additions such as attributes or custom_data.

Glint as a visual check

The enchantment glint is not just decoration. It is a fast in-game confirmation that the item is not a plain diamond sword. If the sword appears without glint, inspect the enchantment field and the version target before changing unrelated settings.

For cosmetic swords, you can keep glint on even with different enchantments, but make sure the lore does not promise combat stats that the command no longer provides.

Reuse in rewards

This sword works as a direct give reward, but it can also become a boss drop, advancement reward, or command-pack line. Save it to a Project before moving it into a multi-command workflow.

When you use it in a function, remove the leading slash from the give line inside the `.mcfunction` file and trigger the function with a short `/function` command.

For related reward setups, compare the custom sword preset and the Blaze Emperor boss loot preset.

  • Direct test: paste the /give command.
  • Reusable map reward: save to Project.
  • Datapack delivery: put the slash-free line in a function.

FAQ

Can I raise Sharpness above level 5?

You can edit the level, but high or unsupported levels may depend on the version and server rules. Test the result in the target world.

Why does the command include glint override?

The override makes the visual glint explicit, which is useful when the sword is a reward and players should recognize it immediately.

Can I add attributes later?

Yes. Save this preset first, then add attributes in a follow-up edit and review the output diff.

Open this workflow

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