Presets

Item presets

Java 1.21 item component preset guide

Java 1.21 item component preset guide is now a complete Give workflow instead of a templated command note. Use this preset when the target world is already on the Java 1.21 syntax family and the item should be written as components from the start. It is the current-output counterpart to the Java 1.20.4 legacy NBT preset. The article keeps the setup fields, output review, Project placement, and result capture together so the command is easy to audit before it becomes part of a map setup, event trigger, or reusable command pack. The Give workbench should make the component payload visible before the command is copied. Custom name, lore, glint, and custom_data are reviewed as component output, which keeps the article focused on current Java behavior instead of old NBT examples.

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

Preset result

A current Java 1.21 item component command with name, lore, glint, and custom_data.

Output

Java 1.21 component item command

/give @p minecraft:trial_key[custom_name={text:"Vault Trial Key",color:"gold",italic:false},lore=[{text:"Java 1.21 component item",color:"gray",italic:false}],custom_data={trial_key:"vault_alpha"},enchantment_glint_override=true] 1

Preset screenshot

Start with the Give controls that define the preset state.
The second shot highlights the setting or companion command that changes player-facing behavior.
The output shot keeps the final command or command pair visible before it enters Project.

Build the preset

  1. Open Give with Java 1.21 selected.
  2. Choose the base item that matches the map reward or key.
  3. Add component-backed custom name and lore.
  4. Set glint or custom_data only when the workflow needs it.
  5. Review the output for bracketed component syntax.
  6. Save the command with the target version clearly named.

Why this Give preset belongs in Project

Use this preset when the target world is already on the Java 1.21 syntax family and the item should be written as components from the start. It is the current-output counterpart to the Java 1.20.4 legacy NBT preset.

The Give workbench should make the component payload visible before the command is copied. Custom name, lore, glint, and custom_data are reviewed as component output, which keeps the article focused on current Java behavior instead of old NBT examples. A copied command is only useful when the surrounding assumptions are visible: selector scope, world state, order inside the pack, and the exact output that will be pasted into Minecraft. Treat this preset as a checkpoint where those details can be reviewed before the command leaves NBTForge.

The gallery is structured around that review. The first shot shows the workbench state, the second shot calls out the field or companion module that changes player-facing behavior, and the output shot keeps the command or command pair visible. When the preset has a visible result, the in-game capture confirms the same idea in a restored test world rather than relying on a generic overlay.

Testing and scope checks

Component output is version-sensitive. Keep the selected target version with the saved Project entry so another creator does not reuse the command in an older server without checking syntax first.

Run the first smoke test with a narrow selector and a clean world state. Environment, utility, routing, and feedback commands can look harmless, but they often affect every player or the whole world. Confirm the command changes only the intended state, then save the exact output beside the setup or follow-up lines that explain why it exists.

If the command becomes part of a function file or command-block chain, test the copied artifact, not only the live workbench state. That catches stale selectors, wrong command order, missing setup lines, and effects that only appeared to work because a previous test left state behind.

  • Keep selectors narrow until the full pack is reviewed.
  • Place world setup before encounter-specific overrides.
  • Save feedback commands next to the state change that triggers them.

Where to go next

Use this component item as the modern replacement when retiring legacy Java item NBT commands.

For migration context, compare the Java 1.20.4 item NBT preset and cross-edition item preset checklist.

FAQ

Can I paste this Give command into chat?

Usually yes for a one-command smoke test if the selector is safe and the line is short. For repeatable map behavior, save it to Project and copy the ordered pack or function-style output.

Why is this gallery UI-only?

This preset produces JSON, project organization, or review workflow rather than a visible in-world object. The useful proof is the workbench state, output, and Project placement.

What should I check before sharing this preset?

Check selector scope, command order, target version, and whether the command belongs in setup, encounter logic, feedback, or cleanup. Those categories decide where it should sit in a Project pack.

Open this workflow

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