Summary:
If the desired biome is in another dimension, far away, or for some other reason is not immediately located, it freezes the world until an error is issued or until the desired biome is found.
You can try mushroom_island_shore this biome is not in worlds.
Steps to reproduce:
Write a command to search for a biome that is not in your current dimension.
Try to break blocks, place blocks (until an error message appears).
Observed results:
While searching for a biome, the world is freezes.
Expected results:
The biome search will be instant or the world will not freeze during the search.
Linked issues
is duplicated by 2
Attachments
Comments 3
@unknown
Alas, the problem has not been completely fixed. /locate biome still noticeably freezes the world when looking for biomes that don't exist. In 1.19.10.23, this could be from 3 to 50 seconds, and in 1.19.10.24, a maximum of 5 seconds. For comparison, in the java version, this does not happen and mobs, blocks and other processes do not freeze for a second (even if the biome search is not instantaneous).
As of version 1.19.10.24 this is a very minor issue for me, but could be a significant issue for weaker devices.
You can also create a command block to repeat and enter a command to find a non-existent biome (/locate biome crimson_forest in the overworld) and activate, then the world will freeze hard (no fps drop is observed).
[media]
This bug is fixed in the latest beta version, and the fix will be included in a future update when that is ready for full release (no specific date can be given). We will leave this ticket open as a point of reference until the fix has been fully released.