mojira.dev
MC-179057

/locate executes differently in command blocks than players

if you execute the command /locate, it will return a different structure location than if a command block runs it

Comments 3

Unable to reproduce, please check if this is still an issue in 1.16 Pre-release 2 or later.

Edit: Actually, maybe I just had the "TrackOutput" button in the wrong state.

This happened to me in 1.21. I had a world with seed -4011148878802504948 and the following command block:

/setblock 277 73 176 minecraft:command_block[facing=east]{Command:"locate biome minecraft:eroded_badlands"}

The LastOutput field was consistently blank after running the command, while another nearby block worked reliably and yet another worked only for biomes that were close by. After destroying and replacing the consistently broken block, all the blocks began working reliably. I have no clue what specifically might have caused the bug to occur.

This report is currently missing crucial information. Please take a look at the other comments to find out what we are looking for.
If you added the required information and a moderator sees your comment, they will reopen and update the report. However, if you think your update to this report has been overlooked or you want to make sure that this report is reopened, you can contact the Mojira staff on Discord or Reddit.
-- I am a bot. This action was performed automatically! If you think it was incorrect, please notify us on Discord or Reddit

Vidgame Doksha

(Unassigned)

Unconfirmed

(Unassigned)

20w16a

Retrieved