mojira.dev
MCPE-165945

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

Attachments

Comments 6

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:

Steps to Reproduce:
1.
2.
3.

Observed Results:
(Briefly describe what happens)

Expected Results:
(Briefly describe what should happen)

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:

  1. Put a Blaze in a 1x2x1 box

  2. Activate 1 sticky piston to push a block into the top of the box horizontally

  3. Deactivate Piston

  4. Blaze should be pulled outside of box or into an adjacent block of the box

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

[media]

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

BMAGS6

(Unassigned)

1194110

Confirmed

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

Retrieved