The "conditional" setting no longer works for command blocks
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 by5
MC-116368Conditional Command Block Settings No Longer Work On Shapshot 17w16aDuplicateMC-116387The 'Conditional' tag for command blocks no longer works.IncompleteMC-116396(17w16a) command block Conditionnel is bug DuplicateMC-116403Commands changed after snapshotDuplicateMC-116426Chain command blocks running when they shouldn't beDuplicate![[Mod] Skylinerw](../../../data/assets/gravatar/skylinerw.png){kind=small}
Created Issue:
The "conditional" setting no longer works for command blocks
Very simply, the "conditional" setting does nothing when set (i.e. the command block runs as though it was unconditional). This affects all types of command blocks.
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
Very simply, the "conditional" setting does nothing when set (i.e. the command block runs as though it was unconditional). This affects
all types of commandblocks.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.
relates to
is duplicated by
is duplicated by
is duplicated by
is duplicated by
![[Mojang] Searge (Michael Stoyke)](../../../data/assets/gravatar/searge.png){kind=small}
[Mojang] Searge (Michael Stoyke)is duplicated by
This should be re-opened, as it's still bugged in 17w16b, though in a slightly different way. The command won't execute until its condition is met, but once that happens, it will execute forever, even after its condition fails again. It's as though it's not resetting its "condition met" flag when the previous command fails, which it should be doing.
relates to
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
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.
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.
For me it still doesn't work properly in 17w16b!
Janik Schumacher:
MC-116471