-
Bug
-
Resolution: Invalid
-
None
-
Minecraft 16w39b, Minecraft 16w39c, Minecraft 16w40a, Minecraft 16w42a, Minecraft 16w44a, Minecraft 1.11 Pre-Release 1, Minecraft 1.11, Minecraft 16w50a, Minecraft 1.11.2, Minecraft 1.12.1, Minecraft 1.12.2 Pre-Release 1, Minecraft 1.12.2 Pre-Release 2, Minecraft 1.12.2, Minecraft 17w43a, Minecraft 17w43b, Minecraft 17w45a, Minecraft 18w22a, Minecraft 1.13-pre1, Minecraft 1.13.1, Minecraft 1.13.2, Minecraft 18w43b, Minecraft 18w43c
-
Confirmed
-
(Unassigned)
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
- Create a new world where generate-structures=false.
- Use /locate <structure> and observe the output.
- Click the coordinates to travel there.
- There is no structure because structure generation is disabled.
- Command should output there is no structure nearby.
- is duplicated by
-
MC-108330 /locate still gives coordinates when they're nothing
- Resolved
-
MC-130441 /locate still returns coordinates when structure generation is disabled
- Resolved
-
MC-136494 Strange behavior of /locate if the option Generate structures is set to OFF
- Resolved
- relates to
-
MC-108801 /locate command returns offset or incorrect mineshaft locations
- Resolved
-
MC-108187 /locate returns location of non-existent Mansion in pre 1.11 generated terrain
- Resolved
-
MC-110532 Use "/locate Stronghold" output "An unexpected error occurred trying to execute that command"
- Resolved