mojira.dev
MCPE-20296

repeated use of /clone command causes redstone to stop updating

I discovered this bug while working with a simple T Flip-flop design which I was using to create a binary counter. When I cloned the circuit, I found it stopped working. Not only that, but some of the redstone, torches, and repeaters stopped updating altogether. I believe this bug is associated repeated cloning of redstone elements. For example, if a redstone which is powered is cloned on top of a redstone which is unpowered, the resulting redstone will no longer update.

To test this theory, I did the following:

  • place a lever next to redstone dust

  • clone the lever and redstone to another location

  • turn the original lever on

  • clone the lever and redstone again in the same location

  • destroy the lever

  • now the redstone is powered, but there is nothing powering it

I hope this is not a duplicate report, I searched the forum and didn't find anything!

Linked issues

Attachments

Comments 3

Confirmed on 1.0.4. The wrong state of redstone dust cannot be fixed by reloading the world. The only way to repair it is to repower it. But it seems this is only a visual glitch: the incorrectly powered redstone isn't actually powered. It doesn't activate any adjacent redstone components.

I can confirm the moderator's ststement with my bug report on using '/setblock' of Redstone ('redstone_wire') with a data value that is non-zero: MCPE-22515

Cleaning up old tickets: This ticket has not been updated recently (~1 year+) so is being closed as Cannot Reproduce. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

Richard Preston

(Unassigned)

63208

Confirmed

Windows

clone, redstone

1.0.4.11, 1.2.8.0

Retrieved