mojira.dev
MC-11107

Sticky Pistons will not drop blocks in some setups.

A sticky piston powered as in the picture below will create less than one tick pulses but the piston still holds on to the block. Powering the repeater to the left causes this. What I would expect to happen is the block to be left in the extended position as it does in nearly every other setup with 1 tick or shorter pulses.

Linked issues

Attachments

Comments 23

Confirmed.

João Mambelli

Also wanted to know why when you place a sticky piston, a boco in front and a torch on top of the block, the piston pushes and pulls back the block. This was to be a pulse of 1 tick.

João Mambelli

Tails, can you explain?

Only Mojang knows.

João Mambelli

To whom and how do I ask?

13 more comments
DicoTheRedstoner

To quickly clarify why this bug occurs:
When the piston pushes the block, it does not update directly after. The first update comes from finishing the extension, after 1.5 ticks. Thus, the piston starts its retraction 1.5 ticks after extending, making it not leave the block behind, because for that it needs to extend for less than 1.5 ticks (most often referred to as receiving a 1-tick pulse).

To confirm this, you can have a repeater coming from the redstone dust that powers the piston, which updates the piston (without powering it).

This is not necessarily a bug, we might eventually see what Mojang thinks of it. If it were fixed, many buds would definitely break, such as the sticky piston with a slimeblock and a redstone block bud, or the one with glass and sand on top. Thus I would prefer to see this report's solution also become 'works as intended'. Generally, redstone changes are bad, because they often break many contraptions that rely on current redstone mechanics. This one certainly would break quite a few if it were Fixed.

Is this still an issue in the most recent versions (currently that is 1.10.2, or 16w42a) of Minecraft? If so, please update the affected versions and help us keeping this ticket updated from time to time. If you are the owner/reporter of this ticket, you can modify the affected version(s) yourself.

Cannot reproduce in 18w47b

DicoTheRedstoner

@Connor Steppie

I can reproduce this in 18w47b.

Please check if that's still an issue for you in the latest 1.15.2 stable release or the latest 1.16 development snapshot.

Andrew

(Unassigned)

Confirmed

(Unassigned)

Minecraft 1.4.7, Snapshot 13w10a, Minecraft 1.5.1, Minecraft 1.5.2, Snapshot 13w18c, ..., Minecraft 16w44a, Minecraft 1.12 Pre-Release 6, Minecraft 1.13.2, Minecraft 18w47a, Minecraft 18w47b

Retrieved