When a command block is created, it seems to be unable to execute its command at first.
How to reproduce:
Put a command block, and type this command:
setblock ~ ~ ~2 137 1 replace {Command:"say Hi!"}. When activated, this will create a new command block with a command "say Hi!". Put a repeater between them, facing the second block. Put a button on the first one, and press it. You will see the repeater getting powered (and the second block created if you broke it), but there will be no "Hi!" in chat.
If you set first block's command to something else, second block will not be replaced just before powering, and will execute its command normally. Also, making 2 blocks wide gap instead of one and putting two repeaters between them also solves this issue (even if sum of their delays is smaller than delay of one repeater).
EDIT: whoops, seems that i accidentally wrote "1" in block data, changing to 0 fixes this 🙂
Attachments
Comments
migrated
kumasasa
Confirmed.
This is also a problem in 13w37b
Torabi
Probably related to MC-18631.
Still not working
The command block need to be updated to start working.
Set the block
update it
now the command is working
Note:
The clone command with a command block doesnt have this issue
Confirmed for 14w18b.
data of 1 in a commandblock says it's already powered, 0 means unpowered
kumasasa
Resolving this ticket as invalid, but reopening MC-31100 since placing a command block on a restone block won't trigger the command block