[MCPE-15195] Restone torches on piston power piston Created: 09/Jun/16  Updated: 05/Sep/16  Resolved: 05/Sep/16

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 0.15.0 Beta build 2, 0.15.0, 0.15.4
Fix Version/s: 0.15.7

Type: Bug
Reporter: Joshua Michael Hess
Resolution: Fixed Votes: 2
Labels: None

Attachments: PNG File Screenshot_2016-06-09-17-22-55.png    
Issue Links:
Duplicate
is duplicated by MCPE-16504 This is a glitch in Mc pe and win 10 ... Resolved
Relates
relates to MCPE-16283 Redstone torch burn/turn off when pla... Resolved
relates to MCPE-16286 Pistons are incorrectly activated whe... Resolved
Confirmation Status: Unconfirmed
Platform: Phone - Android - Samsung Galaxy Note

 Description   

Torches placed on the side of a piston will activate the piston, but according to the wiki, torches should not power the blocks they are on.



 Comments   
Comment by PHO [ 05/Sep/16 ]

Yes. This one has been fixed in a sense. Closing as Fixed.

Comment by Zeb [ 04/Sep/16 ]

Shouldn't this bug be closed since the new behavior is in MCPE-16283? Or should that bug be closed and this one be updated with the new behavior?

Comment by Zeb [ 11/Aug/16 ]

Confirmed for 0.15.6 (Tested on Windows 10.) See above comment. The bug report's description should be updated to reflect the change in behavior since either 0.15.3 or 0.15.4.

Comment by Zeb [ 08/Aug/16 ]

Confirmed for 0.15.4. (Tested on Windows 10.)

The behavior is different now, however. Previously the torches would simply power the piston. Now they blink rapidly, powering the piston, and then burn out, unpowering the piston. (As if they were in a torch-burnout-clock-circuit.)

Comment by AMAN4700 [ 08/Aug/16 ]

Please respond and add the current version if you can reproduce this issue.

Comment by Zeb [ 13/Jun/16 ]

Confirmed for 0.15.0 official release. (Tested on Windows 10 Edition.)

EDIT: Also confirmed for 0.15.0 on Android.

Comment by Joshua Michael Hess [ 11/Jun/16 ]

Still affects build 3

Generated at Sat Jan 11 15:06:43 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.