[MC-171049] locatebiome tries to find biomes that do not exist in current dimension or that do not generate at all

The locatebiome command can try to locate biomes that do not exist. This can be because the player is in the wrong dimension for the biome or the biome will never generate. The game takes several seconds to look for the biomes.

Examples:

/locatebiome minecraft:deep_warm_ocean (never generates with Default worlds)
/locatebiome minecraft:mountain_edge (never generates with Default worlds)
/locatebiome minecraft:nether_wastes (when in Overworld of a Default world)

What should happen: There should be a check on whether biome generation is possible. If it is not possible, the message should say "Biome does not exist" (for biomes that never generate) or "Biome does not exist in this dimension".

Linked issues

relates to

MC-126244 '/locate', explorer maps, and treasure maps can cause extreme TPS lag, even leading to a complete server freeze if structure generation is turned off

Comments

marcono1234 2020-02-16T03:12:49Z

Note that unlike /locate, /locatebiome has at least a limitation and stops after a while if it cannot find the biome.

bdm68 2020-02-16T07:15:50Z

The locatebiome command does stop after a while, but it shouldn't be making an attempt that can be determined before starting to be futile.

Compare the behaviour when using locatebiome on a superflat world. This skips the check and returns immediately.

Adrian Östergård 2020-02-26T08:31:54Z

This is a feature request.