Ok, so if I am using a command block with the clone command. If I use a redstone circuit to activate that command block, when the command block and the circuit is cloned, it preserved the activate state of the redstone. This means that the new command box repeats the command already given. This will keep happening until the clones extend to the horizon/ungenerated chunks.
Replication steps.
1. Create a command box that is activated by a redstone circuit. (Not a button, it works fine with a button).
2. Set the command box to clone it's self and the redstone circuit using relative coordinates.
3. activate the red stone circuit. (I used a button on a block connected to the command block with redstone)
4. Watch as the clones of the circuit go flying off into the horizon.
Comments 5
It's only supposed to copy once. This video shows what happens. https://www.youtube.com/watch?v=9WCc-Ij-c_4
It's only supposed to copy once.
No. You're already describing why it's supposed to copy endlessly:
If I use a redstone circuit to activate that command block, when the command block and the circuit is cloned, it preserved the activate state of the redstone
Active redstoned cloned yields in active redstone.
Still don't see a bug.
The bug can be fixed by simply making it so that the command executes after the block metadata gets set to one. If that is done, then this bug won't occur.
Where is the bug ?