Redstone not powering horizontally adjacent blocks

It's not just about torches. When a line of redstone dust is powered by a strongly-powered adjacent block, it fails to power a horizontally adjacent block while it powers a block below it or another dust placed next to it (See

). The glitch does not occur when the dust in question is a dot, not a line (Correction: the same thing will happen when a dot is powered sideways but not from below). So this is very similar to [MCPE-11353] but apparently not the same.

It turned out that the line needs not to be powered sideways to cause the glitch. The same oddity happens when it's powered by a block below it. See [MCPE-11887] and

.

Confirmed while making a NOT NOT (see MCPE-11887)

@PHO I have updated my bug report with regard to your comments.

Fixed in 0.13.1. Thanks.

The glitch came back to 0.14.0 alpha. Please reopen this.

@PHO do I have to reopen it? Or can only a moderator do so

@@unknown only moderators, unfortunately

Moderators, please reopen this. The glitch came back to 0.14.0 alpha, and it's mislabeled as "Duplicate" too.

This is not a duplicate and has been confirmed by the community, however the confirmation status in unconfirmed.

@unknown, it's been reopened already.

Confirmed on 0.15.0 on Windows 10.

I was able to reproduce every situation in the pictures except the one in another-pattern-of-redstone-glitch.png. Powering from strong power below seems to be fixed, but horizontal strong power is still buggy.

Affects 0.15.1. (Tested on Windows 10.)

Affects 0.15.4. (Tested on Windows 10.)

Also confirmed in 0.15.4 on Samsung Galaxy S5

Is Mojang aware of this at all? There hasn't been an assignee on this issue at all since this issue was created.

@Kyle Bartush We no longer assign tickets to people in this tracker.

Just found this glitch on my iPhone running mcpe 0.15.6. One interesting note is that pistons are not affected by this glitch, probably due to the change that makes redstone now automatically connect to pistons.

Confirmed for 0.15.7. (Tested on Windows 10.)

Confirmed for 0.15.90.2. Using an Acer B1-750 tablet. (Intel HD Graphics for BayTrail, Android KitKat 4.4.4)

Affects 0.16.0 Beta Build 4 (AKA 0.15.90.7).

I wonder if this bug has the same root cause as MCPE-11353. Perhaps that bug was never completely fixed, and this is what is left of it?

Also, affects 0.15.10. (Tested on Windows 10.)

Affects 0.15.90.8 (0.16.0 beta build 5).

This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).

Some of the example are working correctly in 1.0.0, but there is one remaining instance which does not behave in the same was as Java redstone:

This one also shows a bug in 1.0.2. The left-hand block can not by powered by activating the lever on top of the center block. But it can be powered by the lever on the side.

Still present in 1.0.3... I can't believe this bug is still present after all this time

Affect version 1.2.0.2 (Win 10).

Some, but NOT all of the cases of this bug have been fixed as of 1.2.5 build 2.

Fixed in 1.2.6.2, as far as I can tell! If anyone finds a case of this bug that is still occurring, please post it here and I'll reopen the ticket.

Not fixed in 1.2.6 release. Even the use cases in the original attachments don't work. Video attached.

Seems to be at least partially broken again in the final 1.2.6 release.

As the 'Minecraft 12_6_2017 4_15_38 PM.png' image shows, this is fixed for certain orientations, but not all.

https://gyazo.com/418e45b94834496e3bd57674bba8fab1

Repeaters don't power pistons that are positioned like this. When replacing the repeaters with redstone, the piston DOES get powered.

@unknown, that behavior is intentional. The redstone wire powers the block below it and any non-wire blocks adjacent to that block, such as the piston, whereas the repeater only powers the block on its output side and any blocks adjacent to that block, if there is one. Because the repeater is just pointing into air, it powers nothing, and so the piston is not powered.

In Java Edition, a quirky behavior called quasi-connectivity (or QC - caused by mistakes in the redstone & piston code) causes pistons, droppers, and dispensers to be powered in instances where they logically should not, such as in this case with the repeater.

Ah I see. Thanks for informing me. I'm not the best at redstone. I'm also still used to the Java edition 🙂

This makes my previous comment invalid.

Confirmed to be fully fixed using my previous test cases.

The error demonstrated in the "Lever-Off.png" and "Lever-On.png" attachments still exists. Tested in Windows 10 1.2.10.2.

Odd... Perhaps the fix was reverted from the beta? That exact test case was fixed in it (the beta).

@unknown, the 1.2.10.2 release seems to have been based off a different development branch than the 1.2.10.1 beta build, so some of the fixes/changes in that beta will likely show up again in 1.2.11. Until then, I'll reopen this issue.

Not quite. This redstone lamp shouldn't be powered.

That would be a separate bug, redstone powering blocks it should not be powering.

That issue might be related to or another case of MCPE-16892