Piston no longer retracts an extended piston when de-powered at the same time
The bug
Double piston extenders no longer retract both pistons at the same time, when they are depowered in the same game tick.
This behaviour (retracting both pistons at the same time) was classified as "Works As Intended" in MC-9342.
How to recreate
This behaviour was always dependant on the update order. The piston in the back had to receive the update first. To influence the update order one way was to power the front piston with a comparator and the back piston with a repeater. This behaviour was also reliable with doublepiston extenders facing upwards, being de-powered by a torch or a minecart powering a downwards facing double piston.
Also the double retraction had to happen within the same block event.
Linked Issues
is duplicated by5
MC-89020intentional behavior of pistons got changed in latest snapshotDuplicateMC-98538pistons don't work like they did in 1.8.9DuplicateMC-104530sticky piston does not pull other sticky piston to it DuplicateMC-117587Sticky Pistons do not pull more than one piston.DuplicateMC-155706Sticky pistons won't stick to extended pistons?!?!?!Duplicate
- Unresolved
ilmango- 223
- 73
- Confirmed
Low- Platform
- Redstone
- piston pulling retracting
15w38b - 1.19.3
15w38b 15w45a 15w46a 15w47b 15w50a 16w03a 16w04a 16w05a 16w05b 16w06a 16w07a 1.9-pre1 1.9-pre2 1.9-pre3 1.9-pre4 1.9 1.9.1 1.9.2 16w14a 16w15a 16w15b 1.9.3-pre1 1.9.3-pre2 1.9.3-pre3 1.9.4 16w20a 1.10 1.10.2 16w40a 16w42a 16w44a 1.11 1.11.2 17w06a 17w13a 17w14a 17w15a 17w16a 17w16b 17w17a 17w17b 1.12-pre5 1.12-pre6 1.12-pre7 1.12 1.12.1-pre1 1.12.1 1.12.2 17w43b 17w45b 17w46a 17w47a 17w47b 17w48a 17w49a 18w03b 18w05a 18w20c 18w21b 1.13-pre1 1.13-pre3 1.13-pre4 1.13-pre9 1.13 18w30b 18w33a 1.13.1-pre1 1.13.1-pre2 1.13.1 1.13.2 18w43a 18w44a 18w45a 18w46a 18w47a 18w48a 18w48b 18w49a 18w50a 1.14-pre2 1.14-pre3 1.14-pre4 1.14.1 1.14.2 1.14.3 1.14.4-pre2 1.14.4-pre3 1.14.4-pre5 1.14.4-pre6 19w35a 19w36a 19w38b 1.15.1 1.15.2 20w06a 20w12a 20w13b 20w20b 1.16-rc1 1.16 1.16.2 1.16.3 20w46a 20w51a 1.17.1 1.18.1 1.19.3
Created Issue:
pistons no longer retracts an extended piston when de-powered at the same time
Double piston extenders no longer retract both pistons at the same time, when they are depowered in the same game tick.
This behaviour was classified as "Works As Intended" inMC-9342. People were used to this behaviour and many redstone contraptions rely on the sharper timings such a behaviour enables. Removing this feature would in some cases require major adjustments to those.How to recreate:
This behaviour was always dependant on the update order. The piston in the back had to receive the update first. To influence the update order one way was to power the front piston with a comparator and the back piston with a repeater.
Attachments1
pistonsno longer retracts an extended piston when de-powered at the same time
Double piston extenders no longer retract both pistons at the same time, when they are depowered in the same game tick.
This behaviour was classified as "Works As Intended" inMC-9342. People were used to this behaviour and many redstone contraptions rely on the sharper timings such a behaviour enables. Removing this feature would in some cases require major adjustments to those.How to recreate:
This behaviour was always dependant on the update order. The piston in the back had to receive the update first. To influence the update order one way was to power the front piston with a comparator and the back piston with a repeater. This behaviour was also reliable with doublepiston extenders facing upwards, being powered by a torch or a hopper minecart powering a downwards facing double piston.
Double piston extenders no longer retract both pistons at the same time, when they are depowered in the same game tick.
This behaviour was classified as "Works As Intended" inMC-9342. People were used to this behaviour and many redstone contraptions rely on the sharper timings such a behaviour enables. Removing this feature would in some cases require major adjustments to those.How to recreate:
This behaviour was always dependant on the update order. The piston in the back had to receive the update first. To influence the update order one way was to power the front piston with a comparator and the back piston with a repeater. This behaviour was also reliable with doublepiston extenders facing upwards, being powered by a torch or ahopperminecart powering a downwards facing double piston.Double piston extenders no longer retract both pistons at the same time, when they are depowered in the same game tick.
This behaviour was classified as "Works As Intended" inMC-9342. People were used to this behaviour and many redstone contraptions rely on the sharper timings such a behaviour enables. Removing this feature would in some cases require major adjustments to those.How to recreate:
This behaviour was always dependant on the update order. The piston in the back had to receive the update first. To influence the update order one way was to power the front piston with a comparator and the back piston with a repeater. This behaviour was also reliable with doublepiston extenders facing upwards, being de-powered by a torch or a minecart powering a downwards facing double piston.
duplicates
relates to
is duplicated by
duplicates
Double piston extenders no longer retract both pistons at the same time, when they are depowered in the same game tick.
This behaviour (retracting both pistons at the same time) was classified as "Works As Intended" inMC-9342. People were used to this behaviour and many redstone contraptions rely on the sharper timings such a behaviour enables. Removing this feature would in some cases require major adjustments to those.How to recreate:
This behaviour was always dependant on the update order. The piston in the back had to receive the update first. To influence the update order one way was to power the front piston with a comparator and the back piston with a repeater. This behaviour was also reliable with doublepiston extenders facing upwards, being de-powered by a torch or a minecart powering a downwards facing double piston.
Double piston extenders no longer retract both pistons at the same time, when they are depowered in the same game tick.
This behaviour (retracting both pistons at the same time) was classified as "Works As Intended" inMC-9342. People were used to this behaviour and many redstone contraptions rely on the sharper timings such a behaviour enables. Removing this feature would in some cases require major adjustments to those.How to recreate:
This behaviour was always dependant on the update order. The piston in the back had to receive the update first. To influence the update order one way was to power the front piston with a comparator and the back piston with a repeater. This behaviour was also reliable with doublepiston extenders facing upwards, being de-powered by a torch or a minecart powering a downwards facing double piston.Also the double retraction had to happen within the same block event.
is duplicated by
is duplicated by
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
is duplicated by
Double piston extenders no longer retract both pistons at the same time, when they are depowered in the same game tick.
This behaviour (retracting both pistons at the same time) was classified as "Works As Intended" inMC-9342. People were used to this behaviour and many redstone contraptions rely on the sharper timings such a behaviour enables. Removing this feature would in some cases require major adjustments to those.How to recreate:
This behaviour was always dependant on the update order. The piston in the back had to receive the update first. To influence the update order one way was to power the front piston with a comparator and the back piston with a repeater. This behaviour was also reliable with doublepiston extenders facing upwards, being de-powered by a torch or a minecart powering a downwards facing double piston.Also the double retraction had to happen within the same block event.
The bug
Double piston extenders no longer retract both pistons at the same time, when they are depowered in the same game tick.
This behaviour (retracting both pistons at the same time) was classified as "Works As Intended" inMC-9342. People were used to this behaviour and many redstone contraptions rely on the sharper timings such a behaviour enables. Removing this feature would in some cases require major adjustments to those.How to recreate
This behaviour was always dependant on the update order. The piston in the back had to receive the update first. To influence the update order one way was to power the front piston with a comparator and the back piston with a repeater. This behaviour was also reliable with doublepiston extenders facing upwards, being de-powered by a torch or a minecart powering a downwards facing double piston.
Also the double retraction had to happen within the same block event.
The bug
Double piston extenders no longer retract both pistons at the same time, when they are depowered in the same game tick.
This behaviour (retracting both pistons at the same time) was classified as "Works As Intended" inMC-9342. People were used to this behaviour and many redstone contraptions rely on the sharper timings such a behaviour enables. Removing this feature would in some cases require major adjustments to those.How to recreate
This behaviour was always dependant on the update order. The piston in the back had to receive the update first. To influence the update order one way was to power the front piston with a comparator and the back piston with a repeater. This behaviour was also reliable with doublepiston extenders facing upwards, being de-powered by a torch or a minecart powering a downwards facing double piston.
Also the double retraction had to happen within the same block event.
The bug
Double piston extenders no longer retract both pistons at the same time, when they are depowered in the same game tick.
This behaviour (retracting both pistons at the same time) was classified as "Works As Intended" inMC-9342.How to recreate
This behaviour was always dependant on the update order. The piston in the back had to receive the update first. To influence the update order one way was to power the front piston with a comparator and the back piston with a repeater. This behaviour was also reliable with doublepiston extenders facing upwards, being de-powered by a torch or a minecart powering a downwards facing double piston.
Also the double retraction had to happen within the same block event.
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
rockenroll4life (Josh Letellier)piston no longer retracts an extended piston when de-powered at the same timePiston no longer retracts an extended piston when de-powered at the same time
![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
rockenroll4life (Josh Letellier)![[Helper] Lord_Quadrato](../../../data/avatars/users/26105.png){kind=small}
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
is duplicated by
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
![[Mod] Pokechu22](../../../data/avatars/users/92931.png){kind=small}
![[Helper] Michał](../../../data/avatars/users/43368.png){kind=small}
![[Mod] Les3awe](../../../data/avatars/users/79847.png){kind=small}
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
![[Mod] Chandler](../../../data/assets/gravatar/triwonder81.png){kind=small}
![[Mod] SPGoding](../../../data/avatars/users/44622.png){kind=small}
![[Mod] Avoma](../../../data/avatars/users/86198.png){kind=small}
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
Does MC-88959 describe your issue?
Thank you for your report!
However, this issue has been closed as a Duplicate of MC-88959.
It has been linked to this report. If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Looks like MC-49981 (a bug that was incorrectly marked as a dupe of an unrelated report) is back. And if my guess is correct, then MC-88959 (broken DP retraction) should now be fixed..? Afaik MC-49981 (persistent double headed piston) was "fixed" back in 1.9 by introducing MC-88959, rather than fixing MC-89146 (lost block event). Hopefully MC-89146 gets fixed this time.
![[Helper] Johnibur](../../../data/avatars/users/28381.png){kind=small}
Please note this site is for bug reports only. If you need help with the game, you may want to reach other platforms mentioned on the Community Support page.
We're actually already tracking this issue at MC-88959, so we will resolve and link this ticket as a Duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
That's why
MC-9342is resolvedThis is no duplicate.
I should have made it clearer, that the game does the EXACT OPPOSITE of what Jeb saw as intended behaviour.
No, he said he'd leave it the way it is, so the behaviour is more consistant
I don't know how I should make this any clearer. In
MC-9342people complained about both pistons retracting at the same time. Jeb decided that this (both pisotns retracting at the same time) is intended behaviour. Since 15w38a both pistons no longer retract at the same time. The behaviour got changed with the latest snapshot. People were used to this behaviour and a lot of redstone contraptions rely on it.Do people, that are responsible for bug reports, read those comments? Should I make a new bug report, that I've been misunderstood?
Please don't let me be misunderstood.
Sorry, I did get it the other way round. Reopened.
I hope someone can solve this problem because i can't play 1.9. I need to play in 1.8.9 to make some of my contraptions to work.
this behavior broke all the cornet 0 ticks mechanics!
It is need FIXING!
i did it looking UP
The fix to this that doesn't seem like a strange quirk would be to add full sticky piston chaining: when sticky pistons are retracted, they will pull other sticky pistons and slimeblocks so long as they are facing the same direction. Pulling ANY connected would complicate things, but would also allow more elaborate contraptions (connected blocks can always be slid off using non-movable blocks like obsidian, or pushed off since stickiness would not go both ways) so I guess it'd depend on how the community feels about it.
Chaining will simplify the needed redstone immensely, especially for longer chains. Instead of a simple on circuit and an advanced off circuit that needs to recursively de-power and re-power the chain to retract all pistons and move the target block, it will instead be completely the reverse circuit design (a simple line of pistons will be powered back-to-front and de-powered front-to-back). This is how the original piston mod functioned: https://youtu.be/mQEgPPjLoG8?t=57s
This, along with lower restrictions on slimeblocks (like making restrictions individually counted, that way the amount of normal blocks you can push... but then pistons are not counted in that number, and slimeblocks would count the number of self-connections they have versus the amount of non-slimeblock connections they have) would make big slimeblock doors possible (that are aesthetically pleasing) that don't close incredibly slowly like this: https://youtu.be/ZZXThD0pBLs?t=15s
still not fixed in 1.12
Confirmed for 1.12.2 and 17w43b
Confirmed for 1.13-pre3
Affects 18w48a, 18w48b, 18w49a and 18w50a
Affects 1.15.1
20w06a and 1.15.2 affected. Also affects with delayed retraction (repeater from image set to second stage)
Affects 1.16 Release Candidate 1
confirmed in 1.17.1
can confirm in 1.18.1
Can confirm in 1.19.3