Ctrl + Pick on Command block block does not save the conditional state

Probably intended even though it seems pretty annoying. The problem is that the conditional state is no longer saved as NBT tag and so it won't be copied.

And I think it's important that conditionality should be saved only when using Ctrl unlike wool which color is saved regardless of using Ctrl and that makes sense for wool but would be annoying for command blocks.

Can also confirm.

It's like this in 15w37 too.

Still there in 15w38a

The bug is in 15w39b too.

Soooooooooooooooooooooooooooooooooooooooooooooo annoying ;'(

15w42a is still affected.

Affects 15w43a

15w44a confirmed.

Definitely very annoying, I've been working with command blocks and having the condition constantly reset every time I need to move/copy them is a huge pain.

Confirmed for 15w45a

This is because the conditional command blocks are a data value of the block, not a block tag (i.e. command_block data:8 is conditional, but command_block data:0 is not), thus since it is not a tag, you can't pick-block it. This is likely done so that minecraft can apply a different texture to the block. A possible solution would be to split all the conditional blocks into a new block type (i.e. conditional_chain_command_block), which would allow it to be pick-block able.

Edit: Also, realizing that stone DOES pick-block on different data values, command blocks probably don't because then you would be able to pick-block specific directions the block faces, which probably isn't desired. So solution would still be to create a new block type for it. But on second thought, that might break current conditional command blocks placed in the world...perhaps make a special case for pick-block to pick only conditional or unconditional blocks out of all the data values? (like if you pick a cmd with data 0 to 7, you get an unconditional block, but 8 to 15 gets a conditional block)

15w47a

Onnowhere,
CTRL+Pick copies NBT data, not only metadata. If it only copied metadata, then we wouldn't be able to CTRL pick and have a, say, repeat command block that doesnt require redstone. For some reason the condition effect on a command block does not copy with ctrl pick, possibly something to do with the NBT data

It looks like there's no any NBT tag that states the "condition" for a command block (although I really want it to have).

@Dylan, Onnowhere is correct. The conditional setting is not stored in NBT, so the fact of NBT being copied is irrelevant.

@Skylinerw, Exactly what I was pointing out. There is no NBT setting for conditional therefor it does not copy correctly. Maybe I had misread and missed something, if so, I apologize

Confirmed for 15w50a

Confirmed for 15w51b

Confirmed for 16w06a

Confirmed for 1.9-pre1

Confirmed for 1.9-pre2

Same issue 😉

Still a problem in 1.9-pre3.

Still a problem in 1.9-pre4...

Confirmed for 1.9 Release.

This is a block state not an NBT tag. I think this should be added though. Can someone suggest this on the reddit forums?
http://www.reddit.com/r/minecraftsuggestions/

Still in 16w40a

Confirmed for 1.13.1.

Still in 1.14 Pre-Release 5

1.14.3 as well, since it's easier to mark tickets as duplicate than give a try on solving this that makes no sense since 1.9...

Confirmed for 1.15.1

Hello,
Since a lot of version I have this problem ... When I copy a command block with the click wheel and the control key, the command is copied inside, however the “Conditional” option is not saved which is problematic in the following situation.
If I place a chain command block with a teleport command following a reapeting command block, the player is endlessly teleported to the same place, the only solution is to remember the coordinates of the command block to delete it ...
Besides, it would be great to have a gamerule allowing to stop the command blocks as on the servers.

20w06a affected

still in 20w15a

confirmed in 20w17a

Present in 20w18a.

Hi there!

Can confirm for 1.16.1 and 20w28a.

Affects 1.16.1

still in 1.21.2 release-candidate 1