Some of these have been fixed. For example, observers will detect wall shape changes.
Sometimes it’s possible to encase the the flying machine in bedrock to prevent destructive side effects like pistons misfiring. However, this is not a nice workaround, and does not work when the observer pulse has side-effects like flipping a latch.
Might relate to or duplicate MCPE-99760 and MCPE-47573, which were resolved as “cannot reproduce” for some reason.
Mojang should really take a closer look at this one now, considering that this behaviour pack provides a consistent way to reproduce the bug, and this report points out the exact cause of the bug.
I was not able to reproduce the bug after recording this. The bug may have been caused by me opening the world to LAN/multiplayer, which might have changed how the client-server connection is handled.
This bug has been around for a while. I noticed it while making a railgun to oneshot the ender dragon sometime in 1.16. Arrows from the dispenser would do almost no damage to the ender dragon, even when arrows from an unenchanted bow would oneshot the dragon.
For whatever reason TNT doesn’t have this issue.
Also happens at X=255 pushing from the +x side to the -x side
Ender pearls in Bedrock Edition have no drag, as specified by the
"inertia": 1,
"liquid_inertia": 1in the entity file.
I’ve reported a similar bug detailing a different setup with moving blocks. MCPE-224099
This is useful for counting stacked wind charges precisely.
I've only noticed this when the wind charges are going down and collide with a block. I suspect the issue is caused by a wind charge exploding and cancelling thr momentum of all other wind charges, causing them to fail thr collision check.
Skeletons do not start drowning instantly, and burning mobs automatically pathfind into water.
Isn't this because breezes will not attack when within 2 blocks of an enemy, an intended feature? Sitting in the same boat as a breeze surely puts you closer than 2 blocks.
Have you enabled the option to improve input response time? I've had it enabled once and it made the game unplayable in a few minutes. Disabling the option fixed it for me.
I have heard that they changed the way slime blocks work recently.
You likely were killed while stuck in the loading screen when moving to the overworld and retained only your maximum 7 levels of XP. There is also a bug where some entities spawn over world spawn at y=32767, which may have happened to your items but not your XP.
… and locking/unlocking a repeater