[MCPE-12420] Redstone dust not powering the correct blocks Created: 15/Jan/16  Updated: 28/Apr/16  Resolved: 28/Apr/16

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 0.13.0
Fix Version/s: 0.14.2

Type: Bug
Reporter: TRCYX
Resolution: Fixed Votes: 0
Labels: None

Attachments: PNG File IMG_1718.PNG     PNG File IMG_1720.PNG     PNG File IMG_1721.PNG     PNG File IMG_1722.PNG    
Issue Links:
Relates
relates to MCPE-11353 Redstone dot doesn't power blocks on ... Resolved
relates to MCPE-12776 Dropper or dispenser is not activated... Resolved
Confirmation Status: Unconfirmed
Platform: Phone - iOS - iPhone 5S

 Description   

Well actually I'm using 0.13.1 but there isn't this option.
In MCPE, a redstone dust "connected to nothing" automatically points to all four adjacent blocks, but in my pictures some adjacent blocks which are pointed to doesn't seem to be actually powered.
To reproduce this situation, place a redstone dust pointing to a block in any direction. As the world is made of blocks, now there is a row of blocks in which both the block and the redstone dust is in the row. Power the redstone dust with a block or a redstone torch which is adjacent to the redstone dust but is out of that row. Test if the first block (pointed by the wire) is powered and you will find that it is not.
I'm afraid this can't be explained clearly so in the screenshots below there are several situations in which the bug occurs.
The bug happens in different directions, so I wonder if the code about checking which directions a redstone dust points to is incorrect.



 Comments   
Comment by PHO [ 20/Feb/16 ]

Fixed in 0.14.0 alpha.

Comment by TRCYX [ 16/Jan/16 ]

Well it's only that I suppose they occur because of the same reason and thanks for pointing it out.

Comment by PHO [ 16/Jan/16 ]

I don't think so. It's a separate glitch MCPE-11668.

Comment by TRCYX [ 16/Jan/16 ]

Well sometimes the dust powers more blocks than supposed. I'm thinking it's the same bug.

Comment by PHO [ 15/Jan/16 ]

But wait, the screenshots IMG_1718.PNG and IMG_1720.PNG provide something new to MCPE-11353. Given the fact that apparently duplicating MCPE-11871 turned out to be a different bug, I think it's safer to mark this Related to, not Duplicate of MCPE-11353.

Comment by ItsPlantseed [ 15/Jan/16 ]

"Duplicate" of MCPE-11353

Generated at Sat Jan 11 14:55:56 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.