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
5365757111184314758Visit 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
/locatebiomein 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
/locatebiomein 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 biomein 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
Linked issues
is duplicated by 12
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-249822
Deep Dark not generating properly in updated worlds
Resolved
MC-264838
Cherry Grove Biome (1.20.1) cannot be located using /locate biome command
Resolved
MC-278663
Broken worlds/ locate commands?
Resolved
MC-278681
Locate an pale garden locate an dark oak forest if the chunk was generate before 1.21.4
Resolved
MC-278722
Using /locate pale_garden in a pre-generated world, will bring you where it was SUPPOSED to be.
Resolved
relates to 4
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
MCPE-188792
/locate biome pale_garden command leads to already explored Dark Forest
Open
MC-135996
Eye of Ender and /locate structure report wrong coordinates in upgraded worlds
Resolved
Comments 6
Can confirm in 1.19.3.
I'm running a minecraft server world which I have been updating, it's now on 1.20.4 - I'm unable to use /seed which returns a 0, and I am unable to use the /locate command to find anything, the game happy generates the world based on the 'old' generation, but has 'bugged out' with a few areas which are completely misaligned to the old generation, and obviously the 'new' generation.
But it's impossible to use any commands that rely on the world seed because of this misalignment. I suspect this also means for those chunks which are 'rendering on the old style' that they may not even generate anything new?
Weird that we're still suffering this kind of thing. Especially when this problem is acknowledged enough to have other tickets closed out as duplicates.
Happy birthday to this issue I guess? 4 years old soon?
@tryashtar - Do you think we could have the votes increased on this considering there's 21 tickets closed out as duplicates and those, the votes for them, and the comments on them could be considered votes for this issue?
As I believe the 'expecting people to vote for an issue if it's important enough' is disingenuous and masking the issue in favour of user fatigue.
Hey stanto. I'm sorry this issue is troubling you. I am curious what you mean by /seed giving 0. And the rest of your earlier comment has me a bit confused as well. Are you finding that in your world, even generation in newly explored chunks is incongruent with the /locate output? If so, I think something may be amiss even beyond this bug report. I'd be interested to look into that.
As for the votes, I'm afraid I'm powerless to manipulate the tally, or do much to help it get fixed faster. My personal, unprofessional opinion is that I think that based on the nature of the command, it's unlikely this issue will be fixed (MC-135996, a more impactful issue IMO, was declined recently). But who's to say. Thank you for your interest and concern. 🙂
marcono1234
/locatebiome basalt_deltas takes me to a huge nether wastes biome.