Piston pushing redstone block bug
When a sticky piston pushes a redstone block veritcally and the power source to the piston is removed, the piston stays extended
I expected it to retract when the power source was removed
The piston stayed extended until the redstone block was removed (removing the blocks around the piston didn't do anything so it isn't a block update issue)
Steps to Reproduce:
1.Place a sticky piston with a restone block on its surface vertically
2.Put a torch under the piston
3.Remove the torch
Environment
Windows 7 64 bit
Created Issue:
Piston pushing redstone block bug
When a sticky piston pushes a redstone block veritcally and the power source to the piston is removed, the piston stays extended
I expected it to retract when the power source was removed
The piston stayed extended until the redstone block was removed (removing the blocks around the piston didn't do anything so it isn't a block update issue)
Steps to Reproduce:
1.Place a sticky piston with a restone block on its surface vertically
2.Put a torch under the piston
3.Remove the torchEnvironment
Windows 7 64 bit
Linked Issues
duplicates1
TRASH-991
- Unresolved
- Open
- Unconfirmed
- Creative
- bug piston redstone redstoneblock
- 13w03a
duplicates
MC-17025
duplicates
TRASH-991
59th duplicate? oh my god.
according to my observation, pistons, sticky pistons, dispensers and droppers can be activated by applying Redstone signal to the space above it; so if there's a Redstone block/charged block/Redstone torch etc two block above it with air in between, the (sticky)piston/dispenser/dropper will activate remotely and deactivate once the signal is removed, but only when the block adjacent to it is changed.
I don't know a lot about the technical stuff here but I think this is due to some 'update'(possibly block or chunk update), which is triggered by the block space adjacent to the piston/dispenser/dropper changing(placing/destroying etc.), which, combined with space above's 'conduction' caused the remotely-activating-and-non-retracting piston; the dispenser/dropper are impulse-type blocks, so they only show remote activation.
in the examples below, most blocks activated by placement of a signal source adjacent to the air above said block/'updating' said block by destroying block next to it after placing signal source, and deactivate by 'updating' the block (by placing blocks next to it) after removing signal source. most signal sources are block, so their placement themselves will bring the 'update'(see the text example below); the button is a special case, as it doesn't have any signal on placement, so I used a second piston to simultaneously change the space next to target piston(in this case, place a piston head in it), thus 'updating' it while giving power to the air above it, so it activated as expected.
these two bugs/unintended features((sticky)pistons/dispensers/droppers powered through air above & needs 'update' to activate/deactivate) can explain a lot of issues here(such as placing a redstone block on top of top-facing piston causing the piston not retracting; removing the redstone block give the piston 'update'(because the block is adjacent to its head) so it will retract.):
59th duplicate of
MC-108, please use the search function to see if your bug has already been submitted. Currently over 45% of tickets are being closed as duplicate.Tails, THIS IS A BUG.
MC-108only talks about piston extension in 1.4.5, not the latest snapshot/update which pertains to redstone blocks. This bug is also present in 1.6.2. Please as a member of the community re-investigate the bug, and if needed, ask me for a bug report. Thank you.~Jouster500
@Zachary: Stop spamming