Presets

Datapack presets

Recipe preset for custom crafting

Recipe preset for custom crafting is now a complete Data Pack workflow instead of a templated command note. Use this preset when a map item should be craftable through datapack recipes rather than handed out by command. Recipes are good for hub unlocks, puzzle rewards, and progression items because the inputs and result stay reviewable as JSON. 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 Data Pack workbench keeps recipe type, category, ingredients, result id, result count, namespace, and resource path in one view. That prevents a common mistake where the JSON output looks valid but is saved under the wrong recipe path.

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

Preset result

A custom shapeless recipe resource for crafting an adventure-map key item.

Output

Custom recipe JSON

data/nbtforge/recipe/keys/ancient_key.json
{
  "type": "minecraft:crafting_shapeless",
  "category": "misc",
  "ingredients": [
    "minecraft:echo_shard",
    "minecraft:gold_ingot"
  ],
  "result": {
    "id": "minecraft:tripwire_hook",
    "count": 1
  }
}

Preset screenshot

Start with the Data Pack 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 Data Pack and choose Recipe.
  2. Select a recipe type, usually `crafting_shapeless` or `crafting_shaped`.
  3. Set namespace to `nbtforge` and choose a clear resource path.
  4. Fill ingredient ids and the result item id.
  5. Set result count deliberately.
  6. Review the generated JSON and copy the path.
  7. Test the recipe after `/reload` in the target version.

Why this Data Pack preset belongs in Project

Use this preset when a map item should be craftable through datapack recipes rather than handed out by command. Recipes are good for hub unlocks, puzzle rewards, and progression items because the inputs and result stay reviewable as JSON.

The Data Pack workbench keeps recipe type, category, ingredients, result id, result count, namespace, and resource path in one view. That prevents a common mistake where the JSON output looks valid but is saved under the wrong recipe path. 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

A recipe controls crafting only. If the result needs a custom name, lore, or custom data, use a reward command or item modifier after crafting because vanilla recipe results cannot express every component workflow in the same way.

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

Save the recipe with the item or reward preset that explains what the crafted key unlocks.

For datapack neighbors, compare the datapack namespace preset and predicate conditional loot preset.

FAQ

Can I paste this Data Pack 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 Data Pack workbench, then adjust the preset fields for your world.