mojira.dev
MC-180092

/locatebiome has much lower range than /locate

When using

/locatebiome minecraft:jungle

I get told there are no jungles within a reasonable distance. 

However if I use

/locate Jungle_Pyramid

I get given the coordinates within a short time.

 

Do these commands function differently underneath the hood? It just seems inconsistent about how they behave. 

Linked issues

Attachments

Comments 11

MC-188953 is a completely different bug! Why is it a duplicate of this?

Confirmed for Minecraft 1.16 Pre-release 5

ManosSef your ticket had a similar issue to this ticket with the distance a biome can be located. Even though both are related, it talks about the same issue, therefore giving a duplicate. I hope that explains it.

————

I think the shorter distance might be intended to not make the server side go behind too long.

Please provide a seed where this happens.

Seed: -5553941294686131356
Coordinates: /execute in minecraft:overworld run tp @s -350.77 71.00 6729.70 -201.45 13.65 then locate any biome.

1 more comments

In most worlds, modified_jungle_edge will always provide the error message due to it being the rarest biome (though that info is based on 1.7, I do believe it is still accurate though)

Can confirm that this is still an issue in 20w51a. I've attached an additional screenshot with the F3 Debug Screen enabled.

Happened to me the same, seed is -8174739535245674310.

Originally tested with Optifine, but still reproducible within the Vanilla environment.

Use this command /locatebiome minecraft:badlands

Can confirm in 21w03a.

Connor Williams

(Unassigned)

Community Consensus

Platform

Normal

Commands

20w17a, 1.16 Pre-release 4, 1.16 Pre-release 5, 20w51a, 21w03a

Retrieved