Quick answer
Turn off the Minecraft Locator Bar for a whole world, only for yourself, or hide your own marker with the correct Java and Bedrock commands for current and legacy versions.
Which Locator Bar setting should you change?
Use the game rule for everyone, receive range for only what you see, transmit range for who can see you, and crouching for a temporary hide.
These controls affect different sides of the waypoint connection. Disabling the world game rule is the broadest option and affects everyone. A receive-range change belongs to one viewer, while a transmit-range change belongs to one sender.
Start with the narrowest control that solves the problem. This avoids turning the feature off for an entire server when only one player wants a cleaner HUD or temporary privacy.
Turn off the Locator Bar for the whole Java world
On current Java releases, set minecraft:locator_bar to false; on Java 1.21.6 through 1.21.10, use the legacy locatorBar name.
The game rule disables the Locator Bar for every player in that world. You need the appropriate operator or single-player command permission. Use the matching true command to restore it later.
Java 1.21.11 renamed game rules to namespaced snake_case IDs. Keeping both versions on this page prevents a current command from being copied into an older server, or an old locatorBar example from failing on 26.x.
/gamerule minecraft:locator_bar false/gamerule minecraft:locator_bar true/gamerule locatorBar false/gamerule locatorBar trueTurn off the Locator Bar only for yourself
Set your waypoint_receive_range to zero to stop receiving markers without changing the game rule for everyone else.
This is the correct vanilla Java control when one player does not want to see waypoint markers. It does not hide that player's own marker from other people; it only stops that player from receiving other waypoints.
Query the existing value first if a server uses custom ranges. The vanilla player base value is 60,000,000, but restoring that number can overwrite a deliberate server-specific base setting.
/attribute @s minecraft:waypoint_receive_range base set 0/attribute @s minecraft:waypoint_receive_range base set 60000000Ask the server owner before replacing a custom base value.Hide yourself from other players' Locator Bars
Crouch for temporary privacy, or set your waypoint_transmit_range to zero to stop broadcasting your marker until the value is restored.
Crouching is the simplest temporary vanilla hide and needs no command. Invisibility and supported head-slot disguises can also hide a player. A transmit-range value of zero is the persistent command-side control for that sender.
Changing transmit range does not turn off what you see. If you want both directions disabled, set both your receive and transmit ranges to zero, subject to the server's permissions and policies.
/attribute @s minecraft:waypoint_transmit_range base set 0/attribute @s minecraft:waypoint_transmit_range base set 60000000Record a custom server value before changing the base.Limit the Locator Bar distance instead of disabling it
Use a smaller receive range to limit what one player sees, or a smaller transmit range to limit how far away others can see that sender.
A limited range can be more useful than an all-or-nothing switch for minigames, PvP, events, and crowded servers. Receive and transmit limits both apply to the connection, so the effective result depends on the viewer and sender settings together.
The following 120-block examples are starting points. Replace 120 with the distance that fits the game design, within the allowed attribute range.
/attribute @s minecraft:waypoint_receive_range base set 120/attribute @s minecraft:waypoint_transmit_range base set 120Turn off the Locator Bar in Bedrock Edition
Use the world Multiplayer settings, or the version-appropriate Bedrock game rule when commands are enabled; Bedrock 26.30 replaced the old locatorbar boolean with playerWaypoints.
Bedrock and Java do not share the same waypoint command system. In current Bedrock 26.30+, playerWaypoints accepts off or everyone. Older Bedrock releases that shipped the Locator Bar used the locatorbar boolean game rule instead.
World owners can also change the Locator Bar option from the Multiplayer settings screen. Do not paste Java waypoint_receive_range or /waypoint commands into Bedrock; those Java controls are not cross-edition equivalents.
/gamerule playerWaypoints off/gamerule playerWaypoints everyone/gamerule locatorbar falseServer, Realm, and plugin considerations
The command must run with sufficient permission in the world being changed, and server software may add its own per-player controls or per-world configuration.
On Java servers, run the command as an operator, through the server console, or through an authorized command block or function. On managed multi-world platforms, confirm whether the game rule is stored separately for each world or dimension.
Plugins and data packs can expose safer player menus, preserve custom base ranges, or override vanilla behavior. If a command reports success but the result immediately changes back, look for a server component that reapplies its own setting.
Sources & verification
References used for this guide
Documented behavior, public identity conventions, and this site's reproducible calculations are kept distinct.