Drakou111
- Drakou111
- JIRAUSER769234
- Europe/Stockholm
- Yes
- No
MC-267605
NormalI said in the issue that it happens in every versions/snapshots after 1.18.2 (which includes 1.20.4)
This is a duplicate bug report since the last one was incorrectly put into "Resolved (
MC-267605) even though I specified that it also happened in current versions. Here is the bug:When placing a piston facing up with a block on top then powering that block from above with a button ON TOP (putting the button on the side of the block won't create the bug), the piston will push the block up, but the block will be invisible during its movement. This is not a visual bug. If the pushed block is a slime and you stand on it, you will not be launched up since the slime is technically not there. Also, this bug does not occur with levers (as shown in the video), and works slightly differently with pressure plates. This bug is present in ALL versions/snapshots after 1.18.2, which includes current versions.
This is a duplicate bug report since the last one was incorrectly put into "Resolved" (https://bugs.mojang.com/browse/MC-267605) even though I specified that it also happened in current versions. Here is the bug:
When placing a piston facing up with a block on top then powering that block from above with a button ON TOP (putting the button on the side of the block won't create the bug), the piston will push the block up, but the block will be invisible during its movement. This is not a visual bug. If the pushed block is a slime and you stand on it, you will not be launched up since the slime is technically not there. Also, this bug does not occur with levers (as shown in the video), and works slightly differently with pressure plates. This bug is present in ALL versions/snapshots after 1.18.2, which includes current versions.
Drakou111 now that this issue is resolved, I'd suggest to open a new report for the other instances of the bug remaining, and in that report you could detail the root cause and point Mojang towards the direction to fix all of them at once and remove unnecessary code.
Like I said in the issue and in the affected versions, the bug still happens in every versions/snapshots after 1.18.2 (which includes 1.20.4 and 23w51b). I've added a video of it in 1.20.4.
This is because whenever your velocity on an axis reachs <.003*slipperiness*0.91 (<.005*slipperiness*0.91 before 1.9), it will be set to 0 for the next calculations since it is "negligible". This code was put in to let the player shift at the edge of a block without having to wait for their velocity to perfectly hit 0 (for instance, in minecraft 1.0.0, this wasn't implemented, and you had to wait ~20 seconds before unshifting, otherwise you would fall off the edge).
In the case of shifting on normal ground in versions above 1.9, if you're at a speed <.00549 on an axis, then you will never accelerate properly on that axis, which causes the issue. In your example, you move at a speed of .00307, which triggers the bug. Fixing this bug would require removing that piece of code, which would require recoding shifting at edges (which they probably should, it is very buggy with ice).
Sorry, I just wanted to be somewhat rigorous with my explanation. Making it not per-axis does solve this issue. However, even after the fix, it still affects other parts of the game, such as shifting at the edge of ice, and other more specific/less important bugs. This is mostly why I saw removing that part of the code as a better choice, since it would remove all of those other issues aswell. Sorry for bringing up older versions.