[MCPE-19864] Redstone Created: 27/Jan/17  Updated: 09/Jun/20  Resolved: 27/Jan/17

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 1.0.2, 1.0.4.11, 1.0.5.0
Fix Version/s: None

Type: Bug
Reporter: CSpider
Resolution: Works As Intended Votes: 0
Labels: None

Attachments: PNG File Screenshot_2017-01-26-20-18-14.png    
Confirmation Status: Unconfirmed
Platform: Tablet - Android - Other (Specify in description)

 Description   

Redstone torch does not activate a block underneath like in other versions before 1.0.



 Comments   
Comment by Henry Markle [ 09/Jun/20 ]

Same thing happened to the Java edition once it's introduced (as a bug); it broke a lot of redstone builds, but it opened up a lot of different possibilities.

Comment by CSpider [ 28/May/20 ]

MantacidTech I know I was the one to report this as a bug, but now that I think about it, we really don't need quasi. Introduction of quasi is gonna break many builds/creations that people worked on for hours. Not having quasi also adds challenge 

Comment by MantacidTech [ 27/May/20 ]

it is my position that Quasiconnectivity should be added into Minecraft Bedrock, simply because it is so useful.

Comment by [MCPE Mod] Dr.Awesome4333 [ 15/Mar/17 ]

CrampedSpider72 that is because of quasiconectivity, which was an unintentional bug added that was later adopted as a feature and is currently not planned to be introduced to MCPE.

Comment by CSpider [ 14/Mar/17 ]

This works in Minecraft PC.

Comment by arian khatibi [ 20/Feb/17 ]

but why it brakes a whole ton of redstone creations pls change

Comment by [MCPE Mod] Dr.Awesome4333 [ 28/Jan/17 ]

I believe you misunderstood what I was saying.
The torch causing the piston to activate was the bug that is now fixed. A redstone torch can only power redstone components such as a piston if it is adjacent to the piston not with a block in between with the exception of a block above the torch with the piston on top of that block as redstone torches power the block above them.

Comment by [MCPE Mod] Dr.Awesome4333 [ 27/Jan/17 ]

Thanks for the report, however this has been resolved as Works as intended. This actually was a bug that was fixed in 1.0.0.1 see MCPE-16286.

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