I know that bedrock and realms have been really buggy as of late, but this is ridiculous. Maybe due to the chunk errors? I'll also add that my stuff despawned instantly afterwards.



by PandaGD

18 Comments

  1. Horny_Dinosaur69 on

    Slowing down the vid you die the second you touch the bottom of the river, looks like water didn’t load or work right bc of bugrock and you basically dove into it

  2. Server desync. Your stuff didn’t despawn instantly, you just died elsewhere. The server didn’t register that curve you did towards the river, so instead your real body traveled double or triple the distance through unloaded chunks in the direction you were going, until the server was able to catch up to it. You died when the blocks loaded, right before your client could sync or get kicked for illegal movement. The problem is your stuff could be inside of any caves of the chunks to the front of where you were going originally.

  3. Minecraft Bedrock Edition handles chunk- and terrain-rendering between server and client differently than java. Even if it’s a local world, which is still a local server on your device. Since client and server don’t always stay perfectly synchronized (especially when traveling quickly with the elytra), the client sometimes shows terrain that the server hasn’t finished loading yet. As a result the player can sometimes fall through and/or collide with unloaded chunks, which causes random deaths.

    I recommend watching [this](https://www.youtube.com/watch?v=1ddRp3RUyJ4) video. I’m not sure if I understood everything 100% either, but at least you now know that you’re not the only one.

    I don’t play bedrock, but if I was, the first thing I would do is to check if/where I can enable the gamerule keepInventory. Exactly for this reason.