-
Bug
-
Resolution: Unresolved
-
None
-
20w07a, 20w15a, 1.16 Release Candidate 1, 1.16, 1.16.1, 20w29a, 1.16.2 Pre-release 1, 1.17.1, 21w43a, 1.18 Pre-release 1, 1.18 Pre-release 2, 1.18 Pre-release 8, 1.18, 1.18.1 Pre-release 1, 1.18.1, 1.18.2 Pre-release 1, 1.18.2, 22w12a, 22w13a, 22w14a, 1.19, 1.19.2, 1.19.3, 1.20.1
-
None
-
Confirmed
-
Commands
-
Low
-
Platform
The bug
When upgrading an older world where the world generation was different, using /locate biome 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)
- Use the version specific steps below
1.16
- 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
1.17 & 1.18-pre1
- Open the world in a 1.17 or 1.18 version
- Use /locatebiome in the Nether
/execute positioned 0 0 0 run locatebiome minecraft:crimson_forest
It claims a crimson forest is at (0,0) even though it is not because the chunks were generated in a previous version
1.19+
- Open the world in a 1.19 version
- Use /locate biome in the Nether
/execute positioned 0 0 0 run locate biome minecraft:crimson_forest
It claims a crimson forest is at (0,0) even though it is not because the chunks were generated in a previous version
- 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
-
MC-239863 /locatebiome command teleports you to wrong biomes in blended worlds
- Resolved
-
MC-241296 /locatebiome command locates non-existent biomes in old worlds
- Resolved
-
MC-241715 /locatebiome does not work properly
- Resolved
-
MC-243419 /locatebiome does not function correctly in chunks generated before 1.18.
- Resolved
-
MC-244091 Locatebiome doesn't work properly in 1.17 to 1.18 worlds
- Resolved
-
MC-244092 /Locatebiome shows the incorrect biome
- Resolved
-
MC-244113 /locatebiome giving wrong biome coordinates
- Resolved
-
MC-244548 /locatebiome on upgraded world doesn't work
- Resolved
-
MC-244953 Did /locate and am in a biome that clearly isnt there
- Resolved
-
MC-248056 Minecraft reports incorrect biomes after upgrading a world from a prior version to version 1.18 and 1.18.1. This breaks the /locatebiome and the village type generation. Unknown is if the other structure generation is affected.
- Resolved
-
MC-249704 The Deep Dark biome can appear in old chunks
- Resolved
-
MC-249822 Deep Dark not generating properly in updated worlds
- Resolved
-
MC-250421 After updating world from pre-1.18 to 1.18, /locatebiome command does not work properly in loaded chunks
- Resolved
-
MC-252550 Seed not updated with 1.19 update
- Resolved
-
MC-252655 When using the "/locate biome" command to find a mangrove swamp on older Minecraft worlds (specifically this world was created in 1.16) it displays coordinates for random spots that aren't mangrove swamps.
- Resolved
-
MC-253010 The deep dark biome isn't generating correctly on old worlds.
- Resolved
-
MC-257649 Locate doesn't support old land's generation
- Resolved
-
MC-264838 Cherry Grove Biome (1.20.1) cannot be located using /locate biome command
- Resolved
- relates to
-
MC-194273 Save data of new Nether biomes is lost when upgrading a world to 20w28a or above
- Resolved
-
MC-253417 Updating a pre-generated world to 1.19+ doesn't generate Deep Dark biomes
- Resolved
-
MC-135996 Eye of Ender and /locate structure report wrong coordinates in upgraded worlds
- Resolved