mojira.dev
MCPE-182470

/locate command sometimes gives false coordinates for Trial Chambers

When creating a new world nearby Trial chambers can't generate but if located by commands for nearby it shows/give coordinates but not generate Structure

How to regenerate issue:

1. Create a new world 

2. Active cheats and set game mode to creative

3. Locate trial chambers using command from world spawn point

4. Reach to given coordinates

Observations:

You will observe that there is no trial chambers generated if you locate trial chambers again on that place it will show same coordinates for trial chambers

Note: If you locate trial chambers for unloaded chunks it will show you coordinates for next trial chambers and that coordinates works.

Expected result:

trial chambers should be generate at coordinates from locate command nearby world spawn point.

For example:

Seed: 264155213235856884

Command used: /locate Structure trial_ chambers

Coordinates: x:80, y❓ , z:48

In Images you will observe that there is no trial chambers generated

Linked issues

Attachments

Comments 7

[media][media][media][media][media][media]

Please provide your seeds and attach your screenshot to show that problem 

Please update the Description to include

  • World seed(s) used (and make sure this is a new world)

  • Exact command(s) used

  • Coordinates returned

Please update the Description to include

  • World seed(s) used (and make sure this is a new world)

  • Exact command(s) used

  • Coordinates returned

Confirmed, This definitely cause of MCPE-179159, Which because of structure changes to improving location and the /locate structure command may could causes an location error.

I've got believe i analyzed from chunkbase website (The trial chambers could found in some marked places) seems discovered that found over the ancient city nearby.

Can confirm on Windows. In Java Edition, the /locate command outputs a different coordinates, and that coordinates have a trial chambers in both editions, which further indicates that it shares the same root cause as MCPE-179159. I would prefer let this one stays as a separate report, though.

Oh and I would recommend to rename this report to focus on the /locate issue, this have nothing to do with the world spawn point. I also have found another example of this.

Seed: -7373789123602069316
Coordinates: -432 ~ -240

Is this still an issue in the latest version?

Infinity_Ishu

(Unassigned)

1250273

Confirmed

Multiple

Android 10

1.21.10.22 Preview, 1.21.2 Hotfix, 1.21.50

Retrieved