Minecraft Locator Bar Not Working? 9 Fixes

Why is my Minecraft Locator Bar not showing?

First confirm that another eligible player or entity exists, the game rule is enabled, and your receive range is above zero.

The Locator Bar does not replace the experience bar permanently. With nothing eligible to display, the normal XP bar stays visible. It can also return temporarily after you gain experience or close an experience-related screen, so wait a few seconds before treating that as a failure.

In an ordinary single-player world there is no other player waypoint to show. To test alone, give one living entity a positive waypoint_transmit_range, then face toward it.

• Confirm another player or transmitting living entity is present.
• Wait at least five seconds after gaining XP or closing an anvil or enchanting screen.
• Make sure you are looking within the Locator Bar's approximate 120-degree facing range.
• Continue with the version-specific game rule check below.

Check the correct Locator Bar game rule for your version

Java 1.21.11 and later use minecraft:locator_bar; Java 1.21.6 through 1.21.10 use the older locatorBar name.

Game rule IDs changed to namespaced snake_case identifiers in Java 1.21.11. This is why a command copied from an older 1.21.6 article can return an unknown-rule error on a current release even though the idea is correct.

Run the query command first. If it returns false, enable the rule with the matching true command. You need permission to query or change protected world settings on a server.

Check your waypoint receive range

A receive range of zero prevents that player from receiving waypoints, so the Locator Bar has nothing to display.

The waypoint_receive_range attribute belongs to the viewer. Players normally receive across the vanilla maximum range, but a command, data pack, plugin, or server menu can change the base value or add a modifier.

Query the effective value before overwriting it. If it is zero and you did not intend to disable reception, restore the vanilla player base value of 60,000,000. On a managed server, ask the administrator whether a plugin owns this setting before changing it.

Check whether the other player is hiding

Crouching, invisibility, certain worn heads, and spectator visibility rules can intentionally remove a player from other players' Locator Bars.

Ask the missing player to stand normally, remove invisibility, and take off any carved pumpkin or mob head used as a disguise. Players in Spectator Mode are normally hidden from non-spectators, while spectators can see one another.

These are vanilla hiding rules, not connection failures. If one player is missing while everyone else appears, check that player's state before changing a world-wide game rule.

• Release the crouch or sneak key.
• Remove Invisibility.
• Remove a carved pumpkin or mob head from the head slot.
• Compare the viewer and target game modes.

Check the sender's transmit range and tracked state

A player or mob must transmit a waypoint far enough for the viewer to receive it; ordinary mobs start with a transmit range of zero.

The waypoint_transmit_range attribute belongs to the sender. Players normally transmit across the vanilla maximum range, while other living entities do not appear until an operator gives them a positive range.

Use /waypoint list as a quick diagnostic for the currently tracked waypoints. For a mob test, select exactly one living entity and set an appropriate range. Do not use an unrestricted @e selector when a command expects one target.

Check permissions, dimensions, and server software

If the vanilla checks pass, verify the active dimension and ask whether the server, proxy, plugin, mod, or data pack changes Locator Bar behavior.

Run diagnostics in the dimension where the players are actually testing and confirm the server accepted each command instead of silently relying on chat history. On multi-world server software, game rules can be managed per world or dimension by the platform.

Plugins and data packs can add per-player toggles, range limits, team rules, or replacement waypoints. Reproduce the problem once on the same version in a clean vanilla world when possible. If vanilla works, the difference belongs to the server configuration rather than the browser tool or the base game rule.

• Read the exact red command error instead of retrying a different command blindly.
• Confirm the operator or command-block permission level.
• Test both players in the same world and dimension.
• Temporarily compare against an unmodified vanilla test world.