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.
Linked issues
Attachments
Comments 11
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.
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.
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.
Okay Thanks, but last night it has made an update and now everything seems normal again maybe it was just an update error.
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.
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
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.