Afan Dhika Nur Esa
Assigned
Reported
Comments
i think on new update 1.18.0.23 they already fix it or maybe just random bug version. after update the minecraft storage cameback to games folder. I still have my previous version backup around v.1.17.0.40 maybe, and i tried to open it then i got no floating bug where my progessing world had. but the world that already loaded with floating bug need to be manually fix by taking water or lava by ourself. i'm just checking chunks around my base, if there is water or something still generated floating correct me.
here is my world that affected. via OneDrive
https://1drv.ms/u/s!AjMERIz72v3eiW42jQNtIyPtwhu2?e=R91jzR
i don't know but after i update to beta 1.18.0.21, minecraft savefile is moving from Storage > games to Storage > Android > data > com.mojang.minecraftpe. that's make my previous world can't detected either from application and external minecraft settings.
sorry i deleted my old world around beta v.1.17, because i thought that beta 1.18.0.23 has been fixed. But after i updated again on beta v1.18.0.24, the bug get worsen, floating block generated more than before. and also the minecraft storage moved again on device storage > android > data > com.mojang.minecraftpe. i always wondering maybe the storage change caused the floating bugs but yet i don't know.
maybe i can share how to reproduce this bugs from creating my own world but i'm not sure :
Steps to Reproduce:
Create world on around beta v.1.17 (Cave and Cliff on)
Then update on affects version of this bugs (for me is beta v.1.18.0.21)
Because the mcpe storage folder is moved, i moved my worlds folder into new mcpe storage folder.
Then just play the world, and you will found that chunks around you is generated with floating blocks.