[MCPE-21898] Redstone torch is on although it should be off Created: 11/May/17  Updated: 23/Jul/20  Resolved: 23/Jul/20

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 1.1.0.9, 1.0.8.1, 1.1.0.55, 1.1.1.0, 1.1.2.50, 1.1.3.1, 1.2.9.1, 1.2.10.1, 1.7.0.9 Beta
Fix Version/s: None

Type: Bug
Reporter: Florian Oser
Resolution: Incomplete Votes: 5
Labels: redstone, redstone_torch

Attachments: PNG File 2017-05-12 15.02.38.png     JPEG File IMG_0406.JPG     JPEG File IMG_0412.JPG     JPEG File IMG_0413.JPG     JPEG File IMG_0414.JPG     PNG File Screenshot_2017-05-01-22-04-30.png     PNG File Screenshot_2017-05-13-11-54-00.png     PNG File Screenshot_2017-05-13-17-04-34.png     PNG File Screenshot_2017-05-13-17-04-54.png     PNG File Screenshot_2017-05-13-17-04-54.png    
Issue Links:
Relates
relates to MCPE-16892 Redstone powers the wrong blocks when... Open
relates to MCPE-11353 Redstone dot doesn't power blocks on ... Resolved
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-16170 Observers powering redstone dust belo... Resolved
relates to MCPE-16831 Redstone comparators do not test for ... Resolved
Confirmation Status: Confirmed
Platform: Phone - Android - Samsung Galaxy S5
CHK:
ADO: 70685

 Description   

Hello, if I build a Redstone mechanism in single game mode, I have the problem that some Redstonetorchs and Redstonelines are on although they should be blocked by another, as soon as I exchanged the broken things they work so long until I restart the app. Here is a picture of the bug.



 Comments   
Comment by [Mojang] Mega_Spud (Jay Wells) [ 23/Jul/20 ]

Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.

Quick Links:
πŸ““ Issue Guidelines – πŸ’¬ Mojang Support – πŸ“§ Suggestions – πŸ“– Minecraft Wiki

Comment by [Mod] GoldenHelmet [ 22/Apr/20 ]

Is this a still a problem in the latest version?

From the pictures, it looks like the burnout setup and steps provided by Pho in the comment above are not what the OP was experiencing. The most recent pictures make clear that the problem occurred in a single chunk, because you can count exactly 16 rows of blocks where the dust is not deactivating the torches. My guess is that this was a chunk loading bug that de-linked the redstone dust from the block below it, somewhat similar toΒ MCPE-48054 but not isolated to chunk borders.

Comment by Florian Oser [ 13/May/17 ]


Suddenly the error is returned: - /: - /

Comment by Florian Oser [ 13/May/17 ]

Comment by Florian Oser [ 13/May/17 ]

Okay Thanks, but last night it has made an update and now everything seems normal again maybe it was just an update error.

Comment by PHO [ 13/May/17 ]

I think I managed to find a way to reproduce it reliably.

Steps to reproduce:
1.
2.
3.

What I expected to happen:
Redstone torches should be turned off because the center block is powered by an active repeater.

What actually happens:
Torches are permanently turned on. For some reason, in this setup you need those blocks on torches and redstone dust on the center block to trigger the bug, forming an inactivated fast torch clock.

Comment by Florian Oser [ 12/May/17 ]

As can be seen here in the picture are 2 torches off (blue edge) and 3 torches on (red edge) and that although they are all switched over the same Redstoneline, as soon as I exchanged the 3 torches they function again.

Comment by Florian Oser [ 12/May/17 ]

Yes the problem is only when I go out and then again and that synonymous not always and with all Redstonetorchs, but only with some.

Comment by PHO [ 12/May/17 ]

Like this?

For me it's working perfectly though. 1.0.8 / iOS.

Comment by Florian Oser [ 11/May/17 ]

Ok the simplest example would be an and-gate, since the output (Redstonetorch) should be only if both inputs are off, with me are both on and the output also. Thus, the circuit can not work. I hope I can explain my problem.

Comment by PHO [ 11/May/17 ]

Could you please provide us a minimal setup of a circuit that exhibits the problem?
It's almost impossible to reproduce the bug solely with your screenshot alone.

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