I wanted to make a redstone contraption in which the sticky piston in the image retracts and pulls the block when I press the button.
What I expected to happen: I press the button, the redstone behind it will power the redstone torch, which unpowers the redstone behind that, which leaves the piston without redstone signal, making it retract, which makes the block attached to it move while the signal is gone.
What happened: I press the button, the redstone behind it will power the redstone torch, which unpowers the redstone behind that, which leaves the piston without redstone signal, making it retract for really only like...1 frame. The block attached to it does not move. (I actually caught the frame on image 3)
I attached some screenshots:
+ 1.png: button in default mode
+ 2.png: button activated
+ 3.png: button during the second "click" sound, so de-activating.
If I were to remove the redstone between the torch and the piston, the piston would retract normally.
Weird fact: I enter this place in my world via a latch or what is it called. Basically a button giving an inverted signal to a piston, but for an extended ammount of time. It...works normally.
Related issues
Attachments
Comments
migrated
migrated
Update:
I removed the block with the button on it, and placed the switch on the block behind it (the one blocked from view in the screenshot) with it facing the position where the screenshot was taken from. Now thàt works correctly.
While typing this I tried to re-place the block and placing the button, making it the way it was. Now it works correctly. Am afraid we'll never know what caused this :s
Edit: I placed it facing the screenshot position. placing it where it really was (facing left) still causes this issue. Sorry for the confusion.
More update: It seems to also glitch with the button facing me, on the block to the left (moved the other block down and put redstone on it, ofcourse)
migrated
Does https://mojang.atlassian.net/i#browse/MC-108 responds your issue?
migrated
I've seen this issue. After a reread I see it kind of includes my issue, though, I'll quote:
"Pistons extend when blocks are providing power to the block above them, even if they don't update the piston."
So...I removed the redstone directly after the torch; so the button powers a the redstone up till the torch; then a gap; then the redstone 2 blocks under the button.
The piston does NOT extend, meaning that the switch is NOT powering the piston.
This is getting pretty nasty now:
Guess I'll make some definitions to (hopefully) prevent confusion. I reverted the changes I made in my game so the images apply again. So there is:
a button, on a block, powering redstone, powering a redstone torch, powering more redstone, powering the piston.
When I remove the redstone directly next to the piston, the button powers the piston while on; then turns off. the piston retracts, as the button unpowers; so you think it DOES power the piston? Let me remove the torch as well.
Removing the torch, I press the button and nothing happens.
When instead of removing the redstone next to the piston and/or the torch, I remove the redstone next to it; next to the torch; nothing happens when I press the button either,
Instead of placing the redstone where it was, I now place the redstone to the left of the redstone torch. (so the wire goes to the piston but in the wrong direction so it wouldn't power it.
The button now once again, powers the piston.
Removing the redstone torch only will always result in the button not doing anything.
Conclusion: It's not exactly the same issue. besides, I tried to reproduce it, but updating the block did nothing at all. I wouldn't call this a duplicate just yet.
I'll open a test world to test this further, Now I'm curious...and bored. especially curious.
migrated
Testing more in creative mode:
These are 2 bugs.
1.: when placing a piston, then a block on top, then a block diagonally, with a switch above the previous block, like:
[ b ] [ s ]
[ ] [ b ]
[ ] [ P ]
(P is piston, b is block, s is switch, nothing is....nothing)
what happens: when powering the switch, the piston will react accordingly, but that requires a block update. so turn it on, update, and it extends. and vice versa. turn it on and off then update and nothing happens.
2. Redstone updates 2 blocks ahead.
Where with BUD-switches you place your block. keep this block empty and place a redstone one block further away. Place another redstone connecting to it; further away yet (triggers the BUD already). power and/or unpower the redstone to trigger the BUD.
So what is my problem? I power a sticky piston with a switch, but it would need a block update first, which happens by bug number 2.
Conclusion: I vote for splitting this up, as this is actually 2 bugs working together.
Edit: in fact MC-108 is that first half of the bug. I'll be looking for a redstone BUD bug quickly now, now that I know that also affects this. I haven't found one. So unless search results have a way to get to a next page this is a new issue. (haven't seen a next page button)
migrated
Making a seperate bug report for the redstone update thing, as this is 2 issues. (it said it's unwanted to have 2 issues in 1 report)
I'll link the new one in this comment, as it kind of IS relevant. Please link this as duplicate to the new issue as well, as this is a combo, and no exact duplicate of only 108.
Link: MC-26545