There is a problem on the realms whereby the cherry biome exists in the code for a non generated area i.e. /locate biome cherry_grove works as intended. However upon going to said coordinates on an existing world, I do see the cherry chunk load but immediately disappear as if it had an error upon loading the newly generated chunk. This then replaces the chunk with an old 1.19 generation (I think) which is not going to ever have the cherry biome. To further elaborate, I have been venturing to never before gone parts of the world where I know for certain no one had been to. So this should have the new generation work. But, it does not, the biome exists but it just refuses to load, thus resorting to a default biome.
But what makes this more peculiar is that if I create a brand new world, everything works as intended. Following the same method as before, I located the cherry biome and viola the biome exists. This tells me there is an error in the code when upgrading from 1.19 to 1.20 where some issue with the generation seems to persist.
I have done some digging, and found some related bugs on 'Bedrock dedicated server' sub directory. But since they are using json. files and what not, I won't be able to follow the same method as listed since I am using a dedicated realms server.
As for reproducing the issue. Just have an old world updated to 1.20 on the realms bedrock server. Then try to locate a cherry biome. As for providing evidence, the best I can do is luck out in seeing the cherry spawn and despawn since that appears to be random. Otherwise you will only see a 'regular' biome where the cherry should have been.
P.s. my previous report came back as 'resolved invalid' due to listing more than one bug. Therefore I am leaving it to just this. The cherry grove not generating is an on going issue.
Linked issues
Comments 4
Hey, thanks for the information.
I am 110% certain this area I am exploring is not generated before because I purposefully go to a very far piece of land that is not documented. This only affects the older worlds i.e. a world built pre 1.20. Here is the thread I was referring to from the bedrock dedicated server section BDS-6230.
Basically from my understanding from reading all the issues over from there is that maybe the cherry_grove file has not been correctly implemented such that the code would run an exception whereby the chunk would default as a plaines biome (that appears to be the most common default for the cherry_grove in my experience).
I have also watched the video on the link you have provided and yes it does look similar but the key difference here is that this affects any biomes but this issue I am facing only affects cherry biomes. All other biomes work perfectly fine.
Thank you again for all the documentation and suggestions. But unfortunately this issue is present regardless.
Hi
Can you please upload copy of affected world where this issue occurs?
This ticket will automatically reopen when you reply.
Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
If you are using /locate cherry_biome, this might still point you to an already-generated chunk. The reason is that /locate works based on the world seed, not the actual contents of the world itself. Since the biome generation changes from version to version, using /locate in or near an explored area from a previous version can easily give unexpected results.
Based on your information that the cherry grove briefly appears, and that the problem does not occur with the same seed in a new world, I believe this is the same issue as MCPE-169059 and am resolving as a duplicate of that.
If you can be certain that you are not in an already-explored area (perhaps by using /tp to move very far away before using /locate) and replicate the issue, you can comment on this report and we can adjust as needed.
You also mentioned that this is reported for the Bedrock Dedicated Server project. If so, please also mention the corresponding issue ID's