mojira.dev
MCPE-164807

Falling through piston elevators that use slabs/stairs as the platform

The 1.19.50 update broke two of my 3x3 piston elevators. The elevator platform has a single half slab in the center, with 8 stair blocks around it that form a depression for players/animals to stand in/on. Going up functions as intended, but when using either of my elevators to travel downwards, I immediately fall through the slab/stairs. In other words, instead of riding the elevator downwards as should be expected, I get an express trip to the bottom of the inner workings of my elevators. This never occurred before this update; Not even once.

Curiously, when I swapped the 3x3 slab/stairs platform for a solid block platform (Quartz block), the elevator functions as it did prior to 1.19.50. Something was definitely changed that broke the previous behavior of falling onto slabs/stairs that are being pulled downwards.

 

Video: https://www.youtube.com/watch?v=y3Fj-ugmceE

Linked issues

Comments 11

Here is video evidence of the issue occurring multiple times, on two different elevators:

https://www.youtube.com/watch?v=y3Fj-ugmceE

It is possible the bug relates to MCPE-166230. Can you upload the world affected?

  • 1) It's certainly possible that the same changes made in the 1.19.50 update are responsible for both MCPE-164807 (this issue) and MCPE-166230, but I can't confirm or disprove that. If MCPE-166230 started happening with 1.19.50, then perhaps the odds of them being related is higher, but again, I'm not sure either way.

  • Something that should be mentioned is that for MCPE-164807, the 3x3 platform of stairs (with a single slab in the center) has either a slime or honey block underneath each block comprising the platform, since pistons on bedrock/realms are limited in the number of blocks that can be pushed/pulled. When the 3x3 platform is pulled downwards by honey/slime blocks that are attached to sticky pistons, players phase through the 3x3 platform as well as the honey/slime blocks underneath them.

  • This issue occurs on two separate piston elevator designs starting in 1.19.50. The only commonality between the two elevator designs is that they share identical 3x3 stairs/slab platforms with honey/slime blocks underneath. The honey/slime blocks are patterned in such a way that allow for two sticky pistons to pull either the honey blocks or the slime blocks downwards. Together these two pistons act in unison to pull the 3x3 slime/honey blocks downwards, which then pulls the 3x3 platform that players stand on. Hopefully that description, in conjunction with the provided video link, clarifies the issue. If need be I can upload additional references to the issue.

 

  • 2) The world in question is a realm. I'm not the owner, just a member. I've contacted the realm owner to get a copy of the world. Unless I run into any technical hurdles, expect it to be linked here soon.

 

Lastly, the issue seems to also be present in 1.19.51.

I understand this is still an issue as of 1.19.51/1.19.60?

Issue MCPE-164807 is present in both 1.19.50 and 1.19.51. I have not tried to replicate the issue on any version past 1.19.51 due to a separate issue (detailed below). I can test 1.19.60 soon and report back.

 

I'm hesitant to even launch Bedrock Minecraft to check if the issue is still persisting in versions past 1.19.51 due to another issue that seemingly coincided with the release of 1.19.50, where Bedrock will hang at the initial black screen, never showing the Mojang logo. Afterwards the program is frozen, Windows 11 freezes, and nothing responds except that the mouse cursor can still move around. No amount of Ctrl Alt Del, or Alt F4, fixes it. The only remedy to that issue is to hard shutdown the computer.

 

I'm still trying to get a copy of the realm to upload. The owner has made repeated promises to send the file, but hasn't followed through on that, so all I can do on that front is keep reminding him and be patient.

1 more comments

This issue persists in v1.20.10

Still an issue in v1.20.15

I tested the new update (1.20.30), and this is still an issue.

This is still an issue in 1.20.32

@unknown: As the reporter, you can add the affected version to the issue yourself. That's why I ask you not to always comment on it as well, as it unnecessarily bloats the issue.

K.E.

(Unassigned)

1000464

Confirmed

Multiple

Windows 11 (22621.819)

1.19.50, 1.19.51, 1.20.10, 1.20.32 Hotfix

Retrieved