When a piston is powered with a 0 redstone tick pulse (or a half redstone tick pulse, meaning it's powered for only 1 game tick but not a full redstone tick), it only gives a pulse at some occasions, as it can be seen in the screenshots.
To reproduce:
Make a monostable circuit (a sticky piston facing up with a block on top and a repeater pointing at the block), put a piston with a block on its head, next to the monostable circuit (as it can be seen in the screenshots), and power it.
Linked issues
is duplicated by 1
Attachments
Comments 14
This is really weird because with some specific setup, pistons respond. See http://youtu.be/J12aW0hmT98
Is this still a concern in the latest Minecraft version 14w30c? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Mojang seems to have decided that the purpose of pistons is to have as many inconsistent behaviors as possible. I don't think any piston-related reports are going to be fixed any time soon.
This bug is not due to pistons.
Tho its hard to test without them
Its due to block update order XYZ
So the X-piston checks for power and fires
Then the Y-piston checks for power and fires (which moves the block)
Then Z-piston checks for power (sees no power due to the block being moved) and doesn't do anything
If the block update order was changed from XYZ to XZY or YXZ there would be way less Directional stuff
Confirmed.