Locator Bar

Minecraft Locator Bar Not Working: 14 Fixes

Why the Minecraft Locator Bar shows nothing — wrong gamerule name, zeroed receive range, hidden players, version mismatch — with the command to fix each.

Last updated: 2026-07-23

"The locator bar is not working" almost never means the feature is broken. It means one of about a dozen specific conditions is true, and each one has a different fix. The list below is ordered by how often it turns out to be the culprit, and every entry states the symptom, the underlying cause, and the exact command or setting that resolves it.

Before working through it, three questions eliminate most cases in under a minute:

  1. Is anyone else actually in the world? With no other players present the experience bar simply behaves normally. The locator bar never appears in a solo single-player world.
  2. What version are you on? The game rule name changed in Java Edition 1.21.11 and again on Bedrock in 26.30. A command copied from a 2025 tutorial will fail on a 2026 client.
  3. Are you facing them? The bar only covers about 120 degrees of your camera's facing. Someone directly behind you is not drawn.

If none of those settle it, start at fix 1.

Fix 1 — Nobody else is in the world

Symptom. The experience bar looks completely normal. No dots ever appear, in any direction, at any distance.

Cause. The locator bar is a multiplayer HUD element. Mojang's 25w17a changelog puts it plainly: if there are no other players in the world, the experience bar displays as normal. There is nothing to draw.

Fix. Open the world to LAN (Esc then "Open to LAN") or join a server with at least one other player online. If you only want to confirm the feature is alive, a second account or a friend joining for thirty seconds is enough. There is no test mode and no single-player preview.

Fix 2 — The game rule is off, or you are typing the wrong name for your version

Symptom. /gamerule locatorBar true returns "Unknown game rule", or it succeeds but nothing changes.

Cause. The identifier has been renamed twice on Java. In snapshot 25w15a it was useLocatorBar. From 25w17a through 1.21.10 it was locatorBar. In 1.21.11 (released 9 December 2025) Mojang moved all game rules into a registry and, in their own words, renamed them "from their previous camel case names to resource locations in snake case". Since then the rule is locator_bar, full identifier minecraft:locator_bar.

Fix. Match the name to your version:

  • 1.21.6 through 1.21.10 — /gamerule locatorBar true
  • 1.21.11 and every later release, including 26.1 and 26.2 — /gamerule locator_bar true

The rule is a boolean defaulting to true, so if it is off someone turned it off. Setting it to false removes all existing waypoints from all players immediately, which is why the bar can vanish server-wide the instant an operator runs the command.

On Bedrock Edition the equivalent is /gamerule playerwaypoints everyone from version 26.30 onward. Before 26.30 it was the boolean /gamerule locatorbar true. If you are on 26.30 or later and locatorbar is rejected, that is the reason — the boolean rule was removed, not deprecated. Worlds are migrated automatically: true becomes everyone, false becomes off.

Fix 3 — Your version does not have the feature yet

Symptom. The game rule does not exist at all, no matter which spelling you try. /waypoint is not in the command list.

Cause. The locator bar shipped in Java Edition 1.21.6 (17 June 2025) and Bedrock Edition 1.21.90. Anything older simply does not have it. On Java it was also present in snapshots 25w15a and 25w16a only behind an experimental data pack, which was removed 14 days after it was added and never reached a release build.

Fix. Update. On a server, the server version is what decides: a 1.21.11 client connected to a 1.21.5 server gets no locator bar. Check the server jar, not just the launcher profile. On Bedrock, everyone in a session needs a version that has the feature; a lagging console or mobile client that has not applied its update will not show the bar.

Fix 4 — Your own receive range is zero

Symptom. Other players can see each other fine. You see nothing, ever, even standing next to someone. The game rule is on.

Cause. The minecraft:waypoint_receive_range attribute controls how far a player accepts incoming waypoints. Its player base value is 60,000,000, but a data pack, plugin, map, or an earlier experiment of your own may have set it to 0. Mojang documents that a player with a receive range of zero receives nothing at all — effectively a per-player off switch.

Fix. Check it, then restore it:

  • Check — /attribute @s minecraft:waypoint_receive_range get
  • Restore — /attribute @s minecraft:waypoint_receive_range base set 60000000

Do not "reset" it by setting 0, and do not assume the generic default of 0.0 shown in attribute tables is what players ship with. The generic default is 0.0; the player base value is 60,000,000. Those are two different numbers and confusing them is a common way to lock yourself out of your own bar.

Modifiers stack on top of the base value, so if a plugin is applying a multiplier the base-set above will not be enough — you also need the plugin to stop applying it.

Fix 5 — The other player's transmit range is too small, or zero

Symptom. One specific player never appears, or appears only when they are very close and vanishes at a distance that is nowhere near your view distance.

Cause. minecraft:waypoint_transmit_range decides how far away an entity can still be seen as a waypoint. Player base value is 60,000,000, but Mojang's own examples encourage setting it low — base set 80 limits a player to 80 blocks. Minigame maps and privacy plugins do exactly this.

