If you have a command block, cloning a single command block to the location of the clone command block when you clone the block, the command output will be "No Blocks Cloned". (eg. let's say that a /give @a apple command block is at coordinate: 0, 10, 0, then you have a command block near it, with the command: /clone 0 10 0 0 10 0 ~~~ [0 10 0 being the coordinate of the command block] when you clone the block, the command output of the cloned command block will be "No Blocks Cloned".) Hope that wasn't too confusing!
Linked issues
duplicates 1
Comments 5
It does somewhat.. But my issue is that a command block with the command /give @a apple, when cloned on top of a /clone command block, will have the command output, "no blocks cloned," even though its /give command doesn't correspond to cloning at all.Â
Yeah, I had this same problem. Note that it only occurs when the cmd block being cloned is the same type of cmd block at the clone location, eg. both cmd blocks are Chain.
This does sound like the exact same underlying issue as MCPE-83352: "/clone" reports failure when the destination block matches the source block even if it successfully clones the tile data. That issue is reported fixed in a general way in 1.16.210.57 beta:
Using the '/clone' command to clone a block of the same type is no longer treated as a failed operation (MCPE-83352)
Since the fix is describe a change to the way /clone works for all blocks, I see no reason to keep this report open as a separate issue. Resolving as a duplicate.
Since the block is the same, it will have the exact same properties when it tries to clone, so it will report that 0 blocks changed. It can't change anything if you copy it to the same position. You will also have an error due to clone overlap, you should have to use force and (destroy or replace). But what is the use case? output result (success/fail) is updated straight after the command is run.
The ~ refers to the location of the command runner, so in this case the command block. If you want to copy it to X entity/player, you have to use the /execute command to change the position that the command is "run at". For example, /execute at <selector> run /setblock ~ ~ ~ air
Or you can use "positioned as <selector>", or "positioned X Y Z" or "positioned ~ ~1 ~"
Does MCPE-83352 describe your issue?