A command block (impulse, unconditional, redstone required) which clones (move) itself, an attached powered block (or redstone wire) and a repeater powering the block (or wire) retriggers immediately after cloning, disappearing into the far distance rapidly.
To reproduce:
Place on top of solid blocks (east to west) a command block, any solid block or redstone wire, and a repeater facing east.
Enter the following command into the block:
clone ~-2 ~ ~ ~ ~ ~ ~-1 ~ ~ replace move
Set the command block to impluse, unconditional, redstone required.
Place a redstone torch or other power source in the block immediately west of the repeater.
Expected: The command block, solid block (or wire) and repeater move one block east and stop, being no longer powered.
Observed: the three blocks move rapidly into the distance as the command block is retriggered after each move.
EDIT:
If the assembly is not on a flat plane it will stop when the repeater no longer has a block beneath it.
This implies that it is the state of the cloned repeater that causes the problem.
Replacing the repeater with a button results in a cloned button which is locked in the powered state. In this button-powered setup change the command to
clone ~-2 ~ ~ ~-1 ~ ~ ~-2 ~1 ~ replace
In this case pressing the button results in the button and the block to which it is attached being cloned one place upwards, but the cloned button is locked in the powered state and cannot be pressed.
Further testing shows that cloned pressure plates also remain powered indefinitely.
Linked issues
relates to 1
Attachments
Comments 10
In the above setup, replace the repeater with a button which can power the solid block.
On pressing the button the command block, solid block and button move one place East and stop, but the button remains powered and cannot be pressed again. This does not explain the re-triggering in the first case but may provide a clue to the cause.
Duplicate of MC-48373.
In the setup shown in screenshot 2016-05-21_09.48.40.png the command block was configured to clone the 18 blocks including the stone block and the buttons attached to the top,East,West,North and South faces.
Pressing the buttons on the West or North faces produced a duplicated assembly with the corresponding button permanently pressed. Pressing any other button produced a duplicated assembly with the corresponding button pressed, but it released after a time-out.
Three further tests: In each case a command block is configured to setblock the space above it to sandstone. It chains to another command block which clones the 3x3 space immediately above it (the first command block and everything horizontally adjacent) to a destination four blocks to the right.
In 2016-05-27_10.43.42.png this includes the repeater that triggered the first command block, but not the slab it is sitting on. The cloned repeater triggers the cloned command block before dropping.
In 2016-05-27_10.44.51.png the repeater has been replaced by a comparator. In this case the cloned command block is not triggered.
In 2016-05-27_10.46.02.png the top command block is triggered by an East-facing button attached to it. In this case the cloned command block is not triggered, but the cloned button remains permanently pressed.
In 2016-05-27_11.11.23.png the top command block was triggered by a button placed on top (as shown this has been replaced by the setblock command). It was surrounded by dispensers each containing a different colour wool block. After cloning the two dispensers on the -X and -Z side were triggered. Those on the +X and +Z side and the cloned command block were not triggered. This may be something to do with the order in which the cloned blocks are updated after cloning.
Is this still an issue in the latest snapshot 16w44a? If so please update the affected versions.
This is an automated comment on any open or reopened issue with out-of-date affected versions.
WARNING: On a multi-player server this can crash the server, as the world grows out of control.