The upward facing piston monostable is both orientational and coordinate dependant > Huge inconsistency
The upward facing piston monostable is very inconsistent.
I will show 4 situations, each with 2 inputs, 2 pistons as outputs, and 2 pictures of what happens when I flick the first or second lever.
Each of this has the lever above and on the left, and the pistons on the right and on the bottom. I will change the direction the pistons are facing, and move the setup for each situation.
In situation 1 (Picture 1 and 2), we see that powering the lever on top powers only the piston on the right, and powering the other lever powers the other piston.
In situation 2 (Picture 3 and 4), we see that powering the lever on top powers none of the 2 pistons, and powering the other lever powers the piston on the right.
situation 3 (Picture 5 and 6) is identical to situation 2, the 2 pistons are just facing a different direction, and are in a different location.
situation 4 (Picture 7 and 8) is identical to situation 1, one of the pistons is just facing a different direction, and are in a different location.
The top of the pictures is always facing f:2(North)
Also: I know this is a duplicate, but I just wanted to make the bug more clear 
I really hate this bug, and I think it should be fixed by pre-release.
UPDATE:
Powering the monostable with redstone or repeater actually makes a difference.
EDIT: Since 14w19a, this monostable works consistently in one orientation, in the other however it is still coordinate dependant.
Nice 20w18a repro: https://www.youtube.com/watch?v=ptK-7n--yYM
Linked Issues
is duplicated by13
MC-11064New T-Flip Flop nonfunctioningDuplicateMC-12518directional quirk with redstoneDuplicateMC-12552Directional Bug (Piston)DuplicateMC-15583Piston MonostablesDuplicateMC-24009Directional issue with Redstone Flip-FlopDuplicateMC-30506Piston + strongly powered blocks picking up signal only in specific directions.DuplicateMC-150121monostable circuit does not power along north south linesDuplicateMC-159186Different pistons activate depending on what direction a circuit is facingDuplicateMC-174753One Tick Pulse Pistons DirectionalityDuplicateMC-182166Target block powering of pistons differs in negative-X direction. DuplicateMC-192232Zero-tick piston not gettin powered from north to south or south to north alignmentDuplicateMC-196123T-Flip Flop only working in east/west directionDuplicateMC-204875Piston and Sticky Piston do not recieve redstone signal in a specific contraption. Duplicate
LowAttachments10
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
![[Mod] Jiingy](../../../data/avatars/users/91802.png){kind=small}
Created Issue:
The upward facing piston monostable is both orientational and coordinate dependant -> Huge inconsistency
The upward facing piston monostable is very inconsistent.
I will show 4 situations, each with 2 inputs, 2 pistons as outputs, and 2 pictures of what happens when I flick the first or second lever.
Each of this has the lever above and on the left, and the pistons on the right and on the bottom. I will change the direction the pistons are facing, and move the setup for each situation.In situation 1 (Picture 1 and 2), we see that powering the lever on top powers only the piston on the right, and powering the other lever powers the other piston.
In situation 2 (Picture 3 and 4), we see that powering the lever on top powers none of the 2 pistons, and powering the other lever powers the piston on the right.
situation 3 (Picture 5 and 6) is identical to situation 2, the 2 pistons are just facing a different direction, and are in a different location.
situation 4 (Picture 7 and 8) is identical to situation 1, one of the pistons is just facing a different direction, and are in a different location.
The top of the pictures is always facing f:2(North)
I really hate this bug, and I think it should be fixed by pre-release.
Environment
Mac OSX
Attachments8
The upward facing piston monostable is both orientational and coordinate dependant-> Huge inconsistency
The upward facing piston monostable is very inconsistent.
I will show 4 situations, each with 2 inputs, 2 pistons as outputs, and 2 pictures of what happens when I flick the first or second lever.
Each of this has the lever above and on the left, and the pistons on the right and on the bottom. I will change the direction the pistons are facing, and move the setup for each situation.In situation 1 (Picture 1 and 2), we see that powering the lever on top powers only the piston on the right, and powering the other lever powers the other piston.
In situation 2 (Picture 3 and 4), we see that powering the lever on top powers none of the 2 pistons, and powering the other lever powers the piston on the right.
situation 3 (Picture 5 and 6) is identical to situation 2, the 2 pistons are just facing a different direction, and are in a different location.
situation 4 (Picture 7 and 8) is identical to situation 1, one of the pistons is just facing a different direction, and are in a different location.
The top of the pictures is always facing f:2(North)
I really hate this bug, and I think it should be fixed by pre-release.
The upward facing piston monostable is very inconsistent.
I will show 4 situations, each with 2 inputs, 2 pistons as outputs, and 2 pictures of what happens when I flick the first or second lever.
Each of this has the lever above and on the left, and the pistons on the right and on the bottom. I will change the direction the pistons are facing, and move the setup for each situation.In situation 1 (Picture 1 and 2), we see that powering the lever on top powers only the piston on the right, and powering the other lever powers the other piston.
In situation 2 (Picture 3 and 4), we see that powering the lever on top powers none of the 2 pistons, and powering the other lever powers the piston on the right.
situation 3 (Picture 5 and 6) is identical to situation 2, the 2 pistons are just facing a different direction, and are in a different location.
situation 4 (Picture 7 and 8) is identical to situation 1, one of the pistons is just facing a different direction, and are in a different location.
The top of the pictures is always facing f:2(North)
Also: I know this is a duplicate, but I just wanted to make the bug more clearI really hate this bug, and I think it should be fixed by pre-release.
is duplicated by
is duplicated by
The upward facing piston monostable is very inconsistent.
I will show 4 situations, each with 2 inputs, 2 pistons as outputs, and 2 pictures of what happens when I flick the first or second lever.
Each of this has the lever above and on the left, and the pistons on the right and on the bottom. I will change the direction the pistons are facing, and move the setup for each situation.In situation 1 (Picture 1 and 2), we see that powering the lever on top powers only the piston on the right, and powering the other lever powers the other piston.
In situation 2 (Picture 3 and 4), we see that powering the lever on top powers none of the 2 pistons, and powering the other lever powers the piston on the right.
situation 3 (Picture 5 and 6) is identical to situation 2, the 2 pistons are just facing a different direction, and are in a different location.
situation 4 (Picture 7 and 8) is identical to situation 1, one of the pistons is just facing a different direction, and are in a different location.
The top of the pictures is always facing f:2(North)
Also: I know this is a duplicate, but I just wanted to make the bug more clearI really hate this bug, and I think it should be fixed by pre-release.
UPDATE:
Powering the monostable with redstone or repeater actually makes a difference.
Mac OSX
Any platform
is duplicated by
The upward facing piston monostable is very inconsistent.
I will show 4 situations, each with 2 inputs, 2 pistons as outputs, and 2 pictures of what happens when I flick the first or second lever.
Each of this has the lever above and on the left, and the pistons on the right and on the bottom. I will change the direction the pistons are facing, and move the setup for each situation.In situation 1 (Picture 1 and 2), we see that powering the lever on top powers only the piston on the right, and powering the other lever powers the other piston.
In situation 2 (Picture 3 and 4), we see that powering the lever on top powers none of the 2 pistons, and powering the other lever powers the piston on the right.
situation 3 (Picture 5 and 6) is identical to situation 2, the 2 pistons are just facing a different direction, and are in a different location.
situation 4 (Picture 7 and 8) is identical to situation 1, one of the pistons is just facing a different direction, and are in a different location.
The top of the pictures is always facing f:2(North)
Also: I know this is a duplicate, but I just wanted to make the bug more clearI really hate this bug, and I think it should be fixed by pre-release.
UPDATE:
Powering the monostable with redstone or repeater actually makes a difference.EDIT: Since 14w19a, this monostable works consistently in one orientation, in the other however it is still coordinate dependant.
![[Mod] Torabi](../../../data/assets/gravatar/torabi.png){kind=small}
is duplicated by
Any platform
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
![[Bot] Arisa](../../../data/assets/gravatar/mustek2.png){kind=small}
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
is duplicated by
![[Mod] NeunEinser](../../../data/avatars/users/39263.png){kind=small}
is duplicated by
![[Mojang] Panda](../../../data/avatars/users/41658.png){kind=small}
relates to
The upward facing piston monostable is very inconsistent.
I will show 4 situations, each with 2 inputs, 2 pistons as outputs, and 2 pictures of what happens when I flick the first or second lever.
Each of this has the lever above and on the left, and the pistons on the right and on the bottom. I will change the direction the pistons are facing, and move the setup for each situation.In situation 1 (Picture 1 and 2), we see that powering the lever on top powers only the piston on the right, and powering the other lever powers the other piston.
In situation 2 (Picture 3 and 4), we see that powering the lever on top powers none of the 2 pistons, and powering the other lever powers the piston on the right.
situation 3 (Picture 5 and 6) is identical to situation 2, the 2 pistons are just facing a different direction, and are in a different location.
situation 4 (Picture 7 and 8) is identical to situation 1, one of the pistons is just facing a different direction, and are in a different location.
The top of the pictures is always facing f:2(North)
Also: I know this is a duplicate, but I just wanted to make the bug more clearI really hate this bug, and I think it should be fixed by pre-release.
UPDATE:
Powering the monostable with redstone or repeater actually makes a difference.EDIT: Since 14w19a, this monostable works consistently in one orientation, in the other however it is still coordinate dependant.
Nice 20w18a repro: https://www.youtube.com/watch?v=ptK-7n--yYM
is duplicated by
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
is duplicated by
is duplicated by
is duplicated by
![[Mod] Chandler](../../../data/assets/gravatar/triwonder81.png){kind=small}
![[Helper] Johnibur](../../../data/avatars/users/28381.png){kind=small}
![[Helper] Jack McKalling](../../../data/avatars/users/92859.png){kind=small}
![[Mod] SPGoding](../../../data/avatars/users/44622.png){kind=small}
![[Mod] markderickson](../../../data/avatars/users/18946.svg){kind=small}
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
![[Mod] turbo](../../../data/avatars/users/92867.png){kind=small}
is duplicated by
This ticket has been marked as a duplicate of MC-11165, in favor of the better description/information provided.
This is caused by the order in which the blocks are updated, and I believe it to be the same issue as MC-11165.
Thank you for your report!
We're actually already tracking this issue in MC-11165, so I've resolved and linked 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
Actually, this is a duplicate of MC-11165
Hi there!
This looks like a duplicate of MC-11165. Make sure to do a quick search for your bug before posting it, and then vote for it, comment on it, and follow it. This is the best way for it to be prioritized by Mojang. Making a duplicate post means more work for the volunteers who help out to moderate and clean things up for the developers to look at and fix what needs to be fixed.
Hi there!
Does MC-11165 describe your issue?
Hello! Does MC-11165 happen to describe your issue?
Duplicates MC-11165. See the YouTube video there, or the mp4 video (while it's techincally invalidated because the user has a modified client in it, I can reproduce that same behavior in vanilla).
Can confirm for 1.6.2.
This is now consistent in one orientation, in the other orientation it is still coordinate dependant.
(14w19a)
According to a comment on this video, this is caused by the order of the block updates:
Is this still a concern in the current Minecraft version 1.8.1 Prerelease 3 / Launcher version 1.5.3 or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
No response for over a year.
Sorry, yes this is still a concern in the current version, however it has become slightly more stable.
I'm quite certain that it works reliably if the monostable is powered from 2 of 4 directions now, but it's definitely still in the game.
The preferred solution for me would be to make it not power any pistons, but still power repeaters.
Let me argue why:
Nearly every redstone contraption is made to not rely on unreliable bugs in the game, to ensure that it is not coordinate dependant, random, or direction dependant.
So nearly every redstone contraption is made to not use this monostable to power pistons directly, but this monostable is the most often used monostable in the game, so it is important that it will power repeaters. Fixing it this way will break next to no contraptions. Remember that most redstone creations take hours to complete, and some even months. Having to go back and fix them, which might sometimes be impossible, will take another large amount of time.
I know that this way of fixing it doesn't make much sense, but now you know why I prefer it, and I'm sure you can see my point.
[Mod] Torabi DicoTheRedstoner I can confirm that it is caused by the update order.
Currently: west east down up north south
Depending on if the piston in front or the one below get updated first the circuit behaves different.
It's impossible to avoid all directional behaviour because the updates need some order, but the y-axis shouldn't be updated in between the two other axis.
Because that causes everything that depends on something updating a y-direction before a horizontal one or the other way around, to be directional.
The question is: What order would be best?
Y-Last: west east north south down up
Y-First: down up west east north south
Y-Split: down west east north south up
I think it would make sense to keep the horizontal directions in the same order they have been before to minimize the things that would break. I also don't see any advantage changing it.
Of course you could also switch the places of up and down in all of these.
No matter how you change it, it would break some things that depend on update orders. They would be fixable though.
I made a mod that allows to set the update order with a command (E.g. /updateorder west east north south down up).
If you want to try how different update orders would behave you can download it here: http://www.mediafire.com/download/b9mjwuimu2ei7wg/1.9_UpdateOrder.zip
Video about it with a more general/theoretical approach: https://www.youtube.com/watch?v=aRr3NpmQiCg
Is this still an issue in the most recent versions (currently that is 1.10.2, or 16w43a) 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.
I can confirm 16w43a.
Can confirm for 1.12
confirmed still in 20w08a
Still present in 1.16.1.
Hi there!
Can confirm in 20w27a.
In 1.16.2 RC-1
Can confirm in 1.17.1.
This issue is fixed in the 24w33a redstone experiment:
2024-08-20_23-17-03.mp4