mojira.dev
MCPE-159992

/locate biome deep_dark sometimes sent you to the wrong coordinates of the biome

The /locate biome usually finds biomes, even cave biomes, except for the deep dark biome. There are some chances when locating the deep dark biome would result in the wrong coordinates.
For example, we're going to be using 3 random seeds to test (w/ Java as a comparison):

Seed #1: 565463436
BE coordinates: -186 104 0
JE coordinates: -676 -34 920

Seed #2: 65161496154
BE coordinates: -1184 128 -992
JE coordinates: -90 -17 -2249

Seed #3: 3216549867
BE coordinates: 32 121 -352
JE coordinates: 536 -36 -522

Seed #1 map and corresponding coordinate:

[media]

Seed #2 map and corresponding coordinate:

[media]

Seed #3 map and corresponding coordinate (w/ in-game screenshots):

[media]

[media]

From all the seeds that I got, seed #1 and #2 on BE give the coordinates to the outer edge of the deep dark biome boundary, instead of within inside of them. Seed #3 on BE gives completely wrong coordinates where there is no deep dark biome at all at the location.

How to Reproduce:
1. Create a new world (preferably with spectator mode for a quick check underground).
2. Locate a deep dark biome using /locate biome deep_dark command.
3. Switch to Spectator Mode.
4. Go to that coordinate that the command output gave.
5. Go underground to see if the deep dark exists.

Observed Result:
Sometimes the coordinates send you to the correct coordinate, but in some cases, it sends you to the wrong coordinates where there is no deep dark biome at all, despite what the command output says.

Expected Result:
The /locate biome deep_dark command should always give the correct coordinates, like what Java does.

Attachments

Comments 3

[media]

(See note at end about this pic, comment IS about deep dark) I am experiencing this issue in Java as well. I'd say on average only about 15% of the locations given actually are in Deep Dark biomes. In 2 out of the approximately 15 I tried, I found deep dark at a different y coordinate. I had tried digging up and down from the given location because most of the coordinates given through "locate" have only ~ for a y coordinate and I thought maybe that was the faulty coordinate.  In one case I was given coordinates near but not inside a deep dark biome I had already found.  In almost, if not all, cases the debug screen (F3) showed the biome to be deep dark at the given location, the coordinates I teleported to were inside solid deep slate, tuff or other solid material that was NOT sculk or any of its variations. My conclusion is that the problem is not with the "locate" command but with the definition of the biome. I will be doing further research on this.

I am pleased to say that if you are looking for Deep Dark with an Ancient City, you are in luck.  That can be located spot on as long as you know the right y coordinate to look at. Thus a good work-around is to "locate" an ancient city rather than just deep dark. It's probably the city you really want anyway.

PS I also remember noticing that I was a fair distance offshore of a mushroom island when the debug screen started identifying the biome as "mushroom fields". I just did a "locate" on mushroom fields and wound up a bit offshore as seen in the attached pic. Had this been an underground situation, I wouldn't have known I was anywhere close.

 

Here is my further research. Essentially what I found is that in most cases, a Deep Dark biome is found within 50m of the location predicted but it is not often visible from the teleport location. To get the data, I teleported (in creative, of course, otherwise I'd have died in solid rock) and used fill commands to remove all of the deep slate in an area 50m from the beam in site in all horizontal directions and 10 meters above. This took 4 commands because of the size of the area. In all but one case, this revealed the deep dark biome. The one exception was when the biome was below the teleport location which was not surprising since the y coordinate given was only -10.  In this data set, all coordinates given did show as deep dark at the location, although I have seen exceptions to that in the past. My conclusion is that, at least in Java,  the problem is not with the locate command but with the definition of the biome boundaries. 

lillybeacon

(Unassigned)

760264

Confirmed

Windows

1.19.30.23 Preview, 1.19.30.22 Preview, 1.19.20.24 Preview, 1.19.11 Hotfix, 1.19.20, 1.19.21 Hotfix, 1.19.51

Retrieved