Very simply, the "conditional" setting does nothing when set (i.e. the command block runs as though it was unconditional). This affects impulse and chain blocks.
Linked issues
is duplicated by 5
MC-116368
Conditional Command Block Settings No Longer Work On Shapshot 17w16a
Resolved
MC-116387
The 'Conditional' tag for command blocks no longer works.
Resolved
MC-116396
(17w16a) command block Conditionnel is bug
Resolved
MC-116403
Commands changed after snapshot
Resolved
MC-116426
Chain command blocks running when they shouldn't be
Resolved
relates to 2
Comments 4
Glad this has been reported. I opened my testing world in the newest snapshot, and suddenly chaos ensued because teleports that were supposed to be conditional were running every tick. Definitely a game-breaking bug for mapmakers and command block system designers.
@unknown: MC-116471
Can confirm, have a single player sleeping command block setup, the output from `/testfor @p[score_sleep_min=105]` correctly returns `[19:32:48] Entity '@p[score_sleep_min=105]' cannot be found`, yet the conditional command block feeding from it, always executes. Was working fine with 17w15a.