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.
Related issues
is duplicated by
relates to
Attachments
Comments
migrated
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
SunCat
@unknown, you don't need to add a link to the version number. Just write it like this: MC-108801
#ThanksAgain
Affects Version(s) 16w42a
Why is the CHK set to 23/Oct/16 10:38 AM when it should be set to when it was confirmed? And who did actually confirm it?
SunCat
CHK is an internal field and it is set to whatever date it needs to be set.
In 16w44a,
Causes error for Strongholds in Screenshot 1
Nonexistent structure being supposedly located in Screenshot 2
Digs to Fire/water cave (which also occurs in MC-108801) in Screenshot 3
Still happens in 1.11pre1
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.