See attached screenshots. The piston is not powered by the redstone dust behind it even though the dust is pointing into the piston. The piston only becomes powered once you connect that piece of redstone dust with something else, like a lever/button/redstone dust/redstone block. This can be on the same level, below or above (if applicable). The piece of redstone dust may not be connected to anything on the side, otherwise the piston won't be powered either.
I'm not even going to attempt explaining what logic error caused this bug.
Related issues
is duplicated by
MC-12643
Redstone wire running through a piston doesn't extend it!
MC-12811
Redstone wire running through a piston extends under certain circumstances. (see screenshots)
MC-21689
piston bug with detection powered redstone wire
MC-25534
Redstone dust seens to directly power block but it doesn't
MC-44063
Piston/Hopper/TNT won't power(certain position) when redstone transfer upward by slab/glowstone
MC-89855
Top piece of staircase redstone dust doesn't power blocks on the same height in the direction it is powered from unless only connected to something on the other side
MC-89866
Inconsistent piston behaviour regarding redstone dust.
MC-100326
Diagonal piston towers behave strangely when powered from below
MC-138049
Sticky piston bug
relates to
Attachments
Comments
migrated
migrated
If you place a block next to the pistons that aren't extending, do they update and extend?
migrated
No, they are not waiting for an update.
migrated
I was hoping it was a new way for a bud switch, but sadly no. lol
migrated
Added image so its clearer for you guys.
migrated
Confirmed.
migrated
I as well am experiencing such problems with pistons although i am not sure weather or not to report it as a new bug.
(pistons powered with a redstone block forced into place above the now bugged piston, by a non effected stick piston are powering other pistons diagonally and will not retract after the power"redstone block" source is retracted "only will retract after redstone block and others nearby are destroyed" and so not helping my constant testing for a perfect fully automatic sugarcane farm)
If this is a new bug please contact me and i can provide more details and screen shots.
migrated
due to BUD this may have to stay as is, however I have found some fun uses for it.
migrated
Still a concern in 1.7.5 and 14w08a
migrated
Confirmed for 14w18a
Jens Bergensten
Won't fix because the risk is too high that something else changes behavior.
RedCMD
The bug is that when a block (or piston, redstone lamp, trapdoor etc) checks to see if redstone is pointing towards it
It actually checks to see if the dust is pointing away from it AND if its not pointing to the left or right
(Theres a seperate check to see if the dust is a dot, rather than a line)
A simple fix that works 100% is...
Inside the BlockRedstoneWire.class
At the bottom of the method getWeakPower()
Just below
if (side.getAxis().isHorizontal() && enumset.isEmpty()) {
return i;
}
else if (enumset.contains(side) && !enumset.contains(side.rotateYCCW()) && !enumset.contains(side.rotateY())) {
return i;
}and above
else
{
return 0;
}add
else if (enumset.contains(side.getOpposite())) {
return i;
}(It fixes all except the slab tower, which is another bug)
[media]
RedCMD
Fixed 20w18a