Presets

World presets

Waypoint preset for locator bars

Waypoint preset for locator bars is now a complete Waypoint workflow instead of a templated command note. Use this preset when a map needs visible navigation support without turning the objective into a long chat instruction. Waypoint commands are useful for lobby returns, quest markers, team routes, and testing paths where creators need to verify that the marker color and target selector are correct. 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 Waypoint workbench keeps the action, target selector, color, and style fields visible. That is the real value of the preset: the command is short, but the map needs a clear decision about who receives the marker and what color communicates the route.

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

Preset result

A waypoint command styles the player locator marker so navigation feedback is intentional.

Output

Locator bar waypoint command

/waypoint modify @s color gold

Preset screenshot

Start with the Waypoint 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.
A waypoint command styles the player locator marker so navigation feedback is intentional.

Build the preset

  1. Open the Waypoint workbench.
  2. Set action to `modify` when changing a tracked marker.
  3. Set target selector to the player or entity that owns the locator marker.
  4. Choose a readable color such as gold for the active objective.
  5. Review the generated `/waypoint` output and save it beside routing commands.
  6. Run the command in-game and confirm the locator feedback belongs to the intended target.

Why this Waypoint preset belongs in Project

Use this preset when a map needs visible navigation support without turning the objective into a long chat instruction. Waypoint commands are useful for lobby returns, quest markers, team routes, and testing paths where creators need to verify that the marker color and target selector are correct.

The Waypoint workbench keeps the action, target selector, color, and style fields visible. That is the real value of the preset: the command is short, but the map needs a clear decision about who receives the marker and what color communicates the route. 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

Waypoint behavior depends on the target and the client version. Keep the selector narrow while testing, and save a fallback title or actionbar hint when the map has players on versions where locator UI behavior may differ.

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 after lobby teleport or spawn setup so players get a navigation cue at the correct point in the flow.

For adjacent navigation commands, compare the teleport lobby return preset and adventure map starter command pack.

FAQ

Can I paste this Waypoint 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 include a result capture for a utility-style preset?

The result capture proves the command changed visible world, HUD, routing, or feedback state in Minecraft instead of only looking correct in the output panel.

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 Waypoint workbench, then adjust the preset fields for your world.