mojira.dev
MC-108011

/locate and custom worlds

If you use /locate in a custom world with some structures disabled it still gives the location of the nonexistent structure.


Mod edit: Copied repro steps from MC-130441

Expected output:

'Could not find that structure nearby.' (or whatever the command says when it fails)

Returned output:

'The nearest <structure> is [coords].'

The bug

The /locate command returns coordinates of structures even in worlds when structure generation is disabled.

To recreate

  1. Create a new world where generate-structures=false.

  2. Use /locate <structure> and observe the output.

  3. Click the coordinates to travel there.

  4. There is no structure because structure generation is disabled.

  5. Command should output there is no structure nearby.

Linked issues

Attachments

Comments 15

Similarly, if you update to 1.11 from a 1.10.2 world, where the location of a Mansion has already been generated, the locate command will still point you to the location, even though there isn't a Mansion there.

However, I expect I may need to raise a separate ticket for that.

Still happens to 16w40a

This issue relates to MC-108801

@unknown, you don't need to add a link to the version number. Just write it like this: MC-108801

#ThanksAgain

5 more comments

Minecraft 1.11 too.

Affects Version 16w50a

Affects Version 1.11.2

Still happens in version pre-release1

I get 'An unexpected error occurred trying to execute that command' when using /locate instead giving a location in 18w47b.

Maybe it's fixed.

James Bauer

(Unassigned)

Confirmed

(Unassigned)

/locate, customized-world, structure, world-generation

Minecraft 16w39b, Minecraft 16w39c, Minecraft 16w40a, Minecraft 16w42a, Minecraft 16w44a, ..., Minecraft 1.13-pre1, Minecraft 1.13.1, Minecraft 1.13.2, Minecraft 18w43b, Minecraft 18w43c

Retrieved