Summary: I wanted to look for an ancient city and I used the "/locate" command, it showed me a coordinate and I went to it. and I found no ancient city. however, it showed a different coordinate the next time I used the command. I went to it, dug a hole, and I found an ancient city.{*}{*}
Steps to Reproduce:
Create a new world using this seed: "8624896", and enable cheats
Use the "/locate ancientcity" command
Go to the coordinate it tells you (it showed me "-328, (y?), 136" the first time, The second time, it showed me: "-216, (y?), -296")
Dig straight down until you notice some sculk patches, then stop. (-328, (y?), 136)
Go to "-216, (y?), -296".
Dig straight down until you notice an ancient city.
Observed Results:
I only found some sculk patches on the 1st coordinate (-328, (y?), 136) I told you about, on the 2nd coordinate (-216, (y?), -296) however, I found an ancient city.
Expected Results:
I would find an ancient city on my 1st coordinate.
Attachments
Comments 8
I have edited the issue now, I am on my computer and I can't upload the screenshots, because they're on my Xbox. (I forgot to tell you about the screenshots, sorry.)
I'm back and I have managed to get the screenshots for the issue, "how did you manage to upload them?" you may ask, I uploaded them to OneDrive that way I can download them on my computer and upload them that way. I have 2 screenshots for this issue, hope they help you!
This is an artifact of the way locate (and locate biome, when it becomes available) are implemented. The locate commands poll the world generator for where a feature or biome should be located. However, various limiting factors can prevent a feature or biome from actually manifesting. So, when the player arrives there the world generator may have generated something mutually exclusive to that feature or biome and the generation of the feature or biome is aborted.
This is true for both Bedrock and Java, and is just something players who use locate and locate biome have to live with. It is not that difficult to issue the second locate command to find the next nearest object. Or alternatively, now spectator mode can even be used.
Your report does not contain enough information to understand or reproduce the problem.
Are you using a newly created world? If not, and the chunks were already generated, they won't get regenerated, but the command works based on the world seed.
Please Edit the Description section above, using this format:
Steps to Reproduce:
1. (list every step exactly, so someone else can reproduce the issue, and try following your list to make sure you can still reproduce the issue yourself)
2.
3.
Observed Results:
(briefly describe what actually happens, including exact message(s) shown)
Expected Results:
(briefly describe what should happen)
Be sure to include the world seed and coordinates.
This report has been temporarily closed as Awaiting Response. It will automatically reopen when you add information. Please follow the format shown and include all sections (steps, observed, expected). Reports that do not contain all of the requested information and complete steps to reproduce the issue may be closed as Incomplete. For more information please read the Bug Tracker Guidelines.
You may find this Report Creation Form helpful for any future reports you create.