/waypoint Command Generator
Pick what you want to change, get a command that actually runs. Every branch below is built from the command's real grammar, including the rule that trips most people up: the target must resolve to exactly one entity.
Syntax verified againstthe /waypoint command reference
Game version
The grammar has not changed since 1.21.6 (snapshot 25w17a). Everything from 1.21.6 through 26.3 accepts the same command.
/waypoint needs permission level 2 (operator) and cheats enabled. In singleplayer, open the world to LAN with cheats on, or run it from a command block.
1. What do you want to do?
One of the 16 built-in color names. Overrides both the UUID-derived default and any team color.
2. Who is it for?
Must resolve to exactly one entity, and that entity must be a waypoint transmitter — a player, a mob or an armor stand.
@s is the entity running the command — a safe default when a player sets their own color.
3. Pick the color
Start from a player's default color
Java gives every entity a default marker color derived from its UUID. Look one up, then nudge it instead of guessing from a blank picker.
Your command
/waypoint modify @s color redKeep it on for the chat box. Turn it off for command blocks and datapack functions, which reject the slash.
Needs permission level 2 and cheats. Java Edition only.
Every branch of the command
| Syntax | What it does |
|---|---|
waypoint list | Lists every tracked waypoint, each drawn in its own color. |
waypoint modify <target> color <color> | Sets one of the 16 named colors. |
waypoint modify <target> color hex <RRGGBB> | Sets any RRGGBB color, written without a #. |
waypoint modify <target> color reset | Drops the override and returns to the default color. |
waypoint modify <target> style set <style> | Points the marker icon at a waypoint_style from a resource pack. |
waypoint modify <target> style reset | Returns the marker icon to minecraft:default. |
What this Minecraft waypoint command generator writes
/waypoint is the only vanilla command that touches the Locator Bar directly, and it does less than most people expect: it does not create waypoints. It re-skins waypoints that already exist because some entity is transmitting one. This Minecraft waypoint command generator assembles the six valid forms — list, color <name>, color hex <RRGGBB>, color reset, style set <style> and style reset — with the arguments in the order the parser wants them.
The target is an entity selector, not a coordinate, and it has to resolve to exactly one living entity. @e[type=creeper] fails the moment a second creeper exists; @e[type=creeper,limit=1] does not. Setting a color on an entity whose waypoint_transmit_range is 0 makes it show up in waypoint list and nowhere else. The full argument reference is on the Minecraft waypoint command page.
Version rules that break a copied command
Most commands that “stopped working” were written for a different version. Three changes matter, and the Minecraft waypoint command generator above accounts for all three once you pick a version.
1.21.6 introduced the feature.
The Locator Bar and
/waypointshipped in Java Edition 1.21.6. Snapshots 25w15a and 25w16a had the command but not waypoint styles, which is why this Minecraft waypoint command generator disables the style options on those versions.Java 26.2 tightened the color argument.
From 26.2 the named colors are accepted only in lowercase with underscores.
dark_purpleworks;DarkPurpleanddarkpurpleare rejected outright. Command blocks and functions written for 1.21.x start failing after an update for exactly this reason, and the same rule now applies toteam modify <name> color.The game rule was renamed.
locatorBarbecamelocator_barin snapshot 25w44a, released in 1.21.11, when every game rule moved to a snake_case resource location. On 1.21.6 through 1.21.10 use/gamerule locatorBar false; from 1.21.11 use/gamerule locator_bar false. The Locator Bar gamerule page lists all of them, Bedrock included.
Choosing a color worth overriding with
Every player already has a default color derived from their UUID — java.util.UUID.hashCode() folded down to three bytes, then shaded to 90%. It is stable forever, so an override is only worth typing when the default is genuinely a problem. Two checks before you commit to one.
See what the default actually is.
The Locator Bar color finder computes any Java player's default from a username or UUID, including the unshaded value and the nearest of the sixteen named colors — a good starting point if you want an override that still looks like that player. The arithmetic is documented on the Minecraft UUID color page.
Check it against the rest of the party.
An override that collides with a teammate solves nothing. Run the whole line-up through the locator bar color checker first, then override the one color causing the clash.
Named colors are the safer choice for anything that has to survive a version bump. color hex gives you the exact value but no autocomplete, and a typo there fails quietly.
Waypoint command questions
Do I need to be an operator?
Yes — permission level 2 and cheats enabled, or run it from a server console, a command block or a function. There is no client-side setting that changes a waypoint color.
Nothing happened when I ran the command.
Usually the target. The selector has to match exactly one living entity, and that entity has to be transmitting a waypoint for the color to appear on the bar at all. On 26.2 and later, check the color spelling too — lowercase with underscores.
Does any of this work on Bedrock?
No. There is no /waypoint command in Bedrock at any version. Bedrock assigns marker colors randomly per session, and only an add-on using the scripting API can set one. The Bedrock Locator Bar page has the details.
How do I undo an override?
/waypoint modify <target> color reset drops the override and the marker returns to its UUID-derived default. style reset does the same for icon styles. This Minecraft waypoint command generator can build both.