Entities in blocks get pulled through the back of retracting sticky pistons
Whenever a piston activates and the head pushes through a Blaze, the Blaze is not pushed and, when the piston retracts, the Blaze is pulled into the piston block and the blocks behind it.
The Blaze does not have to be enclosed; the piston arm just has to activate into the same occupied block as the Blaze
Blaze farms utilizing pistons are now prone to breaking
Linked Issues
is duplicated by1
relates to9
MCPE-164851Minecarts phase through blocks when pushed upwards with pistonConfirmedMCPE-166230Mobs go through walls if pushed by block on pistonConfirmedMCPE-169011Downward-Retracting Pistons Can Pull Entities Downward Through BlocksConfirmedMCPE-171680Entities on top of or inside a moving block often move farther than the block and may fall through blocks as a resultConfirmedMCPE-173672If a player gets wedged between two not-full blocks pushed by pistons, the player will be pulled behind one of the pistons when they retractConfirmedMCPE-178248Entity(ies) inside an extended piston base gets moved to front of the piston when the piston is retractingConfirmedMCPE-60483Entities on top of any block pushed or pulled by a piston move along with the blockConfirmedMCPE-183495Jumping on moving blocks is buggyCommunity ConsensusMCPE-156031Honey blocks moved by pistons do not drag players and entities as expectedConfirmedAttachments2
- Unresolved
BMAGS6- 6
- 4
- Confirmed
- 1194110
- Multiple
- 10.0.22621.2864 (xb_flt_2211ni.221130-1745)
- Blaze Piston
- 1.19.51 1.20.60 1.20.81 Hotfix 1.21.2 Hotfix
Created Issue:
Blazes get stuck and sucked into pistons
Whenever a piston activates and the head pushes through a Blaze, the Blaze is not pushed and, when the piston retracts, the Blaze is pulled into the piston block and the blocks behind it.
The Blaze does not have to be enclosed; the piston arm just has to activate into the same occupied block as the Blaze
Blaze farms utilizing pistons are now prone to breaking
Attachments1
- Unresolved
- Open
- Unconfirmed
- Xbox
- 10.0.22621.2864 (xb_flt_2211ni.221130-1745)
- 1.19.51
![[MCQA] Bartłomiej Słodkowski](../../../data/avatars/users/18941.svg){kind=small}
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
![[MCQA] Justyna Oleś](../../../data/avatars/users/18934.svg){kind=small}
![[Mod] GoldenHelmet](../../../data/avatars/users/18951.svg){kind=small}
is duplicated by
relates to
Blazes get stuck and sucked intopistonsEntities in blocks get pulled by retracting sticky pistons
Entities in blocks get pulledbyretracting sticky pistonsEntities in blocks get pulled through the back of retracting sticky pistons
![[MCQA] v-magwar](../../../data/avatars/users/18935.svg){kind=small}
![[Mod] Jarl-Penguin](../../../data/avatars/users/92849.png){kind=small}
relates to
relates to
Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response.
Could you please provide a video showcasing the issue?
Just a reminder, to make your bug report as effective as possible, please try and include the following steps to reproduce the problem:
If your ticket does not look like the example given here, then it's likely to be closed as incomplete.
This ticket will automatically reopen when you reply.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📓 Project Summary – 📧 Suggestions – 📖 Minecraft Wiki
Steps to reproduce:
Observed results:
Most of the time, the blazes are pulled into a block of the box or are pulled outside of it entirely.
Expected results:
Blazes should not be pulled by the piston and should stay inside of the box
IMG_1736.mp4
Is this still an issue in the latest version?
Yes this still occurs.
Part of what causes this is that when an entity touches any piston head or moving block, the entity gets moved in each tick in which the piston head or moving block updates. Since moving blocks and updating piston heads take 2 ticks to update (see MCPE-103544), the entity gets moved twice instead of once (see MCPE-171680). In the case of the blaze inside the retracting block described here, the first tick of piston retracting positions the entity up against the piston head, partially inside the coordinate space of the piston head. The second tick of piston retraction moves the entity farther inside the piston, where it is then closer to the back than the front. The entity then gets pushed out the back of the piston by standard entity-block physics.
If entities would only be moved during the first tick of moving block/piston head updates instead of during both, it would probably fix this both this issue and MCPE-171680.
Still an issue in the latest version
Confirmed in 1.21.44