MCPE-155400Ancient Cities are now generating at Y -27 instead of Y -51
Ancient Cities now always generate at Y -27 instead of Y -51 as they did in the previous Bedrock beta/preview, as well as the current Java 22w18a release.
This is a bug. While the ancient city jigsaw files have changed with a starting coordinate at Y -27, the new 22w18a Java generator is designed to generate them downward from that location so they end up at Y -51. However, for whatever reason the Bedrock Ancient City generator is still coded to generate them upward from that position so Bedrock Ancient Cities are generating too high in the world.
Reproducibility: Always
Steps to reproduce:
Go to any Ancient City in Bedrock 1.19.0.30/1.19.0.31. The city will be at a higher Y level than Java.
Suggested seed & coordinates: -1219847014503467214 X: 580 Y: -20 Z: 130
This city is at the same X and Z coordinates in both Bedrock and Java when using this seed and provides a good example of the issue.
Observed results: The city floor places the player at Y -27.
Expected results: The player should be at Y -51 when standing on the city floor.
Created Issue:
Ancient Cities are now generating at Y -27 instead of Y -51
Ancient Cities now always generate at Y -27 instead of Y -51 like they did in the previous Bedrock beta/preview as well as the current Java 22w18a release.
I am not sure if this is a bug or a design change which is eventually coming to Java. There was no mention of it in the changelogs. In any case, this is now a parity issue between the two versions.
Reproducibility: Always
Steps to reproduce:
Go to any Ancient City in Bedrock 1.19.0.30/1.19.0.31. The city will be at a higher Y level than Java.
Suggested seed & coordinates: -1219847014503467214 X: 580 Y: -20 Z: 130
This city is at the same X and Z coordinates in both Bedrock and Java when using this seed and provides a good example of the issue.
Observed results: The city floor places the player at Y -27.
Expected results: The player should be at Y -51 when standing on the city floor.
Attachments2
- Unresolved
- Open
- Unconfirmed
- Windows
- Windows 10 Pro 21H2
- 1.19.0.31 Preview 1.19.0.30 Beta
![[Helper] lillybeacon](../../../data/avatars/users/93893.png){kind=small}
Ancient Cities now always generate at Y -27 instead of Y -51
likethey did in the previous Bedrock beta/preview as well as the current Java 22w18a release.I am not sure if this is a bug or a design change
which iseventuallycoming toJava. There was no mention of it in the changelogs. In any case, this is now a parity issue between the two versions.Reproducibility: Always
Steps to reproduce:
Go to any Ancient City in Bedrock 1.19.0.30/1.19.0.31. The city will be at a higher Y level than Java.
Suggested seed & coordinates: -1219847014503467214 X: 580 Y: -20 Z: 130
This city is at the same X and Z coordinates in both Bedrock and Java when using this seed and provides a good example of the issue.
Observed results: The city floor places the player at Y -27.
Expected results: The player should be at Y -51 when standing on the city floor.
Ancient Cities now always generate at Y -27 instead of Y -51 as they did in the previous Bedrock beta/preview, as well as the current Java 22w18a release.
I am not sure if this is a bug or a design change that will eventually roll out on Java. There was no mention of it in the Bedrock changelogs. In any case, this is now a parity issue between the two versions.
Reproducibility: Always
Steps to reproduce:
Go to any Ancient City in Bedrock 1.19.0.30/1.19.0.31. The city will be at a higher Y level than Java.
Suggested seed & coordinates: -1219847014503467214 X: 580 Y: -20 Z: 130
This city is at the same X and Z coordinates in both Bedrock and Java when using this seed and provides a good example of the issue.
Observed results: The city floor places the player at Y -27.
Expected results: The player should be at Y -51 when standing on the city floor.
According to SlicedLime, the -27 change is by design and is coming to Java. I suppose this bug can be closed as "Works as Intended," though I am not sure of the reason for the change unless Ancient Cities in future MC releases will have multiple levels which require the extra real estate below Y -27.
Ancient Cities now always generate at Y -27 instead of Y -51 as they did in the previous Bedrock beta/preview, as well as the current Java 22w18a release.
I am not sure if this is a bug or a design change that will eventually roll out on Java. There was nomention of it in the Bedrock changelogs. In any case, this is now a parity issue between thetwoversions.Reproducibility: Always
Steps to reproduce:
Go to any Ancient City in Bedrock 1.19.0.30/1.19.0.31. The city will be at a higher Y level than Java.
Suggested seed & coordinates: -1219847014503467214 X: 580 Y: -20 Z: 130
This city is at the same X and Z coordinates in both Bedrock and Java when using this seed and provides a good example of the issue.
Observed results: The city floor places the player at Y -27.
Expected results: The player should be at Y -51 when standing on the city floor.
Ancient Cities now always generate at Y -27 instead of Y -51 as they did in the previous Bedrock beta/preview, as well as the current Java 22w18a release.
This is a bug. While the ancient city jigsaw files have changed with a starting coordinate at Y -27, the new 22w18a Java generator is designed to generate them downward from that location so they end up at Y -51. However, for whatever reason the Bedrock Ancient City generator is still coded to generate them upward from that position so Bedrock Ancient Cities are generating too high in the world.
Reproducibility: Always
Steps to reproduce:
Go to any Ancient City in Bedrock 1.19.0.30/1.19.0.31. The city will be at a higher Y level than Java.
Suggested seed & coordinates: -1219847014503467214 X: 580 Y: -20 Z: 130
This city is at the same X and Z coordinates in both Bedrock and Java when using this seed and provides a good example of the issue.
Observed results: The city floor places the player at Y -27.
Expected results: The player should be at Y -51 when standing on the city floor.
![[MCQA] v-magwar](../../../data/avatars/users/18935.svg){kind=small}
![[Mod] OcelotOnesie](../../../data/avatars/users/43220.png){kind=small}
This is now fixed in 1.19.0.32 / 1.19.0.33. It can be marked as resolved.