mojira.dev
MC-56298

Command blocks not executing while triggered by a very fast clock

In the setup like in the image (I'm facing east) or in the .schematic the command blocks in the middle row facing east and west aren't executing their command. I tried it at different locations and directions in the world, but nowhere it worked.
Additionally, when triggering these commands in the chat they execute as they should. Otherwise as I tried it with a different command, it also worked as it should. (not /execute but /say)
Also as I looked into MCEdit I noticed that every command block has one tile tick at its position but exactly these six command blocks, which don't execute, don't have one.

If it is a bug in block updates or in commands or the selector I don't know.

The commands are (ordered by ascending x or z coordinate):
facing north:

execute @p[rym=135,ry=161,rxm=-10,rx=15] ~ ~ ~ say ~-1 ~1 ~-2 
execute @p[rym=-198,ry=-163,rxm=-14,rx=21] ~ ~ ~ say ~ ~1 ~-2 
execute @p[rym=-162,ry=-136,rxm=-10,rx=15] ~ ~ ~ say ~1 ~1 ~-2

facing east (not working):

execute @p[rym=-135,ry=-109,rxm=-10,rx=15] ~ ~ ~ say ~2 ~1 ~-1
execute @p[rym=-108,ry=-73,rxm=-14,rx=21] ~ ~ ~ say ~2 ~1 ~
execute @p[rym=-72,ry=-46,rxm=-10,rx=15] ~ ~ ~ say ~2 ~1 ~1

facing south:

execute @p[rym=18,ry=44,rxm=-10,rx=15] ~ ~ ~ say ~-1 ~1 ~2 
execute @p[rym=-18,ry=17,rxm=-14,rx=21] ~ ~ ~ say ~ ~1 ~2 
execute @p[rym=-45,ry=-19,rxm=-10,rx=15] ~ ~ ~ say ~1 ~1 ~2

facing west (not working):

execute @p[rym=108,ry=134,rxm=-10,rx=15] ~ ~ ~ say ~-2 ~1 ~-1
execute @p[rym=72,ry=107,rxm=-14,rx=21] ~ ~ ~ say ~-2 ~1 ~
execute @p[rym=45,ry=71,rxm=-10,rx=15] ~ ~ ~ say ~-2 ~1 ~1

Related issues

Attachments

Comments

migrated
[media][media]
migrated

This issue has been reported already. It has been linked to the original bugreport.
Please search before reporting any bugs, as it's likely that one exists already.

migrated

This has nothing to do with signal strength as in the other bugreport. Here clearly get blocks swapped between a redstone block and stone which should cause a block update, even when it happens 20 times a second.
I'm sorry that I wasn't specific about the clock, but I use a command block based clock (one command block sets all blocks to stone the other in the same tick to redstone blocks, wich triggers all command blocks again for the next tick).

migrated

(Unassigned)

Unconfirmed

clock, command_block, execute

Minecraft 14w21b

Retrieved