8:34 That noteblock sound would be the player holding up on their stick or d-pad on the controller. The sound is basically telling you: "No, you cant scroll up because you can only respawn".
@@PhoenixSC thank you for the wonderful video. "Never turn on hardcore mode" is what I say to series made on deadly content. Like the Java parasite mod.
There's a certain horror element where you realize the world around you has stopped making sounds in response to you doing things, and you know you have like, seconds before you mysteriously die.
In my bedrock world for some reason my hearts never fully recharge. I always have one half of a heart missing. But, bedrock being a mysterious and fair god, I can reach 0 hearts of health and still be alive.
When people teleport, on occasion they just decide to fall through the floor, so I had to make a system that teleported them to spawn when they hit the void.
I knew it. Bedrock version got hijacked by herobrine. It became a psychological horror game now. You can notice sound or visual cues, that may or may not save your life, yet still things are out of your control.
7:56 Explanation: The server forgets that you are wearing an elytra and therefore thinks you should be falling and taking fall damage. But once you take the fall damage, the server temporarily realizes you are in fact wearing an elytra and are in the air, until it immediately forgets and sends you "falling" again. The cycle repeats over and over.
There’s a glitch notorious in my friends realm we call the “rain glitch” where it’s just raining infinitely for you, and if u riptide through the air, it will give you fall damage occasionally.
It’s incredibly annoying, but it’s hilarious on servers. I seem to be the only one to experience this, and everyone called me crazy until I started Riptiding while the sun was out. This Glitch is entirely client based, because the rain does not effect the world; snow golems don’t take damage, cauldrons don’t fill up
All this happens and Bedrock still has the audacity to call Keep Inventory cheating Also I should note that the map at 7:02 isn't actually useless because Bedrock has a nice feature where if you take an Overworld map into the Nether you can see your relative position in the overworld, (with a red marker) which could come in handy when trying to link portals
That reminds me, when playing bedrock, the game would just spawn me *underwater*, so the moment the world loaded, you were already at the death screen. I wonder how long the hardcore last with that feature :]
My bedrock moment happened on a Realm - I built a custom nether portal leading to my nether base, but every time I came back, it would generate a new nether portal around 200m north. So eventually there was just this obsidian stonehenge in the middle of town that no one could get rid of because I kept accidentally making new portals
The cherry blossom one at 4:38 has the same energy as a cartoon character running off a cliff and only falling after they realize there's no ground beneath them
I think I got an idea of whats happening here. The problem is basically that the server is running behind the client and the client never gets notified of that fact. In Minecraft Java when the Server and Client get out of Sync you can tell pretty easily because the Server will start correcting the client in order to sync up again. Bedrock just skips this step (or does it less frequently) to archive better performance and the Server and Client fall out of sync. Best example is the Elytra Clip. The Client initiated the flight but the server never got that update therefore the server thought the player jumped down the cliff. Now the client tells the server that the player is still in the air but not that the player is flying. The server lets the player fall and tell the client the player received fall damage. This gets repeated until the player dies. I would gues that in this case they only send the flying flag when the player starts and stops flying to save on latency so if that packet gets dropped the server never realizes that the client started flying. Its honestly just bad protocol design for the sake of performance.
its so funny that the stated reason for not adding all three mobs is because they want to make sure the one new mob has zero issues, and then an entire version of the game is put together so poorly that simply performing the base features of the game will cause it to unravel.
8:10 in bedrock sometimes flying into something and dying doesnt always give "[player] experienced kinetic energy" sometimes i get, "hit the ground too hard", "fell from a high place" and one time i got "suffocated in a wall"
No no no basically you see even on local it creates a "server" sometimes this server doesn't render you doing something but it does render your position and as an anti cheat bc of hacked clients that take advantage of this to fly by settting your client position to something it gives you fall damage as if you were falling normally and when the sound stops that's bc of a desync between the server and the client in some cases it doesnt render your movement and it will keep you from updating it i think
In this clip hes TEN THOUSAND blocks away from spawn. I've played xbox Minecraft for years and i just know not to go far out. Your game WILL mess up. But obviously theres a bigger problem happening with bedrock edition
For wanting it to be the main version of Minecraft, it’s crazy how much shit Mojang let’s happen in Bedrock… like I REALLY REALLY want to know their thought process behind leaving these game-breaking bugs in the game for 8+ years.
@@creepster1509It’s the same thing on Java, except that on bedrock the calculations for positions are calculated differently between client and server for no reason
For the elytra deaths, the game thinks you’re falling over and over while you’re flying relative to your height. So the game thinks you’re just falling over and over as long as you’re in the air. I’ve experienced a glitch like this in survival where I got the ability to fly like in creative mode but took damage if I was too high. Bedrock is so strange.
2:48 as an old treassure wars player on the hive, if the blocks don’t make a sound, just keep bridging as fast towards your destination or back the frick up
As a Bedrock player, the only mysterious damage I've taken is occasionally taking a heart or two when I'm pillaring. I have yet to mysteriously die. I also play with sound off, so I won't even notice when it happens.
Same! I've also done crazy stuff like mining out dozens of chunks, but never got mysterious fall damage while doing so. In all my time playing, I can only remember getting weird fall damage a single time. I play on mobile and without sound, but maybe consoles are worse. Oh but I *have* died from glitching through flying machines. Those things are unreliable as transport on bedrock edition, or at least they were two-ish years ago.
i've mysteriously died before, fell through and slid off of blocks numerous times, I've even gone about 5 minutes where all leaf blocks were non-collidable and only for me not my friend, bedrock is a bundle of bugs
@@Yashu_Playzif it's similar to how java edition works, singleplayer is just a server that's running in your computer that only you can access unless you "open for lan" if it happens on multiplayer I'd assume it happens on singleplayer too but im not 100% sure if it works the same way on bedrock
Yea most bugs are on multiplayer. I’ve played single player worlds for hours with minimal issue but as soon as two people are loading in different chunk areas at once bedrock breaks down
A big issue bedrock has for some reason, during SINGLE player, when your device loses Wi-Fi, it will switch to offline, the entire world lags and you end up having things like 2:47 take place.
It’s because bedrock runs every world, whether it be a server or a single player world as a server. And that means when it lags. There is nothing you can do about it.
Java has an internal server as well, though I guess bedrock's internal server is just connected to the internet so other players can join your world (causing lag where there should be none).
That low pitched note block sound is the sound that plays when you try to scroll up or down, but you've already reached the top/bottom option and can't scroll anymore
Oh so thats why i havent heard it cause im on pc. And the clips were people on console and they presumably had their left stick held down. I thought i just missed the sound when i died tbh
Here's an even more bizarre bedrock edition story than everything in the video. On my 8 year old tablet that barely ran minecraft on life support, i had a horse I took traveling and it drowned in one of those annoying water holes before i could save it. I picked up it's saddle, had it for a while, it wasn't a ghost item cause i put it in chests, had it in my inventory for days, re-logged several times and it was always there. One day I went in the same direction as i did with my horse when it drowned and THE HORSE WAS ALIVE just wandering casually. It had it's saddle on, the world was singleplayer so no-one was messing with me and the saddle i picked up was still in a chest when I brought the horse home.
I love it when you pick up a lot of blocks, and you'll have an empty inventory spot, but it's actually just bugged out. I have to restart to get it back, or sometimes i can get it back by putting the same block in that spot, but sometimes it doesn't. I'm not sure how it works completely yet.
im so glad i switched to pc, playing bedrock edition has always been miserable due to mojang not fixing the horrendous lag that is somehow still experienced even in singleplayer worlds
I'll bet it's because they made the netcode incredibly "performant" by making it run on a single thread with a bunch of other stuff and didn't allow it to be allocated to a less busy thread if the system could support that. After all, it has to run on smart phones using the exact same code, so they probably thought the 3% performance increase on iPhones was a steal, without considering that an xbone, wiimii, ps4, or an objectively better piece of hardware might be able to produce significantly larger and more frequent packets and clog the system worse than the toilet at your local gas station and cause constant desyncs. So, basically the worst possible way to copy Java. The deaths themselves are largely because bedrock prioritises the server over client for player position and movement calculations to prevent flyhacking, (while still allowing the player's coordinates to be set by the client, because why be consistent), so if a desync occurs and the server calculates that you should have fallen, then you will take the fall damage. Because their communication is being throttled by the netcode not having enough CPU allocation to process the packets, they're often desyncing, with only the small/high-priority packets (like player coordinates and momentum) getting through and those slowly, resulting in the server often making mistakes and thus falling through blocks because it simplified a collision calculation, or dropping the player from world height because it didn't get the message that they're supposed to be flying, then passing that result back to the client and overriding the client's statement that everything is fine. Basically it's the opposite of ghost bridging in Java (where a desync basically lets you fly using ghost blocks because the client overrides the server saying that you should have fallen). An alternative explanation is that only the client doesn't actually have the checks for damage built-in and so just trusts the server implicitly, though if that were the case I'd expect it to be much more common.
Bugrock or Lagva, choose your poison 😭 The former was very forgiving to potato PCs (and crossplay) until it deleted chunks of our builds (MCPE-98789) out of nowhere the following day, we moved from the latter where TPS sometimes inconsistently spikes (even in single-player) and the Fabric performance mods became a necessity for a seamless experience after 1.12.2 onwards. (Somehow unmodded 1.20.1 is smooth so far so kudos for them)
I think mojang should stop hiding behind tech debt and different platforms/codebases to excuse the version disparity and general mistreatment of bedrock
Yeah, as a longtime realm owner, Bedrock is notorious for the immense amounts of glitches/horrible issues in the game. Here’s a few things you’ll wanna try for yourself, as well as a few past bugs that existed for prolonged periods of time: 1. Create 3 scoreboards and apply 0 score of those scoreboards on every entity. This produces lag on realms specifically, especially when multiple players in the realm. Even if your frames are smooth, entities will move significantly slower. 2. In the past, there was a glitch where the model or occasionally hurtbox of an entity is either far away, or unloaded. This was an issue that occurred primarily on realms back in the day, but also existed on single player in some occurrences. This results in invisible or invincible mobs that can and will attack you. 3. Fall damage struggles to register in the game, and being teleported in the air will often result in an infuriating death. In the perspective of the victim, they will experience random death. In the perspective of other players, the player will walk around with their model rapidly being sent back up into the air and thrown into the ground again. 4. If a command block is scheduled to create a particle effect from outside particle render distance, it will produce massive lag. 5. Mobs move slower depending on the amount of lag or entities a server is experiencing, resulting in pathetically easy combat. If something occurs to deal with the lag problem in the middle of a battle, enemies will seemingly speed up significantly. 6. Sometimes when blocking with a shield, it will take upwards of 5 seconds for it to activate. 7. Putting behavior packs in realms is a pain in the butt. 8. Horses, Boats, Minecarts, & Donkeys can be affected greatly with 6’s effects, rendering them useless. Elytra is unaffected, and will therefore become significantly buffed in times of severe server load issues. 9. You have to crouch to use a shield, which feels really cursed. 10. Caves & Cliffs has damaged several pre-existing worlds and realms despite the developers claiming it would not overwrite already-loaded chunks.
I like how number 9 isn't a glitch, just a terrible feature. I get why they did it, but it just does not work with the mechanics of the game. If you're early game and a trident drowned spawns in your river, you're just hecked. - you can't hit them without going in the water - you can't swim because you have to crouch to block the tridents - if you don't kill him fast enough, you're either going to drown or get impaled I also frequently struggle to kill skeletons without taking at least _some_ damage. Because the amount of time it takes to activate a shield means I can never really move too far between shots. It's better for me to just tank a hit and try to kill them as fast as possible
@@DaNintendude The entire purpose was for parity with Pocket Edition, but Pocket Edition still has an increased reach. It’s not even a complaint about Pocket Edition being OP or something. It’s more about an unnecessary addition. Why restrict console and keyboard players? Pocket Edition can do its own thing to work alongside the other platforms, it doesn’t need to downgrade the other platforms. It’s just a matter of controls.
I experience that darn shield delay literally every time I use the shield and it’s awful. And I’ve gotta add my own experience and that is with nerd poling. Quite often when poling upwards one of my blocks will not be tangible, this results with you standing inside the block you just placed, and soon afterwards the game will “catch up” and will make the intangible block you are standing in, tangible, causing the block to shove you sideways and fall to your doom. Otherwise I also noticed taking fall damage after doing some parkour jumps. (Although not nearly as constant as what is seen in the video, but regular enough to be note worthy) How has this version of the game been recreated in a new programming language and has had the most official work put into it, only for it’s online to be so recurrently deadly?
@limechip That block-catching-up thing is probably the most frequent and devastating glitch I regularly experience. Happened while I was fighting the Ender Dragon with some friends the other day, which was extremely frustrating.
Things to avoid doing to not die in bedrock (An incomplete list): Placing blocks Standing on ledges Being near hostile mobs Flying Being in unloaded chunks Suffocating Going thousands of blocks from spawn (you can fall through the blocks) Falling Using a Trident with riptide
5:20 yea i remember that bullcrap one, its where if your hitbox is too close to the wall the SERVER thinks that your hitting the ground, and if your going fast enough it calculates fall damage and its ALWAYS lethal, regardless of what armor you got on or if you got featherfalling, its a huge pain in the butt and cause problems to no end on a server i used to play on with friends.
As a bedrock player i was once killed by an invisible zombie with no hitbox. Before anyone asks i was in single player it wasn't one of my friends trolling
Had that with creepers and ranged mobs a few times. An invisible charged creeper blowing up my base was my limit and I'm pretty much strictly on peaceful until they fix it.
@@SnowyOwl369 I honestly think my world or even my account may be glitched. I fall through nether chunks aswell if I log out there- should've bought Java while I had the chance 💀
Honestly, ghost blocks are such a problem that ive been conditioned for the longest time already to hear if the sound is there everytime I place a block while bridging
10:12 I reckon whats happened there is the server lagged as they were standing on that 1 magma block they were walking over. This is clear as the hoglin was chasing them at this point but doesn't appear again after. I think what the server saw was the player standing on a magma block and being hit by a hoglin, explaining the initial massive damage, and then following that the player is just standing on a magma block. Obviously the player never did this, but the server saw it that way. Basically, the unexplained massive damage at the start of their relatively slow death was due to the hoglin seen running at them before disappearing from the scene
As a “bedrockinator” a tip I have is when you feel things aren’t quite right you can test and try and mine a block, if it’s glitched it won’t show the breaking block animation with the cracks and all that. And there aren’t any particles.
@aquicandaquak822 I love how people figure out these "tells" different games incidentally have in them. For example: in Warframe, if you're mid-game and you suddenly get a big lag spike, congratulations! Another player has joined your session! Whenever I open L4D2, I have to wait a good while for it to load all of my mods, and if I close the game mid-load, the next time I open it, it will enable every single disabbled mod that was skipped when I closed it. I know my wait for it to load is over when the lobby music stutters on a bit. If anybody can think of some tells their games have, I'd love to see more of them!
One of my favorite things about the Minecraft community is that as soon as Mojang thought about adding hardcore to bedrock, the people that play bedrock started posting how they died on bedrock for no reason.
@@williamdrum9899 Yeah but then there's not as much incentive to build up an arsenal of "stuff", cause you'll never lose anything. Kinda takes the cool out of going super far away
Game developer here! My theory is that the netcode is seriously messed up. This looks like classic Server/Client Desync. Could be happening in cases of bad internet and lost packets. Typically games with decent netcode will account for differences between the client and server, often smoothing out any janky packets in between. I actually made a video of how lost packets affects abilities in overwatch (It was my bug busting episode on roadhog's hook and times where the hook "looked like" it was landing but it wasnt and no sound or hit markers appeared at all). I dont have bedrock but would love to experiment with this at some point, looks fun.
@@GoldenOcelot11 without looking at the code, here are some speculations. Desync can occur even if the server is localhost. Do you know if when a single player game is started, a local server is spun up or not?
@@TayyabTV Yes, that's the entire point of the video. There is no explainable source for having 1000 ping to yourself. Yes, it uses servers even when playing locally, but so does Java Edition and I sure haven't run into issues like this in it in my decade or so of owning it.
At 9:11 I think the first tick of "damage" may be falling through the block but he takes no damage as that block doesn't exist on the server. Then there is a period of nothing as he's falling before "hitting the ground"
8:37 that sound actually plays when you don't have anywhere to scroll in a menu. So, whenever the noteblock sound plays on the death screen, it's basically telling us that the player was moving their cursor when they died. Its like saying something in a dream and waking up mid sentence, still talking.
Honestly, the wither AI in bedrock is so broken. I spawned one in the nether once, and it’s like the thing forgot I was there. It just wanted to go hunting hoglins 💀
The server seems to think they aren't flying, however it tracks their positions, so they keep falling on the servers side as their position tracks back to the clients side and taking different damage based on how high they are, the suffocation is probably due to the fact that they fall through the solid ghost block for a second and then take the fall damage, as for that one where he kept jumping on the block, it is probably because the speed is being calculated differently on the server side and the server is thinking the player falls past the block, they are all probably caused by lag but who knows.
The issue is that even with nearly perfect internet you’re still going to lag on bedrock. Back before I upgraded it even further I’d get no more than 30 ping on every other game yet bedrock was still often times completely unplayable due to random bs happening all the time and lag spikes
The concept of blocks suddenly stopping to be real (and other Bedrock anomalies) could be a great concept for a Minecraft creepypasta. It's like the world itself is trying to fool you to death.
It's more of a looney tunes thing, like imagine playing with your friends then some mf looks down, sees the blocks under him stopped making sounds, and falls into lava
If the ghost block bug that randomly suffocates you by walking (the cobblestone bridge and torch clip) could be replicated consistently, I could 100% see it being used in attempts at Minecraft horror lol
7:56 it's kinda like that glitch with the guy jumping near a ledge and taking fall damage. the server isn't counting the player as flying, and drops them to the ground. and every time they hit the ground, it takes your new current position and drops you again.
My favorite part of the 1.21 update on bedrock was that the ominous vault doesnt exist in the creative inventory, the new items are not organized (tuff blocks in nature, not building blocks), and the mace having no cooldown
The bedrock menu organization is atrocious. 4 years ago when the nether update dropped, they just dumped all the new blocks at the top of the nature menu before more important blocks like grass and stone. 4 years later, it's exactly the same. I wonder how long until they properly organize the tuff blocks?
"Minecrat Bedbug Edition (6.9 Realistic update)" New features : - Torch damaging your fall - Randomly disappearing block - Died while on elytra - Minecoins - Died after 2 blocks - Minecoins - Died while placing blocks - Noclipping into lava - Minecoins - Disappearing world - Died while breathing air - Died using elytra - Minecoins - Heart Attack
You know, It could be fun to watch for a while, a Badrock hardcore where you have a set of "rules" to follow (or THE GAME ITSELF will punish you), like: can't place blocks under you to bridge or tower, you have to remember to be standing if you have to eat, don't use the elytra/trident/anything that makes you go up in the air and you have a BIG RED MACRO PANIC BUTTON on the desk to press to instantly close the game when you feel something is wrong! So much tension for something totally out of your control, feels like an horror rage game.
THATS SO RIGHT they are actually secret features that mojang added to make players become better at trial and error so you could play the game with 100% caution knowing that you're gonna die or not its called randomized luck not bugs lol lagva players am i right 😜😜😜🤪🤪🤪😜🤪
for the 9:10 one, I assume the suffocation damage at the beginning was the server assuming he fell, but he fell through a "block", and when he died was when he hit the ground, even though he was still on his bridge. the torch glitching was probably "hey, you're not up here, you can't place that there"
Nah people have been denying it for some time now saying it was just bedrock haters faking it and making it up but I play bedrock too damnit. what good does it benefit me to lie against bedrock 😂
@@Bupboy yh some people actually deny it and make it look like it's either fake or really rare when I reality it's really not. That ghost block issue Happen almost 70%of the time in my case when towering and it drives me nuts
As someone who used to play the game when it was still called Pocket Edition, im surprised they broke the system, in the early days of PE you did not take fall damage from nothing.
During high ping or high CPU usage, Minecraft will begin to bug out on modern PE and I've had the misfortune of experiencing these bugs: - suffocating in placed blocks, - suffocating on placed blocks, - suffocating on placed blocks over lava, - suffocating above placed blocks over water, - suffocating in a boat, - farm mobs suffocate in a fence, - drowning in a boat, - drowning on dry land, - ZARUWARDO!! All mobs freeze for 5s-1m and you can stack damage for when they return, however as soon as time restarts mobs will move at 5x/10x their original speed and possibly deal 20 attacks in under a second, - swam in lava without damage, - swam in lava with delayed damage, - ran in fire without damage, - ran in fire with delayed damage, - fallen from great heights, survive, then died 10s later, - fallen from a short height and be hurt x2, - (common, persistent bug) villagers fall through the floor and suffocate to death, - villagers lose their trades, - villagers walk into lava, - consuming items take 2s-15s longer to use (food/potions), - placed blocks deload after 1s-3s, - destroyed blocks disappear after 1s-15s, - mobs turn black, - farm mobs turn black and slowly no-clip through fence, - farm mobs jump on top of fence, - farm mobs walk through door, - floating gravel/sand. All the bugs I can think of. If we're including server lag, once an underground chunk failed to load on my client and I fell into a cave.
yes, exactly… I was really fond of Pocket Edition, it literally ran on ANYTHING even when infinite world was added and there were no bugs, except for redstone differences, but even then redstone was CONSISTENT at least by the way you can't play old versions of Minecraft Bedrock on new android today unfortunately… if the game freezes (by you either going through a nether portal or tabbing out of the game and then back in) it just keeps saying that minecraft is not responding even though it does respond
@@kabanod1mI started on some Pocket Edition version of 0.7.0 and I spent years working on PMMP servers for Bedrock. I quit a while ago, and I'm looking at these bugs now. I never remembered it being like this. When I played, the worst bug was the "pink glitch," which would make every texture forget itself and slowly but surely, your whole world, fonts, and UI would lose their textures and turn a burning pink until your game crashed. As goofy as that one was, you could just restart your game. The stuff in this video is basically unavoidable.
Most of the bugs with bedrock, come from it ALWAYS running on multiplayer*, even in a "singleplayer" world. This is because it needs to give you the ability to let friends join your world. This has the side effect of server lag however.
@@aurastrikeJava and bedrock do the same thing, run a server in the background and join to it, for open to LAN on Java and to let friends join in bedrock
@@RandomBloonStuff Can't. Client and server logic have been merged a long time ago such that there is no more "no server singleplayer" logic in the code. I remember when Mojang first did it years ago, it performed horribly with weird glitches like in the video, but it matured and was fixed. Bedrock however seems like it still hasn't been fixed after all this time.
On our bedrock server, we had just beaten the ender dragon, so I went to take the egg back through the portal, and upon returning, the game instantly killed me and deleted my inventory without dropping it.
I have a bedrock world that's almost 300mb big...and so ridiculously laggy. I mainly play on java, but to stop the fear of dying randomly, I made a backup wave and turned on keep inventory. It's ridiculous that I have to do this.
Yeah keep inv is basically a fun requirement in bedrock, and not just because of these bugs, but also because, and maybe I'm making this up, but mob spawns are far more aggressive in bedrock I've been playing quite a bit of legacy lately, and the mobs are very infrequent, and hardly agro even running past them, while bedrock spawns a waterfall of mobs that can see you from 3 chunks away
@@Bupboy YES THE SIGHT FOR MOBS IS RIDICULOUS. I swear, they can see me and be hitting me before I even notice there's a mob. It's ridiculous. Meanwhile in Java, it's the opposite problem. I have Minecraft Bedrock on the playstation, and Java on my pc. I played bedrock first and Java second, and the differences are RIDICULOUSLY OBVIOUS, and not just in the ways the games are coded, either. Mods are so much more accessible in Java, and I don't really feel like giving Mojang hard-earned money for a "mod" that I can only use in one world.
i have a world on my playstation that was almost a gigabit big, and i can hardly play on it last time i checked. trying to go in and out of the nether would make the world crash and doing anything felt like walking through mud. i couldnt ride through ice tunnels in the nether without having to stop every now and then to let the chunks load (which took way longer than it shouldve). im surprised mojang can pass off bedrock as a functioning game anymore seeing how janky and buggy it is in comparison to java
I've suffered from all of these problems before and it's the result of two things: - server lag, - hardware lag. For mobile of course. I once pointed out how old versions of Minecraft Bedrock ran smoother than this and I got poor-shamed for owning the same hardware that ran Minecraft without issue a few versions before but suddenly couldn't no longer.
everything before the bee update was just better.. literally every platform when that update came all bedrock platforms were forced into the s+++ game called bedrock where lots of things have unnecessary delays, loading times are ridiculous (looking at you settings button why tf does it take so long :| smh)
i find that even java is much laggier now, after the past couple updates - my laptop could run the game just fine even with egregious mods, but now running the base game is choppy :/
I'll be honest... I'm playing a Bedrock HC game right now, I'm like 118 game days in, and I haven't had a problem. Closest to death I've been so far was a totally fair-and-stupid decision on my part to check out the inside of the Woodland Mansion while wearing base leather armor...
For the elytra clips, what I THINK happened is that the server doesn't realise the player is flying, so it thinks that the player is in the air and SHOULD fall, so at the time that they WOULDVE hit the floor, they take damage, but they keep flying, and the server just thinks that theyre still in the air without an elytra and they take damage again, this cycle happens until the player dies for the people who don't understand, basically: the player sees themselves as flying in the air the server sees the player as in the air, thinking theyre falling, then teleporting back in the air and falling again
@@maxdrags3115isnt this a whole video of people experiencing this with more comments under this video with more people saying this happened to them among other bugs? I'm a bedrock player and I have that same question as them.
@@ThatHolyGamerIt's a desynchronization between the client and the server. The client also calculates it's position independently to avoid lag, because server ping can be >100ms and that kind of latency to move your mouse is unplayable of course. I think in singleplayer bedrock still uses a server but runs it on the device, just like java edition. What java edition does is it just teleports you back. But it's so wierd that this desync even happens in singleplayer, it really shouldn't because there are no way a packet could be dropped or something
7:38. My assumption is, because you can listen closely for the sound of him hitting the ground, that the game saw him as on the ground even when he was flying. Now the dmg came from the mountain, he was just falling down and down. The game saw him as walking forward (or sprinting) but then just walked straight down the mountain taking (clearly) fall dmg.
Wouldn't explain the third damage taken tho, since he'd be at the floor already, and no more cliffs. Most likely the client tells the server he is high up and the server accepts, except the server thinks he isn't flying - falling down and taking damage, then repeat the process. That is why 12:10 took many small damages (low height from ground) and stopped as he landed.
It's because the client isnt recieving the rubber band packets from the server becuase of lag and also the server and client have become desynced at this point. the player elytras sends a packet to the servers saying its at xyz the server says you're falling because you haven't activated the elytra and gives the player fall damage the player sends another packet saying its at xyz and so on untill the player lands and the server doesnt give any fall damage because the player is standing on a solid block which is synced between client and server. tldr client and server become desynced and stuff breaks
@@spicylemon2623Basically the server doesn’t see you gliding so it makes you fall from where you are, tries to correct your position but still doesn’t think you’re gliding so to the server you just keep falling over and over until you die or land
Chances are the same thing happens with blocks: You place a block over the ledge, server doesn’t see the block, you fall on the server but the client updates your position back to the block the server can’t see you you keep falling over and over unless you move out of the way of the block. Almost all bedrock deaths can probably be explained by a desync between client and server that Java edition either doesn’t have or is better at correcting.
I remember when I was younger I would play my bedrock survival world, and sometimes I would join the world to find I had died in my own house for no reason, ahh, bedrock you always used to amaze me with your twisted ways.
I started playing Minecraft through Bedrock edition years ago. It always felt like I was connected to a server and would just occasionally lag and pop back in a LOCAL game. You can't even pause the game with escape. They must not implement any sort of network loopback, and you just drop packets. That's my only thought.
also Java Edition uses TCP for all of its networking, and Bedrock uses UDP. Using UDP instead of TCP is generally good for performance but it's only as good as the developer makes it to be, because with UDP you have to write your own packet loss handling. with TCP there is no packet loss.
in bedrock single player worlds are a local server than the game directly managing the world and player, in java the game directly does that unless you do open to LAN
You are technically playing on a local server in both Java and bedrock (and lots of other games too) in single player, most games just aren't completely messed up like bedrock
@@sarandip no, in Java ever since 1.3 you've always been on a local server, even if you never opened the world to LAN. I'd provide proof here but links get my comments deleted and I can't insert pictures here
8:55 I think the "drowning" visual is caused by the hitbox of the person falling through the blocks (or at least what the server thinks is happening) causing them to suffocate as they fall through the blocks and then die from fall damage
i love how at some point they changed suffocation damage to be negatable by water breathing bedrock devs are DEFINITELY competent and dont change old features that have no fucking reason to be changed whatsoever :3
12:25 I think what's happening here, is that Minecraft doesn't see them as flying and puts a ghost player on his location every few seconds, and that ghost player keeps falling and taking fall damage. That's just what I think it is.
This is at least how it feels. I've been lucky with Bedrock so far and only died once from this lag or whatever it is. But that is one times too many. ESPECIALLY on Hardcore. Gj Mohjang.
This is some urban legend stories stuff, lol. "When you're playing Minecraft bedrock edition at midnight. Rumors said that if you are placing blocks and there is no sounds, you will die mysteriously"
Me and my brother had a survival world we'd play from time to time, and it was the highlight of my week when he had time to play. We built a house I was really proud of, a giant over engineered Villiger trading compound thing we were actively working on, and I had really fast horse named Hermes I was quite fond of. Then we got kicked while I was riding him, and when I joined back, he was gone. I got another horse I named after an equivalent god from another pantheon, but it just vanished from our stable a while later, I wasn't even riding it. Then we started getting these weird chuck corruption structures all around the our house that really ruined the landscape. We tried to remove them, but it just turned into a game of whack a mole. Then one day I got kicked, and couldn't rejoin. When I finally managed to join back on, my spawn point and inventory had been completely wiped. I had made sure to turn on keep inventory precisely because I knew I wouldn't be able to keep going if I ever lost everything, but it didn't matter. I couldn't handle being burned yet another time, so I just accepted that our world was dead, even if it meant we wouldn't spend as much time together. The game works just well enough to get you invested, only to rip it away from you.
@@professormutant3252 completely agree, however Play terraria anyway, it good, cheap and cool modding world fine and is easy, not that it's required, easily got over a couple hundred hours before considering mods, plus you can always just play both, the games literally recommend each other in splash text
Sad thing is is that many bedrock players have just either accepted this or refuse to acknowledge this, but both sides will say that it's the player's fault for not having a good enough device to play bedrock properly.
I’m in neither party though. I have literally never experienced anything like this and I’ve been playing bedrock for 10 whole years now, on a mixture of devices from phone to high quality gaming pc. I don’t know what to think but I am either really lucky or people are faking these videos because of the meme. I know it sounds insane but nobody I’ve talked to irl has ever seen anything like this (who have all played bedrock as long as I have) and it’s only online this type of thing seems to exist
@@SpremeCalami I play on PS5, which is actually the PS4 Edition. On singleplayer it's generally fine. If my world is set to Multiplayer I can experience minor lagspikes or ghost blocks when the internet slows down, but nothing major. When I'm on a friend's world however, their internet isn't the best as they live in the sticks - so a lot of desyncing and heavy lagspike issues can happen, I've experienced many of these issues regularly, including crops not getting re-planted properly requiring I go over the same patch two or three times. Thankfully only one desync has resulted in an unfair death; 1v1'ing a mob that just did lots of delayed damage to me after a lagspike. I also got dipped into lava in the Nether after ghost blocks disappeared under me, but by that point I had fully enchanted gear so lava was not fatal just annoying and panic inducing. Desyncs happen, but how the game handles them and just retcons things that happen client-side with information that server-side sees is what causes issues. For example, when placing ghost blocks you don't get rubberbanded back to where you were at the last block that was successfully placed, the game just lets you carry on. When it realises those blocks don't exist, it corrects those by "deleting" them, but doesn't update your positioning leading you to fall to your inevitable death - which completely defeats the purpose of sneak-placement, it's meant to stop you from falling off blocks. Ghost blocks produced by pillaring directly up also nudges you off when corrected, so that's also risky.
@@SpremeCalamiI've been playing Minecraft since almost the start and I started on legacy edition, it was great and no lag or issues. When legacy was killed and converted to bedrock there were so many optimization issues that there was so much stuttering and lag on single player. I remember seeing multiple chunks refuse to load in, block disappearing after being placed. it nearly killed me in the end just by towering up. bedrock is unoptimized and is an insult to legacy edition. I haven't had much experience with java only legacy edition since that was all I had before the switch to bedrock. I play bedrock a lot but it pales in comparison to legacy or java despite the little experience I have with it
@@zomadziasans8212 I wish Legacy Console was still supported. And dear god the crashes I got after trading with villagers and closing chests. They were so frequent I ragequit the game for 2 months. I'm glad they fixed those. At multiple points I had to download a backup copy of my world potentially losing hours of work because my Shulker Boxes were lost to the ether. For context, due to the way Minecraft saves the inventory first, and then the world - it would remember I took the Shulker Box out of my Ender Chest but not that I placed it in the world. As that particular Shulker Box had all my max-enchanted tools in it, it was a rather hefty loss to a sudden software closure, which is something completely out of my control. So I ended up just placing them in a specific spot in my house, never moving them, paranoid of losing them again. Having a Shulker Box sat forever in a single spot for fear of a game crash completely defeats the purpose of Shulker Boxes.
I wish Legacy Console Edition was still supported. My word the crashes I would receive after trading with villagers and coming out of a chest inventory. They got so frequent I lost my Shulker Box containing all my max-enchanted tools twice, and both times I had to restore my world to older backups, losing hours of progress. I ragequit for a couple of months because of them. Thankfully that was eventually fixed but I kept sending in error reports every time it happened. For context of why that happened: Minecraft saves the inventory first and then the world. I still don't know why I had game crashes closing inventory menus but I ran the risk of losing my Shulker Box whenever I'd take it out of the Ender Chest (one such inventory menu) and placed it down in the world - it would "remember" that I took it out of the chest, but not that I placed it down as a block, so it went bye-bye. I got so paranoid of it happening again I ended up just keeping them all in a permanent space in my house, which completely defeats the purpose of a Shulker Box.
7:37 I have already experienced this, basically the server thinks you are still in the same spot but on the ground and when there is a bump or a hole you still take fall damage.
8:47 as a bedrock player, I can inform you that the sound plays because they are trying to continue to move while the death menu shows, this causes the noise to play only with a controller
8:00 I'm pretty sure the server doesn't know he has an elytra, so while he's flying downhill, the server thinks he's just walking and so taking fall damage when he falls multiple blocks
In my bedrock world, the drowned’s just… refuse to attack me a lot of the time. Like, I’ll be in the water and they’ll be right next to me, but instead of attacking me, they just look at me like “sup bro”. I didn’t know they’d be chill like that.
As a dedicated bedrock player, I think I know part of what’s happening Worlds in bedrock edition are set to allow multiplayer by default, so every world is treated like a server (it’s why you can’t pause and stuff). This means that if you’re playing bedrock edition and your wifi gets slightly delayed or disconnects, your world starts lagging a lot. Bedrock edition is also terrible at dealing with lag, it tries to update mob + player positions and then update blocks and then update chunks, so any changes made to the world are calculated after the players damage, resulting in a lot of random fall damage. It also makes a lot of chunks not load, and unloaded chunks in bedrock are solid, which can cause suffocation damage until it finally loads the chunks.
As a Java player, I've always felt half jealous that Bedrock has that easy bridging... But half suspicious that stuff like this could happen. Sure enough, looks like it's A Thing that could really get in the way when building. 😅 (Though the fact that the lower blocks disappeared was most likely what led to it in this case; he was trying to build along those two blocks which the game likely WOULD have respected, except it decided that those blocks weren't really there. Hence it switching to bridging behavior instead. That's my understanding of it, at least.)
Bedrock servers is just being glitchy for no reason,when i logged on a server with a high ping,i kept spawning in the ground, Mojang should fix these as soon as possible.
that's expected for high ping. the server isn't fully loaded yet, so the client will keep trying to drop you down. but on the next moment the server sending you new data, the client would put you back on the surface. also expected on java.
8:33 that noise is actually played *any time* you cannot move the green select box thing, and because you tend to hold directions to go places, if you are holding a direction when you die there’s only 1 option so you can move the green select box so it plays it *non-stop* until you stop holding a direction
On that cobblestone bridge one, it looks like a weird desync glitch. I think he’s calculated at 1 pixel too low, which leads to the server (maybe) calculating him falling through the block (giving 1 damage as his head goes through), and eventually hitting the ground. As a programmer, this is embarrassing. It’s using calculations to interpolate position, but the calculations are tied to fps, so when frames drop, the distance becomes greater. A similar glitch exists in Doom (and Doom 2) where if you have enough speed, the calculations put you on one side of the wall on the first frame, and the other the next.
And since multiplayer servers run on TPS rather than FPS, thanks to the idiosyncracy of Bedrock worlds being multiplayer servers even in singleplayer mode unless you specifically disable that (or even potentially in spite of disabling that manually), server lag and other forms of desync causes the equivalent of frame dropping.
This is literally ALL desync between server and client. The elytra clips are purely instances where the server believes the elytra was never activated, and therefore always have a small initial bit of fall damage as it thinks you fell from the jump. The issue really becomes apparent as the desync has no method to fix itself, the server keeps playing you in the air where your client says you are but the server STILL thinks you never activated elytra. So you fall again, and again.
@@kennyholmes5196 that's not an idiosyncracy of Bedrock. Java edition also runs a server locally since 1.3. From Minecraft wiki on 1.3.1 update, under General: "Made singleplayer internally use a multiplayer server."
I've yet to experience any of these things. But I did get killed a few times by being attacked whilst in a chest or my inventory, and I would open up my Emote menu by chance of pressing left on my d-pad; I wouldn't be able to break free of the menu in time to kill the thing attacking me and died constantly emoting. Safe to say, I reconfigured my emote wheel to [unset] and completely ignore the feature now.
8:34
That noteblock sound would be the player holding up on their stick or d-pad on the controller. The sound is basically telling you: "No, you cant scroll up because you can only respawn".
Thank you for explaining I was also really confused by that
It also happens in menus, I thought it was an interesting feature at first
Ohhhhhh... That's why it wouldn't happen when I tested it out...
Wow thank so much 200 iq man
@@PhoenixSC thank you for the wonderful video. "Never turn on hardcore mode" is what I say to series made on deadly content. Like the Java parasite mod.
I know Mojang has been trying to add more "real" features but implementing heart attacks is just brutal
it's the american minecraft version, they had to add some realism to it
btw hi colon :D
Cologne will you do a face reveal
Pffff hahahah… man this is bull
Minecraft Bedrock Harcore, but When You Die You Blue Screen
boy i love having a stroke in minecraft
There's a certain horror element where you realize the world around you has stopped making sounds in response to you doing things, and you know you have like, seconds before you mysteriously die.
I thought the same thing. I would pay to watch a short horror short or map based on this
King crimson
They added strokes to minecraft
Death note fr
@@wofama3436 Minecraft Bedrock = Jojo reference!?!
Reminds me of the funniest bug report I’ve ever seen for Minecraft bedrock:
“Interacting with a beehive with honey bottle in hand *refills the hive*”
Tf why they patched it 😂
The Bees! The Bees!
What wait how???
Me: *takes honey out of hive*
Bees: 😡🤬😈
Me: "oh shit my bad" *puts it back in*
@@shadow13392 cuz that isn't... supposed to happene
In my bedrock world for some reason my hearts never fully recharge. I always have one half of a heart missing. But, bedrock being a mysterious and fair god, I can reach 0 hearts of health and still be alive.
Ahhh the balance of bedrock, taketh a half-heart away, giveth a half-heart
This is like a shady pact with some obscure deity.
Never fully healthy, never fully dead.
Fair? I explode mid air and got squat.
its cuz its bugged and 9.5 hearts visually is actually 10 and 0 hearts visually is actually half a heart
As someone that has hosted a bedrock realm for about 2 years now, we still have people mysteriously drown in our fully conduit covered spawn
Oh no... I just made an underwater base with conduits lol
When people teleport, on occasion they just decide to fall through the floor, so I had to make a system that teleported them to spawn when they hit the void.
I can’t do anything like that bc it’s fully vanilla survival without cheats, but that’s a good way to combat it
Bedrock moment
@KnownNiche1999 Woah, _BEDROCK MOMENT??!_ Gee, it's almost as if that's what this *entire video is about*
I knew it. Bedrock version got hijacked by herobrine. It became a psychological horror game now. You can notice sound or visual cues, that may or may not save your life, yet still things are out of your control.
That's why the version changelogs stopped saying "Removed Herobrine" because he became too powerful for Mojang to remove.
respect the bugrock community
@@Xaruzo Hardcore Incel
@@flooriiian*harcore incel
Ah so that's why he wasn't seen in Java anymore, he MOVED.
If you look at some of the death messages, some of them don't even have one, all it says is "you died"
Herobrine
The ones without death messages were from before mojang updated the death screen
@@professorbrian9197 No, herobrine
They died, thats what happen
We’re in Darksouls.
7:56 Explanation: The server forgets that you are wearing an elytra and therefore thinks you should be falling and taking fall damage. But once you take the fall damage, the server temporarily realizes you are in fact wearing an elytra and are in the air, until it immediately forgets and sends you "falling" again. The cycle repeats over and over.
Minecraft Alzheimer edition
2:52
It’s like a cartoon. He pauses for a second before he falls. Peak comedy right there.
Bro thinks he’s Wile. E Coyote
he holds up the "help me" sign
YAHAHAHOOO
"Ruh Roh Shaggy"
He almost went to the backrooms
There’s a glitch notorious in my friends realm we call the “rain glitch” where it’s just raining infinitely for you, and if u riptide through the air, it will give you fall damage occasionally.
Ope I think that one was showcased lol
Sameeeee
Yeah, I and my friends were playing , it was always raining damn
It’s incredibly annoying, but it’s hilarious on servers. I seem to be the only one to experience this, and everyone called me crazy until I started Riptiding while the sun was out. This Glitch is entirely client based, because the rain does not effect the world; snow golems don’t take damage, cauldrons don’t fill up
And they want us to pay a billion dollar company for realms.
All this happens and Bedrock still has the audacity to call Keep Inventory cheating
Also I should note that the map at 7:02 isn't actually useless because Bedrock has a nice feature where if you take an Overworld map into the Nether you can see your relative position in the overworld, (with a red marker) which could come in handy when trying to link portals
That's really cool.
Wait what? That's sick af
I miss when the maps showed your coords on legacy
Oh yeah I forgot about that, it’s pretty cool.
whats funny is that feature is a bug lmao
That reminds me, when playing bedrock, the game would just spawn me *underwater*, so the moment the world loaded, you were already at the death screen.
I wonder how long the hardcore last with that feature :]
*harcore
Yeah mojang should fr fix the… everything befote adding hardcore
My bedrock moment happened on a Realm - I built a custom nether portal leading to my nether base, but every time I came back, it would generate a new nether portal around 200m north. So eventually there was just this obsidian stonehenge in the middle of town that no one could get rid of because I kept accidentally making new portals
Well hey, at least you have an infinite obsidian farm
I had the same thing, but it kept placing them when I went to the overworld
This exact thing happend to me too on a cross version server.
I couldnt destroy either portal otherwise I would softlock myself in the Nether.
That's not a bug, just a bad result of a bad feature
@@mrowlsss...no its a bug that is a result of a feature
The cherry blossom one at 4:38 has the same energy as a cartoon character running off a cliff and only falling after they realize there's no ground beneath them
"Lag" *dies*
looney tunes ahh lag 💀💀💀
Same for the one where they're bridging in the nether
On a normal bedrock survival world none of this ever happens
I think I got an idea of whats happening here. The problem is basically that the server is running behind the client and the client never gets notified of that fact. In Minecraft Java when the Server and Client get out of Sync you can tell pretty easily because the Server will start correcting the client in order to sync up again. Bedrock just skips this step (or does it less frequently) to archive better performance and the Server and Client fall out of sync. Best example is the Elytra Clip. The Client initiated the flight but the server never got that update therefore the server thought the player jumped down the cliff. Now the client tells the server that the player is still in the air but not that the player is flying. The server lets the player fall and tell the client the player received fall damage. This gets repeated until the player dies.
I would gues that in this case they only send the flying flag when the player starts and stops flying to save on latency so if that packet gets dropped the server never realizes that the client started flying. Its honestly just bad protocol design for the sake of performance.
TL;DR: Server desync doesn't correct instantly on bedrock
its so funny that the stated reason for not adding all three mobs is because they want to make sure the one new mob has zero issues, and then an entire version of the game is put together so poorly that simply performing the base features of the game will cause it to unravel.
Yep, Mojang's a joke.
Microsoft doesn't know how to code for anything.
Mojang is stupid too I guess
just play java, they should've just put java on all devices, are have the original legacy edition, way less bugs
I think the issues might actually derive from the Java edition of the game, which is itself living on borrowed time
@@victoralexandervinkenes9193 Please do explain how the issues on Bedrock, coded in C++, exist due to Java, coded in... Java.
8:10 in bedrock sometimes flying into something and dying doesnt always give "[player] experienced kinetic energy" sometimes i get, "hit the ground too hard", "fell from a high place" and one time i got "suffocated in a wall"
No no no basically you see even on local it creates a "server" sometimes this server doesn't render you doing something but it does render your position and as an anti cheat bc of hacked clients that take advantage of this to fly by settting your client position to something it gives you fall damage as if you were falling normally and when the sound stops that's bc of a desync between the server and the client in some cases it doesnt render your movement and it will keep you from updating it i think
a new japanese light novel title "I Experienced Kinetic Energy and Hit the Ground Too Hard, That One Time I Got Suffocated In A Wall In Another World"
@@starjadiancloneinvestigato1772 😭
@@starjadiancloneinvestigato1772 xD
In this clip hes TEN THOUSAND blocks away from spawn. I've played xbox Minecraft for years and i just know not to go far out. Your game WILL mess up. But obviously theres a bigger problem happening with bedrock edition
As a bedrock player, the only update I want for bedrock is to be able to build on the nether roof
FOR REAL
we need this
that is one of the reasons i play legacy xbox minecraft
It pisses me off. Like, why can't we have it? You can get up there and get stuck up there. That's the most basic reason to add it in.
I also play bedrock and i absolutely agree
0:18 how fundy was born
The Internet needs more jokesters.
Late timestamp
True
Oh boy…
For wanting it to be the main version of Minecraft, it’s crazy how much shit Mojang let’s happen in Bedrock… like I REALLY REALLY want to know their thought process behind leaving these game-breaking bugs in the game for 8+ years.
I think those bugs are because every world is basically s little server on bedrock, but I'm not sure
@@creepster1509 Except Java has the exact same thing and has *none* of these problems
I remember how happy I was when they removed the block lag bug back then. But after that, block lag just kept coming back
@@creepster1509It’s the same thing on Java, except that on bedrock the calculations for positions are calculated differently between client and server for no reason
Probably Microsoft rather than Mojang. IMO any of the issues you see in Minecraft in general are Microsoft’s fault rather than Mojang.
For the elytra deaths, the game thinks you’re falling over and over while you’re flying relative to your height. So the game thinks you’re just falling over and over as long as you’re in the air. I’ve experienced a glitch like this in survival where I got the ability to fly like in creative mode but took damage if I was too high. Bedrock is so strange.
Did your device lag before that bug happened?
@@MrBrineplays_ nope. It just happened
no it means you just suck at the game
not a joke pls trust
@@aaaaaaaaaaaaaaaaaaaaaaaaa..... Found an ipad kid
Fun challenge run "Can I speedrun the game in harcore before bedrock loses a packet and kills me"
THE ATTENTION TO DETAIL OF THE SPELLING OF "HARCORE"
@@dudical111yeah because that's what its called, anyone who tells you otherwise is a LIAR and they need to be locked up
2:48 as an old treassure wars player on the hive, if the blocks don’t make a sound, just keep bridging as fast towards your destination or back the frick up
As a Bedrock player, the only mysterious damage I've taken is occasionally taking a heart or two when I'm pillaring. I have yet to mysteriously die. I also play with sound off, so I won't even notice when it happens.
Same! I've also done crazy stuff like mining out dozens of chunks, but never got mysterious fall damage while doing so. In all my time playing, I can only remember getting weird fall damage a single time. I play on mobile and without sound, but maybe consoles are worse.
Oh but I *have* died from glitching through flying machines. Those things are unreliable as transport on bedrock edition, or at least they were two-ish years ago.
Playing without sound? Are you insane?
same
I cant stand the sound of walking on grass so I turn sound off as well, I’ve died from drowning on land quite a few times now tho
i've mysteriously died before, fell through and slid off of blocks numerous times, I've even gone about 5 minutes where all leaf blocks were non-collidable and only for me not my friend, bedrock is a bundle of bugs
i like seeing them realize for a split second they have been marked for death
7-3: NO SOUND, NO MEMORY
CHALLENGE: BECOME MARKED FOR DEATH
@@gmdtungsten the fandoms overlap
2:52 as a bedrock player as soon as I heard the block sound stop playing I knew where it was heading, I’ve learned to get back when it stops
Same
Does it happen in singleplayer too?
@@Yashu_Playzoccasionally. Used to be really bad in 1.18
@@Yashu_Playzif it's similar to how java edition works, singleplayer is just a server that's running in your computer that only you can access unless you "open for lan"
if it happens on multiplayer I'd assume it happens on singleplayer too but im not 100% sure if it works the same way on bedrock
Yea most bugs are on multiplayer. I’ve played single player worlds for hours with minimal issue but as soon as two people are loading in different chunk areas at once bedrock breaks down
11:18
The way Fundy just says “Why is he a leaf?” just scratches in itch in my brain.
2:36 You know that feeling when you trip on something but dont fall, yet it gives you a micro heart attack? I guess this is it
Hi
Lol
Did Phoenix just make fundy watch his parents have a kid
Yes
Bruuuuh I absolutely forgot about Fundy, how could I? 😭
merge go
???
He also showed him in the same clip, that he could be his dad
A big issue bedrock has for some reason, during SINGLE player, when your device loses Wi-Fi, it will switch to offline, the entire world lags and you end up having things like 2:47 take place.
Spaghetti code
FR 😭😭
It’s because bedrock runs every world, whether it be a server or a single player world as a server. And that means when it lags. There is nothing you can do about it.
Java has an internal server as well, though I guess bedrock's internal server is just connected to the internet so other players can join your world (causing lag where there should be none).
@@MrZoom689 Only that java does the exact same thing and it works
0:13 *and that's how Fundy was born!*
That low pitched note block sound is the sound that plays when you try to scroll up or down, but you've already reached the top/bottom option and can't scroll anymore
Oh so thats why i havent heard it cause im on pc. And the clips were people on console and they presumably had their left stick held down. I thought i just missed the sound when i died tbh
that noise is ingrained in my skull
@@thepootato held up, actually.
Here's an even more bizarre bedrock edition story than everything in the video.
On my 8 year old tablet that barely ran minecraft on life support, i had a horse I took traveling and it drowned in one of those annoying water holes before i could save it.
I picked up it's saddle, had it for a while, it wasn't a ghost item cause i put it in chests, had it in my inventory for days, re-logged several times and it was always there.
One day I went in the same direction as i did with my horse when it drowned and THE HORSE WAS ALIVE just wandering casually. It had it's saddle on, the world was singleplayer so no-one was messing with me and the saddle i picked up was still in a chest when I brought the horse home.
horse really said "But it refused"
“Did you die??”
“Sadly yes. BUT I LIVED”
I had ghost horses alll the time on my fire tablet. Looking back, playing minecraft on it was like a fever dream.
Bro got his horse back mine just dipped like my dad, didn’t even get his saddle or horse armor back
He respawned!
Bedrock Edition really screams a great Looney Toons gag ngl.
My thoughts exactly, especially that cherry leaves one 😂😂😂
the disappearing netherrack I'm pretty sure is an actual one
To me the slab growing into a full block was hilarious
Yeah 💀
😊
I love it when you pick up a lot of blocks, and you'll have an empty inventory spot, but it's actually just bugged out. I have to restart to get it back, or sometimes i can get it back by putting the same block in that spot, but sometimes it doesn't. I'm not sure how it works completely yet.
im so glad i switched to pc, playing bedrock edition has always been miserable due to mojang not fixing the horrendous lag that is somehow still experienced even in singleplayer worlds
I'll bet it's because they made the netcode incredibly "performant" by making it run on a single thread with a bunch of other stuff and didn't allow it to be allocated to a less busy thread if the system could support that. After all, it has to run on smart phones using the exact same code, so they probably thought the 3% performance increase on iPhones was a steal, without considering that an xbone, wiimii, ps4, or an objectively better piece of hardware might be able to produce significantly larger and more frequent packets and clog the system worse than the toilet at your local gas station and cause constant desyncs. So, basically the worst possible way to copy Java.
The deaths themselves are largely because bedrock prioritises the server over client for player position and movement calculations to prevent flyhacking, (while still allowing the player's coordinates to be set by the client, because why be consistent), so if a desync occurs and the server calculates that you should have fallen, then you will take the fall damage. Because their communication is being throttled by the netcode not having enough CPU allocation to process the packets, they're often desyncing, with only the small/high-priority packets (like player coordinates and momentum) getting through and those slowly, resulting in the server often making mistakes and thus falling through blocks because it simplified a collision calculation, or dropping the player from world height because it didn't get the message that they're supposed to be flying, then passing that result back to the client and overriding the client's statement that everything is fine.
Basically it's the opposite of ghost bridging in Java (where a desync basically lets you fly using ghost blocks because the client overrides the server saying that you should have fallen).
An alternative explanation is that only the client doesn't actually have the checks for damage built-in and so just trusts the server implicitly, though if that were the case I'd expect it to be much more common.
i was about to do that, then i installled a sodium mod and it boosted my fps from 60 to 500ish on 32 render distance @@SmD-ff5xd
@@SmD-ff5xdJava is poorly optimized look into optimization mods for Java they’re pretty easy to install and can triple your fps
Bugrock or Lagva, choose your poison 😭
The former was very forgiving to potato PCs (and crossplay) until it deleted chunks of our builds (MCPE-98789) out of nowhere the following day, we moved from the latter where TPS sometimes inconsistently spikes (even in single-player) and the Fabric performance mods became a necessity for a seamless experience after 1.12.2 onwards. (Somehow unmodded 1.20.1 is smooth so far so kudos for them)
I think mojang should stop hiding behind tech debt and different platforms/codebases to excuse the version disparity and general mistreatment of bedrock
Yeah, as a longtime realm owner, Bedrock is notorious for the immense amounts of glitches/horrible issues in the game. Here’s a few things you’ll wanna try for yourself, as well as a few past bugs that existed for prolonged periods of time:
1. Create 3 scoreboards and apply 0 score of those scoreboards on every entity. This produces lag on realms specifically, especially when multiple players in the realm. Even if your frames are smooth, entities will move significantly slower.
2. In the past, there was a glitch where the model or occasionally hurtbox of an entity is either far away, or unloaded. This was an issue that occurred primarily on realms back in the day, but also existed on single player in some occurrences. This results in invisible or invincible mobs that can and will attack you.
3. Fall damage struggles to register in the game, and being teleported in the air will often result in an infuriating death. In the perspective of the victim, they will experience random death. In the perspective of other players, the player will walk around with their model rapidly being sent back up into the air and thrown into the ground again.
4. If a command block is scheduled to create a particle effect from outside particle render distance, it will produce massive lag.
5. Mobs move slower depending on the amount of lag or entities a server is experiencing, resulting in pathetically easy combat. If something occurs to deal with the lag problem in the middle of a battle, enemies will seemingly speed up significantly.
6. Sometimes when blocking with a shield, it will take upwards of 5 seconds for it to activate.
7. Putting behavior packs in realms is a pain in the butt.
8. Horses, Boats, Minecarts, & Donkeys can be affected greatly with 6’s effects, rendering them useless. Elytra is unaffected, and will therefore become significantly buffed in times of severe server load issues.
9. You have to crouch to use a shield, which feels really cursed.
10. Caves & Cliffs has damaged several pre-existing worlds and realms despite the developers claiming it would not overwrite already-loaded chunks.
I like how number 9 isn't a glitch, just a terrible feature.
I get why they did it, but it just does not work with the mechanics of the game.
If you're early game and a trident drowned spawns in your river, you're just hecked.
- you can't hit them without going in the water
- you can't swim because you have to crouch to block the tridents
- if you don't kill him fast enough, you're either going to drown or get impaled
I also frequently struggle to kill skeletons without taking at least _some_ damage. Because the amount of time it takes to activate a shield means I can never really move too far between shots. It's better for me to just tank a hit and try to kill them as fast as possible
@@DaNintendude The entire purpose was for parity with Pocket Edition, but Pocket Edition still has an increased reach.
It’s not even a complaint about Pocket Edition being OP or something. It’s more about an unnecessary addition.
Why restrict console and keyboard players? Pocket Edition can do its own thing to work alongside the other platforms, it doesn’t need to downgrade the other platforms. It’s just a matter of controls.
Java:
And I don’t have any issues concerning pointless deaths…
I experience that darn shield delay literally every time I use the shield and it’s awful.
And I’ve gotta add my own experience and that is with nerd poling.
Quite often when poling upwards one of my blocks will not be tangible, this results with you standing inside the block you just placed, and soon afterwards the game will “catch up” and will make the intangible block you are standing in, tangible, causing the block to shove you sideways and fall to your doom.
Otherwise I also noticed taking fall damage after doing some parkour jumps. (Although not nearly as constant as what is seen in the video, but regular enough to be note worthy)
How has this version of the game been recreated in a new programming language and has had the most official work put into it, only for it’s online to be so recurrently deadly?
@limechip That block-catching-up thing is probably the most frequent and devastating glitch I regularly experience.
Happened while I was fighting the Ender Dragon with some friends the other day, which was extremely frustrating.
Things to avoid doing to not die in bedrock (An incomplete list):
Placing blocks
Standing on ledges
Being near hostile mobs
Flying
Being in unloaded chunks
Suffocating
Going thousands of blocks from spawn (you can fall through the blocks)
Falling
Using a Trident with riptide
So basically the only way to survive is sitting on the menu screen?
@@superNova5837 only if your game doesn't freeze at specific percentages on the loading screen.
Truly a bedrock experience
And bad wifi lol
Also teleproting and being near anything that can deal damage
5:20 yea i remember that bullcrap one, its where if your hitbox is too close to the wall the SERVER thinks that your hitting the ground, and if your going fast enough it calculates fall damage and its ALWAYS lethal, regardless of what armor you got on or if you got featherfalling, its a huge pain in the butt and cause problems to no end on a server i used to play on with friends.
As a bedrock player i was once killed by an invisible zombie with no hitbox.
Before anyone asks i was in single player it wasn't one of my friends trolling
Had that with creepers and ranged mobs a few times. An invisible charged creeper blowing up my base was my limit and I'm pretty much strictly on peaceful until they fix it.
@@fallowfloof that must've absolutely sucked.
The server thought you were on a different chunk is my guess
@@SnowyOwl369 I honestly think my world or even my account may be glitched. I fall through nether chunks aswell if I log out there- should've bought Java while I had the chance 💀
Even if it would've been a friend, they still would've had hitbox
Honestly, ghost blocks are such a problem that ive been conditioned for the longest time already to hear if the sound is there everytime I place a block while bridging
Same. I havent run into the bridging issue since 1.16 and after moving to pc a year ago i havent been able to witness the xbox weirdness
The issue i get is having to eat food 3 times before it processes but ig that's just lag
So what do you do if you don’t hear anything? Do you go back, stay still, or literally just die like in these vids?
@@palecaptainwolfkayls8499 you re join the game
I have things like this happen in Java is the dumb thing
People say "It's not the fall that kills you, it's the impact".
Mojang begs to differ.
Me: *Jumps once* Minecraft servers: "That's quite an lengthy height there pal."
it’s just the thought
“It’s not the fall that kills you, it’s the illegal argument.”
10:12 I reckon whats happened there is the server lagged as they were standing on that 1 magma block they were walking over. This is clear as the hoglin was chasing them at this point but doesn't appear again after. I think what the server saw was the player standing on a magma block and being hit by a hoglin, explaining the initial massive damage, and then following that the player is just standing on a magma block. Obviously the player never did this, but the server saw it that way. Basically, the unexplained massive damage at the start of their relatively slow death was due to the hoglin seen running at them before disappearing from the scene
but they died of suffocation damage
As a “bedrockinator” a tip I have is when you feel things aren’t quite right you can test and try and mine a block, if it’s glitched it won’t show the breaking block animation with the cracks and all that. And there aren’t any particles.
ain't no way bedrock got strategies to not die of suffocation
@@daniboi_oneninefive survival of the fittest out here
Ah fellow bedrock survivor
Another tip is that when all the creatures stop moving
Pray
@aquicandaquak822 I love how people figure out these "tells" different games incidentally have in them.
For example: in Warframe, if you're mid-game and you suddenly get a big lag spike, congratulations! Another player has joined your session!
Whenever I open L4D2, I have to wait a good while for it to load all of my mods, and if I close the game mid-load, the next time I open it, it will enable every single disabbled mod that was skipped when I closed it. I know my wait for it to load is over when the lobby music stutters on a bit.
If anybody can think of some tells their games have, I'd love to see more of them!
@@daniboi_oneninefive Its the human nature to try to prevent randomly flopping over and dying.
One of my favorite things about the Minecraft community is that as soon as Mojang thought about adding hardcore to bedrock, the people that play bedrock started posting how they died on bedrock for no reason.
Almost as if death in regular play has basically zero consequences if you have keepInventory set to true
@@williamdrum9899 Yeah but then there's not as much incentive to build up an arsenal of "stuff", cause you'll never lose anything. Kinda takes the cool out of going super far away
hopefully these clips encourage mojang devs to actually fix bedrock
@@Frontalllllas soon as notch left it started going down in 2014 we need him back
@@ProbablyNotAChicken it's for bedrock players
I knew we were cooked ever since Mojang stopped putting "Removed Herobrine" in the update logs
he’s too strong. they can’t fight herobrine anymore
5:55 that coal texture is horrendous
It looks like rabbit droppings lol
dookie ore
Wild name 💀
Game developer here! My theory is that the netcode is seriously messed up. This looks like classic Server/Client Desync. Could be happening in cases of bad internet and lost packets. Typically games with decent netcode will account for differences between the client and server, often smoothing out any janky packets in between. I actually made a video of how lost packets affects abilities in overwatch (It was my bug busting episode on roadhog's hook and times where the hook "looked like" it was landing but it wasnt and no sound or hit markers appeared at all). I dont have bedrock but would love to experiment with this at some point, looks fun.
But these are local servers with 0 ping. How are you losing packets over RAM?
@@shny_scott were these clips on single player?
@@TayyabTVyeah, it’s a quite common thing over single player
@@GoldenOcelot11 without looking at the code, here are some speculations. Desync can occur even if the server is localhost. Do you know if when a single player game is started, a local server is spun up or not?
@@TayyabTV Yes, that's the entire point of the video. There is no explainable source for having 1000 ping to yourself.
Yes, it uses servers even when playing locally, but so does Java Edition and I sure haven't run into issues like this in it in my decade or so of owning it.
The “making no sound” thing is like a horror movie lol I get spooked every time one of you points it out-
At 9:11 I think the first tick of "damage" may be falling through the block but he takes no damage as that block doesn't exist on the server. Then there is a period of nothing as he's falling before "hitting the ground"
hehe number
Mr President, the second block has failed to place
@@Pixal_Dragonbro took the opportunity beautifully lmao
9/11
@@Pixal_Dragonmr president, the second mobfarm has experienced kinetic energy
8:37 that sound actually plays when you don't have anywhere to scroll in a menu. So, whenever the noteblock sound plays on the death screen, it's basically telling us that the player was moving their cursor when they died. Its like saying something in a dream and waking up mid sentence, still talking.
Trust me, I've been playing on a Survival World in Bedrock for 3 weeks and I've already summoned like 4 Withers and haven't killed a single one.
Honestly, the wither AI in bedrock is so broken. I spawned one in the nether once, and it’s like the thing forgot I was there. It just wanted to go hunting hoglins 💀
@@DannyDevitoOffical-TrustMeBro kept you as a desert😈
Java withers are like like squeaky toys, bedrock are like bedrock
@@DannyDevitoOffical-TrustMeBro if you hit it it will get mad at you and good luck geting it to forget you have to get like 100 blocks away from it
Yeah there too hard
The server seems to think they aren't flying, however it tracks their positions, so they keep falling on the servers side as their position tracks back to the clients side and taking different damage based on how high they are, the suffocation is probably due to the fact that they fall through the solid ghost block for a second and then take the fall damage, as for that one where he kept jumping on the block, it is probably because the speed is being calculated differently on the server side and the server is thinking the player falls past the block, they are all probably caused by lag but who knows.
no they auffocated from thin air
@@zixvirzjghamn737it's so sad that steve died from asphyxiation😔
The issue is that even with nearly perfect internet you’re still going to lag on bedrock. Back before I upgraded it even further I’d get no more than 30 ping on every other game yet bedrock was still often times completely unplayable due to random bs happening all the time and lag spikes
The concept of blocks suddenly stopping to be real (and other Bedrock anomalies) could be a great concept for a Minecraft creepypasta. It's like the world itself is trying to fool you to death.
underrated comment
It's more of a looney tunes thing, like imagine playing with your friends then some mf looks down, sees the blocks under him stopped making sounds, and falls into lava
@@gneu1527 That's if you're with friends, sure.
If the ghost block bug that randomly suffocates you by walking (the cobblestone bridge and torch clip) could be replicated consistently, I could 100% see it being used in attempts at Minecraft horror lol
The ghost blocks are most common near the stripelands which i will nickname the ghostlands
7:56 it's kinda like that glitch with the guy jumping near a ledge and taking fall damage. the server isn't counting the player as flying, and drops them to the ground. and every time they hit the ground, it takes your new current position and drops you again.
bro I've never had a major bugrock moment and I feel bad seeing ppl loose their stuff because of a glitch they can't control
Cant relate, like & retweet if you have keepinventory on
*Bedrock ❤️
@@ThatLocalBit
bugrock sweetie ❤️
@@ThatLocalBitit was on purpose-
I've had several bugrock moments, but none have made the game as unplayable as these.
They should honestly rename "fell from a high place" to "%s had a heart attack" would be more realistic
My favorite part of the 1.21 update on bedrock was that the ominous vault doesnt exist in the creative inventory, the new items are not organized (tuff blocks in nature, not building blocks), and the mace having no cooldown
Oh fun
No cooldown for mace is more like a feature cause there are no cooldown for every weapon in the game
1.9's combat mechanics aren't on Bedrock, so no melees have a cooldown
ominous vaults are also not in the Java creative inventory because they’re actually a regular vault with some properties changed.
The bedrock menu organization is atrocious. 4 years ago when the nether update dropped, they just dumped all the new blocks at the top of the nature menu before more important blocks like grass and stone. 4 years later, it's exactly the same. I wonder how long until they properly organize the tuff blocks?
It's so sad to see that bastion guy find out that he was about to die and try to run to the chest to save his stuff. Rest in peace my man
"Minecrat Bedbug Edition (6.9 Realistic update)"
New features :
- Torch damaging your fall
- Randomly disappearing block
- Died while on elytra
- Minecoins
- Died after 2 blocks
- Minecoins
- Died while placing blocks
- Noclipping into lava
- Minecoins
- Disappearing world
- Died while breathing air
- Died using elytra
- Minecoins
- Heart Attack
you forgot one:
- Being inferior to Java
You also forgot minecoins
@@King-n00bi3 my bad bruh 😫
@@thedoodlianfella bro gets triggered every time bedrock is mentionned, don't try to reply, you'd be proving my point
@Napoleon_e2 but what if I said I was playing on bedrock? I unfortunately experience all that and more.
This feels like watching the Minecraft equivalent or Liveleak.
3:26 bros reaction is like when the floor in tom and jerry is suddenly gone
Exactly what I was thinking he looks down looks up and says like "oh well" and falls into lava
The worst part is what happens after they fall into lava
Look at their third person model, and how much they don’t react
Dude accepted their fate.
@@palecaptainwolfkayls8499 its literally that clip of Wile E. Coyote staring at the camera with crossed arms as he falls down a cliff into oblivion
There's a whole lot of settings on bedrock server about time, lag deviation and time rewind, but little explanation about what each of them do
You know, It could be fun to watch for a while, a Badrock hardcore where you have a set of "rules" to follow (or THE GAME ITSELF will punish you), like: can't place blocks under you to bridge or tower, you have to remember to be standing if you have to eat, don't use the elytra/trident/anything that makes you go up in the air and you have a BIG RED MACRO PANIC BUTTON on the desk to press to instantly close the game when you feel something is wrong! So much tension for something totally out of your control, feels like an horror rage game.
Minecraft but with a mysterious fae ruleset that you find out through trial and error...
THATS SO RIGHT they are actually secret features that mojang added to make players become better at trial and error so you could play the game with 100% caution knowing that you're gonna die or not its called randomized luck not bugs lol lagva players am i right 😜😜😜🤪🤪🤪😜🤪
for the 9:10 one, I assume the suffocation damage at the beginning was the server assuming he fell, but he fell through a "block", and when he died was when he hit the ground, even though he was still on his bridge. the torch glitching was probably "hey, you're not up here, you can't place that there"
this happened to me like, 3 years ago, its been a constant thing, im surprised people are only talking about it now
Nah people have been denying it for some time now saying it was just bedrock haters faking it and making it up but I play bedrock too damnit. what good does it benefit me to lie against bedrock 😂
@@Mc_Onionspeople deny this stuff happens? That's dumb, it seems clear as day to me that these bugs are legit and suck too
@@Bupboy yh some people actually deny it and make it look like it's either fake or really rare when I reality it's really not. That ghost block issue Happen almost 70%of the time in my case when towering and it drives me nuts
I think it only got brought up now because they are adding hardcore despite all of these random unintentional deaths occurring.
So it was that glitch when i died in bedrock while trying to fix hole creeper made. I legit thought my game was haunted and deleted it after that 🤣🤣
>Your mining
>You break a block and you don’t hear anything
> “Hold shift to sprint.”
As someone who used to play the game when it was still called Pocket Edition, im surprised they broke the system, in the early days of PE you did not take fall damage from nothing.
i played early bedrock, not even early bedrock had that shit 💀
Probably was the rush to achieve parity with Java not taking the time to test everything thoroughly.
During high ping or high CPU usage, Minecraft will begin to bug out on modern PE and I've had the misfortune of experiencing these bugs:
- suffocating in placed blocks,
- suffocating on placed blocks,
- suffocating on placed blocks over lava,
- suffocating above placed blocks over water,
- suffocating in a boat,
- farm mobs suffocate in a fence,
- drowning in a boat,
- drowning on dry land,
- ZARUWARDO!! All mobs freeze for 5s-1m and you can stack damage for when they return, however as soon as time restarts mobs will move at 5x/10x their original speed and possibly deal 20 attacks in under a second,
- swam in lava without damage,
- swam in lava with delayed damage,
- ran in fire without damage,
- ran in fire with delayed damage,
- fallen from great heights, survive, then died 10s later,
- fallen from a short height and be hurt x2,
- (common, persistent bug) villagers fall through the floor and suffocate to death,
- villagers lose their trades,
- villagers walk into lava,
- consuming items take 2s-15s longer to use (food/potions),
- placed blocks deload after 1s-3s,
- destroyed blocks disappear after 1s-15s,
- mobs turn black,
- farm mobs turn black and slowly no-clip through fence,
- farm mobs jump on top of fence,
- farm mobs walk through door,
- floating gravel/sand.
All the bugs I can think of. If we're including server lag, once an underground chunk failed to load on my client and I fell into a cave.
yes, exactly… I was really fond of Pocket Edition, it literally ran on ANYTHING even when infinite world was added and there were no bugs, except for redstone differences, but even then redstone was CONSISTENT at least
by the way you can't play old versions of Minecraft Bedrock on new android today unfortunately… if the game freezes (by you either going through a nether portal or tabbing out of the game and then back in) it just keeps saying that minecraft is not responding even though it does respond
@@kabanod1mI started on some Pocket Edition version of 0.7.0 and I spent years working on PMMP servers for Bedrock. I quit a while ago, and I'm looking at these bugs now. I never remembered it being like this. When I played, the worst bug was the "pink glitch," which would make every texture forget itself and slowly but surely, your whole world, fonts, and UI would lose their textures and turn a burning pink until your game crashed. As goofy as that one was, you could just restart your game. The stuff in this video is basically unavoidable.
Most of the bugs with bedrock, come from it ALWAYS running on multiplayer*, even in a "singleplayer" world. This is because it needs to give you the ability to let friends join your world. This has the side effect of server lag however.
I mean, java has a similar thing, but the server is directly hosted on your pc so it has much less of a chance to lag like this
@@aurastrikeJava and bedrock do the same thing, run a server in the background and join to it, for open to LAN on Java and to let friends join in bedrock
They should make it a toggleable option, most of the people don't even play multiplayer.
@@RandomBloonStuff Can't. Client and server logic have been merged a long time ago such that there is no more "no server singleplayer" logic in the code. I remember when Mojang first did it years ago, it performed horribly with weird glitches like in the video, but it matured and was fixed. Bedrock however seems like it still hasn't been fixed after all this time.
@@JohnSmith-xv1tp
What happens if you launch Bedrock, turn off your WiFi, and _then_ create a new world?
On our bedrock server, we had just beaten the ender dragon, so I went to take the egg back through the portal, and upon returning, the game instantly killed me and deleted my inventory without dropping it.
Lmao.
3:55 Looney Tunes mfs when they realize they're floating off a cliff.
I have a bedrock world that's almost 300mb big...and so ridiculously laggy. I mainly play on java, but to stop the fear of dying randomly, I made a backup wave and turned on keep inventory. It's ridiculous that I have to do this.
Yeah keep inv is basically a fun requirement in bedrock, and not just because of these bugs, but also because, and maybe I'm making this up, but mob spawns are far more aggressive in bedrock
I've been playing quite a bit of legacy lately, and the mobs are very infrequent, and hardly agro even running past them, while bedrock spawns a waterfall of mobs that can see you from 3 chunks away
@@Bupboy YES THE SIGHT FOR MOBS IS RIDICULOUS.
I swear, they can see me and be hitting me before I even notice there's a mob. It's ridiculous. Meanwhile in Java, it's the opposite problem.
I have Minecraft Bedrock on the playstation, and Java on my pc. I played bedrock first and Java second, and the differences are RIDICULOUSLY OBVIOUS, and not just in the ways the games are coded, either.
Mods are so much more accessible in Java, and I don't really feel like giving Mojang hard-earned money for a "mod" that I can only use in one world.
i have a world on my playstation that was almost a gigabit big, and i can hardly play on it last time i checked. trying to go in and out of the nether would make the world crash and doing anything felt like walking through mud. i couldnt ride through ice tunnels in the nether without having to stop every now and then to let the chunks load (which took way longer than it shouldve). im surprised mojang can pass off bedrock as a functioning game anymore seeing how janky and buggy it is in comparison to java
Respect to our Harcore Bedrock Players,
They deserve it
They are expirmenters. They are almost mojang employees
They are a degree of pure masochism that should only exist in a secret lab in the middle of nowhere.
@@timohara7717 The Unsung Playtesters
Respect? at that point youre just plain stupid lmao
If i saw a video
I survived one year on bedrock hardcore i'd watch it 😂
I've suffered from all of these problems before and it's the result of two things:
- server lag,
- hardware lag.
For mobile of course. I once pointed out how old versions of Minecraft Bedrock ran smoother than this and I got poor-shamed for owning the same hardware that ran Minecraft without issue a few versions before but suddenly couldn't no longer.
that's cause adding to spaghetti code just gives you more spaghetti.
Really? Shaming people because they have an old phone?
@@EldenLord-wh4ovSpaghetti
everything before the bee update was just better.. literally every platform
when that update came all bedrock platforms were forced into the s+++ game called bedrock where lots of things have unnecessary delays, loading times are ridiculous (looking at you settings button why tf does it take so long :| smh)
i find that even java is much laggier now, after the past couple updates - my laptop could run the game just fine even with egregious mods, but now running the base game is choppy :/
I'll be honest... I'm playing a Bedrock HC game right now, I'm like 118 game days in, and I haven't had a problem. Closest to death I've been so far was a totally fair-and-stupid decision on my part to check out the inside of the Woodland Mansion while wearing base leather armor...
For the elytra clips, what I THINK happened is that the server doesn't realise the player is flying, so it thinks that the player is in the air and SHOULD fall, so at the time that they WOULDVE hit the floor, they take damage, but they keep flying, and the server just thinks that theyre still in the air without an elytra and they take damage again, this cycle happens until the player dies
for the people who don't understand, basically:
the player sees themselves as flying in the air
the server sees the player as in the air, thinking theyre falling, then teleporting back in the air and falling again
Bedrock edition sucks, why does the game calculate like that
@@ThatHolyGamer Be quiet kid, almost nobody is experiencing this.
@@maxdrags3115isnt this a whole video of people experiencing this with more comments under this video with more people saying this happened to them among other bugs? I'm a bedrock player and I have that same question as them.
@@ThatHolyGamerIt's a desynchronization between the client and the server. The client also calculates it's position independently to avoid lag, because server ping can be >100ms and that kind of latency to move your mouse is unplayable of course. I think in singleplayer bedrock still uses a server but runs it on the device, just like java edition. What java edition does is it just teleports you back. But it's so wierd that this desync even happens in singleplayer, it really shouldn't because there are no way a packet could be dropped or something
@@maxdrags3115 Regardless of it being experienced by many or only a few, that doesn't change the fact that Bedrock edition is turbo garbage.
7:38. My assumption is, because you can listen closely for the sound of him hitting the ground, that the game saw him as on the ground even when he was flying. Now the dmg came from the mountain, he was just falling down and down. The game saw him as walking forward (or sprinting) but then just walked straight down the mountain taking (clearly) fall dmg.
Wouldn't explain the third damage taken tho, since he'd be at the floor already, and no more cliffs. Most likely the client tells the server he is high up and the server accepts, except the server thinks he isn't flying - falling down and taking damage, then repeat the process. That is why 12:10 took many small damages (low height from ground) and stopped as he landed.
It's because the client isnt recieving the rubber band packets from the server becuase of lag and also the server and client have become desynced at this point. the player elytras sends a packet to the servers saying its at xyz the server says you're falling because you haven't activated the elytra and gives the player fall damage the player sends another packet saying its at xyz and so on untill the player lands and the server doesnt give any fall damage because the player is standing on a solid block which is synced between client and server. tldr client and server become desynced and stuff breaks
@@spicylemon2623 main point to learn here… dive to the ground immediately to land and reset your XYZ.
@@spicylemon2623Basically the server doesn’t see you gliding so it makes you fall from where you are, tries to correct your position but still doesn’t think you’re gliding so to the server you just keep falling over and over until you die or land
Chances are the same thing happens with blocks: You place a block over the ledge, server doesn’t see the block, you fall on the server but the client updates your position back to the block the server can’t see you you keep falling over and over unless you move out of the way of the block.
Almost all bedrock deaths can probably be explained by a desync between client and server that Java edition either doesn’t have or is better at correcting.
0:15 NO! IT'S AN ANIMAL JOKER YOU CAN'T!
There's no laws against the Minecraft fox, Batman!
@@BetterCallBigShotAutosits my fox batman
@@BetterCallBigShotAutosbeastiality is a crime joker you’re under arrest.
This would make me rather starve 🤢
@@BetterCallBigShotAutosNOO SPAMTON DONT DO IT NOOO
I remember when I was younger I would play my bedrock survival world, and sometimes I would join the world to find I had died in my own house for no reason, ahh, bedrock you always used to amaze me with your twisted ways.
I started playing Minecraft through Bedrock edition years ago. It always felt like I was connected to a server and would just occasionally lag and pop back in a LOCAL game. You can't even pause the game with escape. They must not implement any sort of network loopback, and you just drop packets. That's my only thought.
also Java Edition uses TCP for all of its networking, and Bedrock uses UDP. Using UDP instead of TCP is generally good for performance but it's only as good as the developer makes it to be, because with UDP you have to write your own packet loss handling. with TCP there is no packet loss.
in bedrock single player worlds are a local server than the game directly managing the world and player, in java the game directly does that unless you do open to LAN
You are technically playing on a local server in both Java and bedrock (and lots of other games too) in single player, most games just aren't completely messed up like bedrock
@@sarandip no, in Java ever since 1.3 you've always been on a local server, even if you never opened the world to LAN. I'd provide proof here but links get my comments deleted and I can't insert pictures here
java also has an internal server
its just that java servers respect the client more than bedrock servers do for some reason
8:55 I think the "drowning" visual is caused by the hitbox of the person falling through the blocks (or at least what the server thinks is happening) causing them to suffocate as they fall through the blocks and then die from fall damage
i love how at some point they changed suffocation damage to be negatable by water breathing
bedrock devs are DEFINITELY competent and dont change old features that have no fucking reason to be changed whatsoever :3
12:25 I think what's happening here, is that Minecraft doesn't see them as flying and puts a ghost player on his location every few seconds, and that ghost player keeps falling and taking fall damage. That's just what I think it is.
yes, i have experienced it and i agree
This is at least how it feels. I've been lucky with Bedrock so far and only died once from this lag or whatever it is. But that is one times too many. ESPECIALLY on Hardcore. Gj Mohjang.
This is some urban legend stories stuff, lol.
"When you're playing Minecraft bedrock edition at midnight. Rumors said that if you are placing blocks and there is no sounds, you will die mysteriously"
"Rumors state that one man spawned on an unrendered chunk, he pleeded for help but he was never found"
Me and my brother had a survival world we'd play from time to time, and it was the highlight of my week when he had time to play. We built a house I was really proud of, a giant over engineered Villiger trading compound thing we were actively working on, and I had really fast horse named Hermes I was quite fond of. Then we got kicked while I was riding him, and when I joined back, he was gone. I got another horse I named after an equivalent god from another pantheon, but it just vanished from our stable a while later, I wasn't even riding it. Then we started getting these weird chuck corruption structures all around the our house that really ruined the landscape. We tried to remove them, but it just turned into a game of whack a mole. Then one day I got kicked, and couldn't rejoin. When I finally managed to join back on, my spawn point and inventory had been completely wiped. I had made sure to turn on keep inventory precisely because I knew I wouldn't be able to keep going if I ever lost everything, but it didn't matter. I couldn't handle being burned yet another time, so I just accepted that our world was dead, even if it meant we wouldn't spend as much time together. The game works just well enough to get you invested, only to rip it away from you.
Try out terraria, that game actually functions
@@deadboyo2773or try out Java
Except it's a completely different game
A better suggestion would be Minecraft java, which is the actually functioning, non shit version of minecraft
@@professormutant3252 completely agree, however
Play terraria anyway, it good, cheap and cool modding world fine and is easy, not that it's required, easily got over a couple hundred hours before considering mods, plus you can always just play both, the games literally recommend each other in splash text
@@professormutant3252Yeah, the problem with Java is just that it's only available on PC, so not everyone can play it.
Sad thing is is that many bedrock players have just either accepted this or refuse to acknowledge this, but both sides will say that it's the player's fault for not having a good enough device to play bedrock properly.
I’m in neither party though. I have literally never experienced anything like this and I’ve been playing bedrock for 10 whole years now, on a mixture of devices from phone to high quality gaming pc. I don’t know what to think but I am either really lucky or people are faking these videos because of the meme. I know it sounds insane but nobody I’ve talked to irl has ever seen anything like this (who have all played bedrock as long as I have) and it’s only online this type of thing seems to exist
@@SpremeCalami I play on PS5, which is actually the PS4 Edition.
On singleplayer it's generally fine. If my world is set to Multiplayer I can experience minor lagspikes or ghost blocks when the internet slows down, but nothing major.
When I'm on a friend's world however, their internet isn't the best as they live in the sticks - so a lot of desyncing and heavy lagspike issues can happen, I've experienced many of these issues regularly, including crops not getting re-planted properly requiring I go over the same patch two or three times. Thankfully only one desync has resulted in an unfair death; 1v1'ing a mob that just did lots of delayed damage to me after a lagspike. I also got dipped into lava in the Nether after ghost blocks disappeared under me, but by that point I had fully enchanted gear so lava was not fatal just annoying and panic inducing.
Desyncs happen, but how the game handles them and just retcons things that happen client-side with information that server-side sees is what causes issues. For example, when placing ghost blocks you don't get rubberbanded back to where you were at the last block that was successfully placed, the game just lets you carry on. When it realises those blocks don't exist, it corrects those by "deleting" them, but doesn't update your positioning leading you to fall to your inevitable death - which completely defeats the purpose of sneak-placement, it's meant to stop you from falling off blocks. Ghost blocks produced by pillaring directly up also nudges you off when corrected, so that's also risky.
@@SpremeCalamiI've been playing Minecraft since almost the start and I started on legacy edition, it was great and no lag or issues. When legacy was killed and converted to bedrock there were so many optimization issues that there was so much stuttering and lag on single player. I remember seeing multiple chunks refuse to load in, block disappearing after being placed. it nearly killed me in the end just by towering up. bedrock is unoptimized and is an insult to legacy edition.
I haven't had much experience with java only legacy edition since that was all I had before the switch to bedrock. I play bedrock a lot but it pales in comparison to legacy or java despite the little experience I have with it
@@zomadziasans8212 I wish Legacy Console was still supported.
And dear god the crashes I got after trading with villagers and closing chests. They were so frequent I ragequit the game for 2 months. I'm glad they fixed those. At multiple points I had to download a backup copy of my world potentially losing hours of work because my Shulker Boxes were lost to the ether.
For context, due to the way Minecraft saves the inventory first, and then the world - it would remember I took the Shulker Box out of my Ender Chest but not that I placed it in the world. As that particular Shulker Box had all my max-enchanted tools in it, it was a rather hefty loss to a sudden software closure, which is something completely out of my control. So I ended up just placing them in a specific spot in my house, never moving them, paranoid of losing them again. Having a Shulker Box sat forever in a single spot for fear of a game crash completely defeats the purpose of Shulker Boxes.
I wish Legacy Console Edition was still supported.
My word the crashes I would receive after trading with villagers and coming out of a chest inventory. They got so frequent I lost my Shulker Box containing all my max-enchanted tools twice, and both times I had to restore my world to older backups, losing hours of progress. I ragequit for a couple of months because of them. Thankfully that was eventually fixed but I kept sending in error reports every time it happened.
For context of why that happened: Minecraft saves the inventory first and then the world. I still don't know why I had game crashes closing inventory menus but I ran the risk of losing my Shulker Box whenever I'd take it out of the Ender Chest (one such inventory menu) and placed it down in the world - it would "remember" that I took it out of the chest, but not that I placed it down as a block, so it went bye-bye. I got so paranoid of it happening again I ended up just keeping them all in a permanent space in my house, which completely defeats the purpose of a Shulker Box.
4:30 bro was like "man it cant get worse than this" *and it got worse*
7:37 I have already experienced this, basically the server thinks you are still in the same spot but on the ground and when there is a bump or a hole you still take fall damage.
8:47 as a bedrock player, I can inform you that the sound plays because they are trying to continue to move while the death menu shows, this causes the noise to play only with a controller
one of my friends got the kinetic energy death message from walking
we havent even got to the end yet
Dude must be running too fast 😂
8:00 I'm pretty sure the server doesn't know he has an elytra, so while he's flying downhill, the server thinks he's just walking and so taking fall damage when he falls multiple blocks
In my bedrock world, the drowned’s just… refuse to attack me a lot of the time. Like, I’ll be in the water and they’ll be right next to me, but instead of attacking me, they just look at me like “sup bro”. I didn’t know they’d be chill like that.
As a dedicated bedrock player, I think I know part of what’s happening
Worlds in bedrock edition are set to allow multiplayer by default, so every world is treated like a server (it’s why you can’t pause and stuff).
This means that if you’re playing bedrock edition and your wifi gets slightly delayed or disconnects, your world starts lagging a lot.
Bedrock edition is also terrible at dealing with lag, it tries to update mob + player positions and then update blocks and then update chunks, so any changes made to the world are calculated after the players damage, resulting in a lot of random fall damage.
It also makes a lot of chunks not load, and unloaded chunks in bedrock are solid, which can cause suffocation damage until it finally loads the chunks.
Ye that definitely makes alot of sense to me and i just realized it now
First time i have seen someone explain it properly for the most part! Kudos to you!
The thing is, Java also runs on an internal server. If they can make Java work, why not Bedrock?
solution: turn off multiplayer in worlds by default and place a lag warning for players trying to enable it
@@06dpabecaude bedrock is lan
4:31 this happens becauseof the way you place blocks in bedrock, the game said "hey i think you're making a bridge" and didnt decide to place below
As a Java player, I've always felt half jealous that Bedrock has that easy bridging... But half suspicious that stuff like this could happen. Sure enough, looks like it's A Thing that could really get in the way when building. 😅
(Though the fact that the lower blocks disappeared was most likely what led to it in this case; he was trying to build along those two blocks which the game likely WOULD have respected, except it decided that those blocks weren't really there. Hence it switching to bridging behavior instead. That's my understanding of it, at least.)
I would love to watch compilations of these with classical music in the background.
There's so many cases that you can't ignore them anymore
I am REALLY lucky that I have never encountered the really bad bedrock moments. The only one I usually get is the “staying alive at zero hearts” one
Bedrock servers is just being glitchy for no reason,when i logged on a server with a high ping,i kept spawning in the ground, Mojang should fix these as soon as possible.
that's expected for high ping. the server isn't fully loaded yet, so the client will keep trying to drop you down. but on the next moment the server sending you new data, the client would put you back on the surface. also expected on java.
Lol it keeps happening to you cuz like you said you have high ping🤣 high ping is cause by low internet
@@KuneSakeSRWSCS The Philippines
"This server has known issues but I'm going to blame it on Mojang instead"
dont think mojang is making bedrock
8:33 that noise is actually played *any time* you cannot move the green select box thing, and because you tend to hold directions to go places, if you are holding a direction when you die there’s only 1 option so you can move the green select box so it plays it *non-stop* until you stop holding a direction
On that cobblestone bridge one, it looks like a weird desync glitch. I think he’s calculated at 1 pixel too low, which leads to the server (maybe) calculating him falling through the block (giving 1 damage as his head goes through), and eventually hitting the ground.
As a programmer, this is embarrassing. It’s using calculations to interpolate position, but the calculations are tied to fps, so when frames drop, the distance becomes greater. A similar glitch exists in Doom (and Doom 2) where if you have enough speed, the calculations put you on one side of the wall on the first frame, and the other the next.
And since multiplayer servers run on TPS rather than FPS, thanks to the idiosyncracy of Bedrock worlds being multiplayer servers even in singleplayer mode unless you specifically disable that (or even potentially in spite of disabling that manually), server lag and other forms of desync causes the equivalent of frame dropping.
@@kennyholmes5196how do I disable that....
This is literally ALL desync between server and client. The elytra clips are purely instances where the server believes the elytra was never activated, and therefore always have a small initial bit of fall damage as it thinks you fell from the jump. The issue really becomes apparent as the desync has no method to fix itself, the server keeps playing you in the air where your client says you are but the server STILL thinks you never activated elytra. So you fall again, and again.
@@randomguyonyoutube5875 No idea. I don't play Bedrock.
@@kennyholmes5196 that's not an idiosyncracy of Bedrock. Java edition also runs a server locally since 1.3. From Minecraft wiki on 1.3.1 update, under General: "Made singleplayer internally use a multiplayer server."
I've yet to experience any of these things.
But I did get killed a few times by being attacked whilst in a chest or my inventory, and I would open up my Emote menu by chance of pressing left on my d-pad; I wouldn't be able to break free of the menu in time to kill the thing attacking me and died constantly emoting.
Safe to say, I reconfigured my emote wheel to [unset] and completely ignore the feature now.