[MCPE-20296] repeated use of /clone command causes redstone to stop updating Created: 11/Mar/17 Updated: 03/Jun/19 Resolved: 03/Jun/19 |
|
| Status: | Resolved |
| Project: | Minecraft (Bedrock codebase) |
| Component/s: | None |
| Affects Version/s: | 1.0.4.11, 1.2.8.0 |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Richard Preston | ||
| Resolution: | Cannot Reproduce | Votes: | 2 |
| Labels: | clone, redstone | ||
| Attachments: |
|
||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Confirmation Status: | Confirmed | ||||||||||||||||||||||||||||
| Platform: | Windows | ||||||||||||||||||||||||||||
| CHK: | |||||||||||||||||||||||||||||
| ADO: | 63208 | ||||||||||||||||||||||||||||
| Description |
|
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:
I hope this is not a duplicate report, I searched the forum and didn't find anything! |
| Comments |
| Comment by [Mojang] Mega_Spud (Jay Wells) [ 03/Jun/19 ] |
|
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: |
| Comment by Katie Heart [ 16/Jun/17 ] |
|
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 |
| Comment by PHO [ 13/Mar/17 ] |
|
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. |