Fix. Have them check and restore their own value:

  • Check — /attribute @s minecraft:waypoint_transmit_range get
  • Restore — /attribute @s minecraft:waypoint_transmit_range base set 60000000

Both ranges must be satisfied for a dot to render. A transmitter at 80 blocks and a receiver at 60,000,000 still lose each other past 80 blocks. Test at point-blank range first: if the dot appears when you stand on top of each other and disappears as you walk away, it is a range setting, not a visibility setting.

Fix 6 — They are hiding, deliberately or not

Symptom. A player disappears from the bar while clearly still online and nearby. They may reappear when they stop moving, or when they change armor.

Cause. Four states zero out a player's transmit range:

  • Sneaking. Applied as the modifier minecraft:waypoint_transmit_range_crouch, value -1.0, operation add_multiplied_total — applied on crouch, removed on release.
  • A head item worn in the head slot. Carved Pumpkin, Skeleton Skull, Wither Skeleton Skull, Player Head, Zombie Head, Creeper Head, Dragon Head, and Piglin Head.
  • The Invisibility effect, via minecraft:effect.waypoint_transmit_range_hide, also -1.0 add_multiplied_total.
  • Spectator mode, covered separately in fix 7.

Fix. There is nothing to repair — this is the feature working. Have them stand up, take the pumpkin off, and drink milk. The carved pumpkin case is the sneaky one, because plenty of players wear one permanently to avoid enderman aggro and never connect it to disappearing from the bar. Because these modifiers multiply the total, they override any base value: a player sneaking with a base transmit range of 60,000,000 is still at zero, and /attribute ... base set cannot cancel them.

Fix 7 — Spectator mode asymmetry

Symptom. A moderator or a dead player in spectator mode is invisible to everyone in survival, but other spectators can see them perfectly. Or: you are spectating and see dots nobody else reports.

Cause. Documented, intentional behavior. Spectators are not shown on the locator bar of non-spectators; spectators are visible to each other.

Fix. Switch out of spectator mode (/gamemode survival) if you want to be tracked. If you are debugging someone else's report, confirm their game mode before assuming anything is broken — this is the single most common false bug report about the feature.

Fix 8 — They are outside the 120-degree arc, or you are misreading the arrows

Symptom. Dots appear and disappear as you turn. A player you know is close by is missing until you spin around.

Cause. Waypoints are drawn only when the camera faces within roughly 120 degrees of the target. The bar is a slice of your field of view, not a compass with a full 360-degree readout. Vertical offset is shown only as a small up or down arrow on the indicator; there is no elevation number.

Fix. Turn slowly through a full circle before concluding a player is missing. If you see an arrow on a dot, the target is significantly above or below you — a player directly beneath you in a cave sits at the center of the bar with a down arrow, which is easy to mistake for someone standing next to you.

Also worth knowing: the third-person front camera had a bug in this area, MC-296542, where waypoints did not adjust to the flipped view. It was fixed in 25w17a, so if you are on an old snapshot, that is a real bug rather than a misreading.

Fix 9 — The bar is being replaced by the experience bar

Symptom. The bar works but flickers away for a few seconds at a time, especially while mining, smelting, or enchanting.

Cause. The locator bar occupies the same HUD slot as the experience bar and yields to it. When your XP changes, or when you close an anvil or enchanting table GUI, the locator bar is hidden for 100 ticks — 5 seconds — before returning.

Fix. Nothing to fix; this is intended. If you need continuous tracking during an XP-heavy activity, stop gaining XP for five seconds. Separately, check you have not hidden the whole HUD: F1 on Java toggles the entire HUD including the locator bar, and Bedrock Edition has a "Hide HUD" option. Neither edition has a client-side setting that hides only the locator bar.

Fix 10 — The /waypoint command fails or does nothing

Symptom. /waypoint modify ... returns an error, or reports success while the dot stays its old color.

Cause. /waypoint is Java Edition exclusive, requires permission level 2, and requires cheats to be enabled. Four further constraints apply:

  • The selector must resolve to exactly one entity. @e[type=creeper] fails when more than one creeper exists.
  • The target must be a waypoint transmitter — a living entity (player, mob, or armor stand) with a transmit range above zero.
  • Since Java Edition 26.2 (16 June 2026), color names must be lowercase with underscores. Only dark_purple is accepted; darkpurple and DarkPurple are rejected. This also applies to /team modify ... color.
  • Hex colors are 6-digit RRGGBB, for example FF0000 or 6495ED.

Fix. Work through them in order:

  • Confirm you are an operator, or that cheats are on.
  • Add limit=1 to any @e selector — /waypoint modify @e[type=creeper,limit=1] color hex 00FF00.
  • Lowercase every color name if you are on 26.2 or later — /waypoint modify Steve color light_purple.
  • If the entity is a mob, give it a transmit range first: /attribute @e[type=creeper,limit=1] minecraft:waypoint_transmit_range base set 200.

