The Bug:
Cloning pressure plates or buttons whilst they're activated keeps them pressed forever.
Steps to Reproduce:
Place down a command block.
Insert the following command into the command block.
/clone ~ ~ ~ ~ ~1 ~ ~ ~ ~1
Place any pressure plate or any button on top of the command block.
Activate the pressure plate or button.
Observed Behavior:
Cloning pressure plates or buttons whilst they're activated keeps them pressed forever.
Expected Behavior:
Cloning pressure plates or buttons whilst they're activated would not keep them pressed forever.
Linked issues
is duplicated by 5
Attachments
Comments 13
/clone ~ ~ ~ ~ ~1 ~ ~1 ~ ~
in an impulse command block with a button on top doesn't work, but /clone ~ ~ ~ ~1 ~1 ~1 ~2 ~ ~
does. When the button is on the side (command block at ~ ~ ~, button at ~ ~ ~1), /clone ~ ~ ~ ~ ~ ~1 ~1 ~ ~
doesn't work, and /clone ~ ~ ~ ~1 ~ ~2 ~2 ~ ~
does work. Here comes the interesting part: putting the button on the other side (command block still at ~ ~ ~, button at ~ ~ ~-1), /clone ~ ~ ~-1 ~ ~ ~ ~1 ~ ~-1
doesn't work, but increasing the selection in the X direction by only one block, like so: /clone ~ ~ ~-1 ~1 ~ ~ ~2 ~ ~-1
, allows it to function as expected. This leads me to believe this bug is caused by the boundaries of the clone command, but only in the positive X and Z direction. The first test case proved the Y boundary didn't matter, the second established that it wasn't any of the inner blocks, and the third established that it was only the positive boundaries.
This same behavior will also cause command block chains to stop executing when cloned (or in my case when I found out about this, moved). I would request that the original report be edited to reflect that. I think it might affect some redstone devices, but I could not reproduce my results once I realized the bugged button was what was powering things, not the bug itself. It would also be worth testing some tile entities to see how they are affected.
Also, confirmed for 1.9.4.
Can confirm for 20w46a.
I'd like to request ownership of this report since the report has been inactive since October 2018.
Relates to MC-224205.
Confirmed.