[MCPE-16170] Observers powering redstone dust below do not power components adjacent to the dust Created: 12/Jul/16  Updated: 24/Oct/17  Resolved: 24/Oct/17

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 0.15.2, 0.15.6, 0.15.7, 0.15.90.2, 0.15.90.7, 0.15.9, 0.15.10, 0.15.90.8, 0.16.0, 0.16.1, 0.17.0.1, 0.16.2, 1.0.0.0, 1.0.0.1, 1.0.2, 1.0.3, 1.0.4.0, 1.0.4.1, 1.0.4.11, 1.0.5.13, 1.0.6.0, 1.0.5.54, 1.1.0.0, 1.0.7.0, 1.1.0.8, 1.1.0.9, 1.1.0.55, 1.1.1.0, 1.2.0.22
Fix Version/s: 1.2.5.12

Type: Bug
Reporter: Amphy2k
Resolution: Fixed Votes: 10
Labels: observer, redstone, redstone_wire

Attachments: PNG File 07078B8E-D2F6-4745-810A-2357C9E297C8.PNG     PNG File A42D621C-1415-42FA-9AB6-534823C74B98.PNG     PNG File D72D4ADB-7D64-4E98-A278-B1833D7B9DAA.PNG     PNG File Observer-Dust-Lamp-Bug.png    
Issue Links:
Relates
relates to MCPE-11871 Redstone not powering horizontally ad... Resolved
relates to MCPE-14668 Redstone repeaters facing into a reds... Resolved
relates to MCPE-15850 Observers redirect Redstone Dust (but... Resolved
relates to MCPE-16831 Redstone comparators do not test for ... Resolved
relates to MCPE-16892 Redstone powers the wrong blocks when... Open
relates to MCPE-21898 Redstone torch is on although it shou... Resolved
Confirmation Status: Confirmed
Platform: Tablet - iOS - iPad Pro
CHK:
ADO: 64483

 Description   

I am building a hidden stair case and when attempting to use the observer to power my t-flip flop i realized the pulse dose not effect the t-flip flop.

After some testing I realized that its pulse doesn't power any block next to it yet when 2 dust away it will.

The first and second picture show how it doesn't power any type of block, lamp piston and my own problem, the dropper, it doesn't work. The third demonstrates how it dose power the farther piston yet not the close one. This i assume would work with any other block that can be powered (dropper, lamp, etc)

How to create (its a 1 wide bug so pictures should be better at explaining it)
1: place a redstone dust
2: place an observer so it can power the redstone dust
3: place a lever (or any block that can easily toggle the observer) on top of the observer
4: place a piston connected to the redstone (horizontal to the observer)
5: place another redstone dust so the first one points to the first piston
6: place another piston at the end of the second redstone dust

Edit by SuperGeniusZeb: Note that pistons are exempt from this bug since they redirect redstone dust.



 Comments   
Comment by MaladjustedPlatypus [ 23/Oct/17 ]

Appears to be fixed as of Beta 1.2.5 Build 2

Comment by Zeb [ 29/Mar/17 ]

Revised title to be more descriptive.

Comment by Zeb [ 10/Oct/16 ]

Affects 0.15.90.8 (0.16.0 beta build 5).

Comment by Zeb [ 05/Oct/16 ]

Affects 0.15.10. (Tested on Windows 10.)

Comment by Zeb [ 29/Sep/16 ]

Affects 0.15.9. (Tested on Windows 10.)

Comment by Zeb [ 16/Sep/16 ]

Affects 0.16.0 Beta Build 4 (AKA 0.15.90.7).

Comment by Zeb [ 03/Sep/16 ]

Confirmed for 0.15.90.2. (Tested on Pocket Edition.)

Comment by Zeb [ 01/Sep/16 ]

Confirmed for 0.15.7. (Tested on Windows 10.)

Comment by Zeb [ 27/Aug/16 ]

Confirmed for 0.15.6. (Tested on Windows 10.)

Probably due to the change to pistons to make them redirect redstone dust, this bug is no longer reproducible with pistons. However, it still occurs for redstone lamps, dipsensers, & droppers. (See attached screenshot.)

Comment by PHO [ 13/Jul/16 ]

But there is a subtle difference between this and MCPE-11871, because in the observer case it's the observer that acts as a power source while in MCPE-11871 those opaque blocks aren't themselves power sources but they are merely strongly-powered. So I don't want to close this one as a duplicate.

Comment by Amphy2k [ 12/Jul/16 ]

Woah now that i see the bug in 11871 it seems like its the exact same bug. If thats the case this isnt a problem with Observers more so its a problem with all redstone.

Comment by PHO [ 12/Jul/16 ]

This is very similar to, but not exactly the same as, MCPE-11871.

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