If you are copying commands from a tutorial published before June 2026, assume the color casing is wrong. The locator bar waypoint command generator emits syntax that matches the version you pick, which sidesteps this entirely.

Fix 11 — waypoint list shows everything as white

Symptom. You run /waypoint list to audit colors and every entry comes back white, even though the bar clearly shows several different colors.

Cause. This is documented behavior, not a fault. waypoint list prints each entry using its explicitly set waypoint color. If no color has been set with /waypoint modify, the output is white regardless of the color the game actually chose or the player's team color.

Fix. Stop using waypoint list as a color audit — it cannot tell you a player's default color. On Java the default is derived from the player's UUID and is stable forever, so you can look it up out-of-game instead: the Minecraft locator bar color finder resolves a username or UUID to its default dot color, and the locator bar color checker lines up a whole party at once so you can spot two players who will be indistinguishable in a fight.

Fix 12 — A team color or an explicit color is overriding what you expect

Symptom. A player's dot is not the color you calculated, or a whole group suddenly turned the same color.

Cause. Two overrides sit above the default. A player or mob on a scoreboard team with a color uses the team color. An explicit /waypoint modify ... color sits above even that. Both are working as designed and both are easy to forget about on a server where an admin set them up months ago.

Fix. Return the waypoint to its default with /waypoint modify <player> color reset — note that reset returns it to the default, which may still be the team color. To lose the team color as well, remove the player from the team (/team leave <player>) or clear the team's color. On Bedrock Edition there is no team coloring and no /waypoint, so this class of problem does not exist there.

Fix 13 — A resource pack has broken the icons

Symptom. Waypoints render as the black-and-magenta missing-texture square, or as invisible or malformed icons.

Cause. Waypoint icons come from hud/locator_bar_dot/ — the directory textures/gui/sprites/hud/locator_bar_dot — and the style definitions live in the waypoint_style/ asset directory. A resource pack built for an older version, or one missing those sprites, produces broken icons. Separately, the game does not validate style names: /waypoint modify <target> style set something_that_does_not_exist gives you a missing texture instead of an error.

Fix. Disable resource packs and check with vanilla assets. If the bar is fine without the pack, the pack needs updating. If a command set a bad style, clear it with /waypoint modify <target> style reset. The vanilla default style is minecraft:default, with near_distance 128 and far_distance 332.

Fix 14 — Server software, plugins, and proxies

Symptom. The bar works in single player over LAN but not on your server, or it works on one server and not another running the same version.

Cause. Waypoint broadcasting is server-authoritative: Mojang describes it as a "Server-authoritative Waypoint broadcasting system", where the server manages the connections between waypoints and players. That means server software has complete control. Third-party plugins exist specifically to strip, gate, or per-player toggle the locator bar on Paper and Spigot, and any of them can be active without your knowledge. Proxied networks add another layer, since the backend server your session lands on is the one whose game rule applies.

Fix. This one is on the server side, and it is worth being clear that plugin behavior is not documented by Mojang:

  • Confirm the game rule on the backend server you are actually connected to, not the lobby.
  • Check the plugin list for anything that mentions locator, waypoint, or vanish.
  • Test with plugins disabled if you own the server. If the bar returns, bisect the plugin list.
  • On a rented host, ask support which build they run — some hosts ship a modified jar.

Realms and Bedrock Featured Servers are managed environments; if the setting is not exposed in the world options, there is no supported way to change it from a client.

One thing we cannot confirm

A frequent report is that a player in the Nether or the End does not appear on an Overworld locator bar. Waypoint broadcasting is server-side and operates per level, and the community consensus is that waypoints do not cross dimensions — but Mojang has not documented this, and neither the Minecraft Wiki's Locator Bar page nor the 25w17a, 1.21.6, 26.1 or 26.2 changelogs state it either way. We are not going to present it as fact. If you are debugging a missing player, do rule dimensions out by having both parties stand in the same one, but treat "different dimension" as an observation rather than a documented rule.

A diagnostic sequence you can paste

Run these in order, in a world where you have operator permission, with one other player online and standing next to you:

  1. /gamerule locator_bar — on 1.21.10 or earlier use /gamerule locatorBar. Expect true.
  2. /attribute @s minecraft:waypoint_receive_range get — expect 60000000.
  3. /attribute @s minecraft:waypoint_transmit_range get — expect 60000000.
  4. Have the other player run steps 2 and 3 on themselves.
  5. /gamemode survival for both of you, and have them stand up and take off any head item.
  6. Turn a slow full circle and watch for a dot.
  7. /waypoint list — remember every entry prints white unless a color was explicitly set, so use it to confirm presence, not color.

If step 7 lists the other player and step 6 still shows nothing, the problem is client-side: check F1, check resource packs, and check that you are not gaining XP in a loop.

Related reading

References