The bug
Using /setblock to place an "Always Active" command block (or any of the command block's variants) which already has a command in it will not cause the command to run immediately. If you change the command block so that it needs redstone and then back to the "Always Active" state, the command will run as expected.
What I expected to happen was:
The command block would immediately execute the command, as it had done in prior versions.
What actually happened was:
The command block did not immediately execute the command.
How to reproduce
Set a repeating command block (make sure cheats are enabled) with
/setblock ~ ~ ~1 repeating_command_block{auto:1,Command:"say Success!"}-> ❌ The command isn't run immediately
Linked issues
is duplicated by 1
Comments 2
MC-135379 is a duplicate and this bug has been fixed in 18w31a.
At first glance, this may look like a duplicate of MC-31100. However, please take the following into consideration before closing this:
This issue started occurring in this snapshot, 18w30b.
MC-31100 says that the affected block(s) will not respond until they receive a block update; however, setting a command block in prior versions with
would cause the command block to start running the command on its own.
If the mods decide to close this as duplicate anyway please give me a detailed reason why - it may sound like I'm asking for a lot, but it would mean so much to me. Thanks!