This happen to me every 30 minutes and idk why. If you can get video evidence of it. I may help with a video.
If you compare this to java you would see the difference in how the sky works from bedrock.
Instead of creating a report, why not rewrite the report you have or delete then create.
I did the same, but I saw this in 1.20.12. And I never got a reply from the developers.
#MCPE-174004
Yes, this is also patch in the version 1.20.1.
No this doesn't affect 1.20.1. This was patch in the new version after 1.19.50
Sorry, but I didn't understand what you mean by:
Title: Neither seasuger, coral nor coral fans spawns when using a bone/bone-meal underwater blocks.
The title does not help for me to understand the problem.
Make sure you don't use a double sized chest. Using a single one get you the achievement. For double size chest you need fill all the slots with cobblestone in order to get the achievement with a double chest.
It's look like your in the nether, but I'm experiencing this to. with RTX and other shaders with render-dragon.
Don't worry Mojang fix this issue after the next update.
All for who reply:
@unknown
@unknown
@unknown
Thanks for Replying!
As an example - the game will get stuck on any loading screen as the Ui at anytime.
This happen to me if your 10000+ away from spawn, it won't locate the stronghold/s if your to far away. Even in the release of 1.19.71.
If you happen to lose you items when joining a server and then joining opt-out survival world I will make a backup or reload the world to get item back and where you were.
Hello, I see you have the same problem as I. If you don't want to lose your items, try reloading the world again and your inventory will be restore. But if the trick don't work always make a backup of your world every time you leave. It's what I do.
This is also happening on pc and it's causing a lot of lag making your game frezze or frame drop.
I rewrite the title and devise version this problem acore on.
It was not storage which was causing the problem and I did not had any video yet then. The only one I made is this in the report.
This only happen on some device or console.
This Bug hasn’t been fix yet after 1.21.71