While testing condition statements within command blocks, I discovered that repeated command block do not transfer their conditional statements DIRECTLY to a repeated command block that is looking for the conditional statement. The first picture failed to execute but the other three pictures worked without any problem. The second and third picture shows that they can get a conditional readout FROM chain and impulse command blocks and the fourth picture shows that repeated command blocks can output conditional readings TO impulse command blocks and chain command blocks (not shown). Also, in the picture, left to right points North.
Linked issues
Attachments
Comments
Skylinerw
Could not reproduce any issues.
I should clarify that command blocks to not pass any statements TO a conditional command block; conditional command blocks do the work. The conditional command block checks behind it when it activates to see if there is a command block physically behind it (not previous in execution) that succeeded in running its command. If so, it may run its command. If not, it cannot.
You will have to go into further detail about what's happening that you're not expecting since we cannot reproduce.
You changed the always active chain command to always active repear, didn't you?
There is a bug (not sure if it was reported yet) that the said chain->repeat command block does nothing until you depower it and repower it
Skylinerw
Aye it's been reported, that would be MC-86846.
Resolving to MC-86846.
The fourth screenshot is WAI.
Other, unable to reproduce. It says "test" for all of them (except the last one)
Try using "Needs redstone" for all of them.