Ace

Happens in Android too, Android 14 Go Edition. Tried reinstalls and restarting my device. No budge.

I've added another screenshot that shows how far I had to travel in a rather straight line before I hit new generation. You can see the beginnings of a bedrock wall where I finally began to drop below level 0.

This is still an issue in 1.18.12. I have attached screenshots. This world is in a Realm.

Aside from the fact that Bedrock has not been replaced with Deepslate despite being updated to 1.18.2 Hotfix, nothing else has changed. There are no addons on the realm either.

I didn't actually play when the Realms were updated to 1.18. My Minecraft automatically updates, and my Realms automatically follow that–literally it locks me out of my Realm until a day after my Minecraft has been updated. I logged in to find out the 1.18.2 Hotfix was already a thing, and already downloaded. I haven't really had time to play after 1.18 dropped.

So as far as I know the Realm went from 1.17 to 1.18 to 1.18.2, but I didn't actually see it at the state of 1.18.

The world copy that was downloaded prior to 1.18 and was not on the Realm prompted me to update when I went to load and verify, and it updated directly from 1.17 to 1.18.2 and was fine. The world copy I downloaded from my Realms (most current copy of my Realm) after the 1.18.2 update did not prompt me to update the world so I know it was updated to the latest update, and that world still has Bedrock.

So to summarize:

Realm - World started with 1.17, possibly updated to 1.18 through auto-update did not play on realm at this time, updated to 1.18.2 through auto-update and world still had Bedrock when loaded in
Downloaded World Save from Realm after 1.18.2 update - 1.18.2 still has Bedrock
Downloaded World Save from Realm prior to 1.18 update - 1.17 updated to 1.18.2 Bedrock replaced with Deepslate

The world and Realm are updated to 1.18.2, I verified after I downloaded a saved copy of the Realm to be sure. The are both 1.18.2 as of the hotfix, and the world was updated prior to that as well. This was a previously 1.17 Realm, so no the hotfix did not fix this for all worlds or even realms despite being marked as Fixed.

The creative copy of the realm downloaded before the 1.18.2 Hotfix and the update to 1.18 (a pure 1.17 world initially, updated to 1.18.2 when I decided to verify if this was honestly an issue still given it was previously marked Fixed) That world actually DOES have the replaced bedrock (I traveled to the same coordinates I was in in my Realm to make sure, those chunks were already generated when I made the creative copy), but anything downloaded post 1.18 and 1.18.2 does not. This information was actually in my original comment, although I did not state the creative copy of my Realm was originally 1.17 before I updated it.

With the 1.18.2 Hotfix this is definitely NOT still resolved. I have a world from 1.17 that I had a mine built in, dug down to try and get to the below 0 levels with new generation, and there is literally 5 blocks of bedrock in my way still. I downloaded the world from my Realm just to make sure it was actually considered updated, and still the bedrock exists. I have older downloaded versions from my realm in creative from before the update and hotfix dropped and those DID have access to the new world generation. I have no idea if this is a continued issue just with Realms worlds or not, but it is very frustrating as I just started this world to enjoy Caves and Cliffs and would rather not have to start all over AGAIN just to get to the new world gen.

I fixed it. If anyone has this bug you might have ray-tracing not but your device isn't supported.

so like 1.5 and 1.5.1 crashes when i try playing it also 1.5.1 is minecraft 2.0 april fool prank one and its release like it says minecraft on the thing cant load

pls close this it was a glitch with my computer  restarted and its back

sorry the it was a glitch i restarted my computer and its back

Just happened to me on 1.13.2 (vanilla)

[20:41:32] [Server thread/WARN]: Failed to handle packet for / IP:PORT
h: Ticking player
        at tf.i(SourceFile:435) ~[minecraft_server.1.13.2.jar:?]
        at uc.Y_(SourceFile:197) ~[minecraft_server.1.13.2.jar:?]
        at hw.a(SourceFile:238) ~[minecraft_server.1.13.2.jar:?]
        at ub.c(SourceFile:171) [minecraft_server.1.13.2.jar:?]
        at net.minecraft.server.MinecraftServer.b(SourceFile:773) [minecraft_server.1.13.2.jar:?]
        at so.b(SourceFile:360) [minecraft_server.1.13.2.jar:?]
        at net.minecraft.server.MinecraftServer.a(SourceFile:681) [minecraft_server.1.13.2.jar:?]
        at net.minecraft.server.MinecraftServer.run(SourceFile:584) [minecraft_server.1.13.2.jar:?]
        at java.lang.Thread.run(Unknown Source) [?:1.8.0_201]
Caused by: java.lang.NegativeArraySizeException: nbits < 0: -1495787926
        at java.util.BitSet.<init>(Unknown Source) ~[?:1.8.0_201]
        at ceh.<init>(SourceFile:22) ~[minecraft_server.1.13.2.jar:?]
        at ceh.<init>(SourceFile:17) ~[minecraft_server.1.13.2.jar:?]
        at ayc.a(SourceFile:138) ~[minecraft_server.1.13.2.jar:?]
        at ayc.a(SourceFile:213) ~[minecraft_server.1.13.2.jar:?]
        at axy.a(SourceFile:1848) ~[minecraft_server.1.13.2.jar:?]
        at ayc.a(SourceFile:197) ~[minecraft_server.1.13.2.jar:?]
        at ayc.a(SourceFile:181) ~[minecraft_server.1.13.2.jar:?]
        at aer.a(SourceFile:639) ~[minecraft_server.1.13.2.jar:?]
        at afa.a(SourceFile:1697) ~[minecraft_server.1.13.2.jar:?]
        at aog.a(SourceFile:1620) ~[minecraft_server.1.13.2.jar:?]
        at afa.k(SourceFile:1998) ~[minecraft_server.1.13.2.jar:?]
        at aog.k(SourceFile:570) ~[minecraft_server.1.13.2.jar:?]
        at afa.R_(SourceFile:1819) ~[minecraft_server.1.13.2.jar:?]
        at aog.R_(SourceFile:281) ~[minecraft_server.1.13.2.jar:?]
        at tf.i(SourceFile:372) ~[minecraft_server.1.13.2.jar:?]
        ... 8 more

I'm actually suffering from this same issue. I'm running a world on a Realm, we just spawned in the Wither, the fight was able to go okay for maybe 5 minutes and then the health bar vanished but the Wither was still visible. After knocking the Wither down to the second stage where it killed me for the last time before the bug happened the Wither literally vanished but continued to hurl Wither skulls at anyone within range.

Every time anyone returned to where we spawned the Wither we were able to see the Wither in a pure white skin as it hurled Wither skulls at us. We were able to watch said Wither appear to "die" or "despawn" and from that point on Wither skulls would be hurled from an invisible enemy. Every time we died it would put in a death message that we either withered away or were blown up by the Wither. All of our gear also vanished after the first death from the period when the Wither had gone into its second stage–even though it took ten seconds to return to the spot where we died and the moment the Wither glitched.

Also discovered the day/night/weather cycle broken in synchronous with the Wither resulting in day/night/weather cycle still appearing to work visually, but no effect on the world as a whole. Mobs would spawn as if night and would not suffer damage even if the game visible showed day.

Only packs loaded in are a texture pack, Chroma Hills HD. Nothing else added, no cheats allowed, pure 100% survival world because we as friends wanted to get achievements together.