Presets

Item presets

Custom name and lore preset for any item

Custom name and lore preset for any item is now a complete Give workflow instead of a single overlay image. Use this whenever the visible tooltip is the main point of the item: keys, relics, trophies, shop goods, and NPC rewards. The page treats the command as a reusable item definition, not a paste-only snippet, so the visible name, lore, component payload, output, and in-game delivery all have to agree. The text-component controls avoid hand-escaped JSON while still producing the exact custom_name and lore components. The final capture proves the generated item reaches a real hotbar before you connect it to a map script, loot path, or command-pack workflow.

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

Preset result

A readable quest item with a colored name, two lore lines, glint, and a custom_data marker.

Output

Custom name and lore command

/give @p minecraft:netherite_sword[custom_name={text:"Story Relic",color:"light_purple",italic:false},lore=[{text:"Recovered from the old keep",color:"gray",italic:false},{text:"Quest item",color:"gold",italic:false}],enchantment_glint_override=true,custom_data={story_relic:1b}] 1
Too long for Minecraft chat

The longest command line is 281 characters, 25 over the 256-character chat input limit. Pasting it into chat can truncate the line and make Minecraft report a syntax error even when the generated command is valid.

  • Use a Command Block: run /give @s command_block, place it, then paste this command into the block command field.
  • Use a .mcfunction for a reusable datapack: save the line without the leading slash at saves/<world>/datapacks/<pack>/data/<ns>/function/<name>.mcfunction with a minimal pack.mcmeta, run /reload, then run /function <ns>:<name>. Do not paste .mcfunction content into chat.

Preset screenshot

The text-component controls avoid hand-escaped JSON while still producing the exact custom_name and lore components.
The second shot highlights the fields that change the item tooltip or component payload.
The output shot keeps the final command and copy controls visible before testing.
The in-game shot confirms Story Relic named item is delivered by the same Give command.

Build the preset

  1. Open the Give workbench and confirm the target selector is appropriate for the world or command block.
  2. Set the item to netherite sword.
  3. Add the visible name and lore for Story Relic named item.
  4. Add only the components that matter for this item, then review the generated output.
  5. Copy the /give command for a smoke test, or save it to Project when it belongs to a larger workflow.
  6. Run the command in a creative test world and confirm the item appears in the player hand or hotbar.

Why Story Relic named item needs a preset

Use this whenever the visible tooltip is the main point of the item: keys, relics, trophies, shop goods, and NPC rewards.

The text-component controls avoid hand-escaped JSON while still producing the exact custom_name and lore components. That is the part a plain command snippet usually hides: the player-facing text, version-sensitive components, and copy-ready output all need to agree before the command leaves the workbench.

Use this preset as a review surface before the item enters a larger command chain. Confirm the tooltip tells players what the item does, confirm custom_data or other hidden components support command logic, and confirm the copied output still belongs to the selected Minecraft version. The in-game result is deliberately simple because it answers the first QA question: does this exact command deliver the item stack the article describes?

Version and component checks

Modern Java item commands use item components for many details that old tutorials wrote as NBT. Keep the selected version visible while editing, especially when the item uses names, lore, enchantments, rarity, custom model data, potion contents, or unbreakable state.

Long lore wraps badly in inventory. Keep each lore line short and store machine-readable state in custom_data instead.

After the command validates, run it in the same version family that will host the map or datapack. A command that copies cleanly can still be the wrong design if the component is unsupported, the selector targets too many players, or the item text promises behavior that the data does not enforce. Save stable variants in Project before adding scoreboard, loot, shop, NPC, or reset commands around them.

  • Use the workbench fields before editing raw command text.
  • Keep display text short enough for inventory tooltips.
  • Use custom_data for command logic instead of relying on visible names.

Where to use it next

Save a Project copy before adding enchantments, attributes, or predicates to the same item.

If the item will be reused, save it as a Project entry before adding scoreboard, loot table, NPC, or reset commands around it. That keeps the item definition auditable when the map grows.

For adjacent tooltip examples, compare the quest reward item preset, adventure map key item preset, and custom sword preset.

FAQ

Can I paste this Give command into chat?

Yes if the command length warning stays under the chat limit. If it grows past the limit, use a command block or a datapack function instead of pasting the full line into chat.

Can I change the item type after using this preset?

Yes. Change the item field first, then recheck every component. Some settings make sense for a netherite sword but not for every Minecraft item.

Why include an in-game item screenshot?

The screenshot confirms the command delivers a real item stack, not just a valid-looking string in the output panel.

Open this workflow

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