Details
-
Type:
Bug
-
Status: Open
-
Resolution: Unresolved
-
Affects Version/s: 20w07a, 20w15a, 1.16 Release Candidate 1, 1.16, 1.16.1, 20w29a, 1.16.2 Pre-release 1
-
Fix Version/s: None
-
Labels:None
-
Confirmation Status:Confirmed
-
Category:Commands
-
Mojang Priority:Low
Description
The bug
When upgrading an older world where the world generation was different, using /locatebiome in that world might claim that it found a biome even though these chunks have already been generated in a previous version and the desired biome is therefore not there.
How to reproduce
- Create a world with the following seed in any version before the 1.16 snapshots
5365757111184314758
- Visit the chunks in the Nether near (0,0)
- Open the world in a 1.16 version
- Use /locatebiome in the Nether
/execute positioned 0 0 0 run locatebiome minecraft:soul_sand_valley
It claims a soul sand valley is at (0,0) even though it is not because the chunks were generated in a previous version
Attachments
Issue Links
- is duplicated by
-
MC-178181 /locatebiome won't tell me the right coordinates
- Resolved
-
MC-190538 /locatebiome command points to new nether biomes in older terrain, and therefore is there only nether wastes.
- Resolved
-
MC-191019 Locatebiome command when used in nether incorrectly identifies chunks generated in 1.15
- Resolved
-
MC-194451 Not locate new biome in nether
- Resolved
- relates to
-
MC-194273 Save data of new Nether biomes is lost when upgrading a world to 20w28a or above
- Resolved
-
MC-135996 Eye of Ender and /locate report wrong coordinates
- Open