Datapack presets

Advancement reward preset guide

Advancement reward preset guide is now a complete Data Pack workflow instead of a templated command note. Use this preset when a map milestone should trigger a structured reward path instead of running a command every tick. Advancements are useful for one-time achievements, story steps, and kill milestones because criteria and reward function stay in one datapack resource. 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 workbench highlights the trigger, entity condition, reward function, namespace, and file path. Those fields need a deliberate review because a typo in the function id or resource path can make the advancement silently fail after `/reload`.

Read inEN RU DE ES PT 中文日本語 VI FR 한국어 ID PL TR

Preset result

An advancement resource that grants a reward function when the player clears the target encounter.

Output

Advancement reward JSON

data/nbtforge/advancement/story/clear_crypt.json
{
  "criteria": {
    "clear_crypt": {
      "trigger": "minecraft:player_killed_entity",
      "conditions": {
        "entity": [
          {
            "condition": "minecraft:entity_properties",
            "entity": "this",
            "predicate": {
              "type": "minecraft:wither_skeleton"
            }
          }
        ]
      }
    }
  },
  "rewards": {
    "function": "nbtforge:grant_crypt_reward"
  }
}

Preset screenshot

NBTForge Data Pack workbench configured for Advancement reward preset guide. — Start with the Data Pack controls that define the preset state.

Detailed Data Pack controls for Advancement reward preset guide. — The second shot highlights the setting or companion command that changes player-facing behavior.

Copy-ready output for Advancement reward preset guide. — The output shot keeps the final command or command pair visible before it enters Project.

Build the preset

Open the Data Pack workbench.
Select Advancement as the generator.
Set namespace and resource path for the story milestone.
Choose a trigger such as `player_killed_entity`.
Set the entity condition that marks the completed encounter.
Set Reward Function to the function that grants the prize.
Review the JSON output and save it with the function file path.

Why this Data Pack preset belongs in Project

Use this preset when a map milestone should trigger a structured reward path instead of running a command every tick. Advancements are useful for one-time achievements, story steps, and kill milestones because criteria and reward function stay in one datapack resource.

The workbench highlights the trigger, entity condition, reward function, namespace, and file path. Those fields need a deliberate review because a typo in the function id or resource path can make the advancement silently fail after `/reload`. 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

Advancements are not a replacement for every scoreboard. Use them for milestone-style triggers, and keep repeatable counters or per-room state in scoreboard objectives where they can be reset explicitly.

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

Pair this advancement with a reward function and the item modifier that shapes the final prize.

For the reward resource itself, continue with the item modifier custom reward preset or the function pack command chain 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.