Comparators from command blocks no longer output results properly
Using /execute if entity @e or /execute unless entity @e without "run" subcommands (which is a replacement for testfor commands) no longer gives off an output relative to result and will be successful in command blocks regardless of result.
Has the same issue for /execute if:unless block
Commands such as /data get no longer have the practical output of "result" using comparators.
Commands such as /scoreboard players get no longer have the practical output of "result" using comparators.
Additionally, using comparators with things like /difficulty and /scoreboard players get no longer gives an output of "result", which was useful with doing complex calculations and computing using command blocks and comparators.
Linked Issues
is duplicated by9
MC-131812"/execute if" is totally brokenDuplicateMC-131818Testforblock Replacement Doesn't Work or Give an OutputDuplicateMC-131861Repeating Command Blocks don't reset a comparator statusDuplicateMC-131876Execute if always gives an output!DuplicateMC-131896execute if entity @p[distance..3] always returns true on repeating cmd block, despite being out of range.DuplicateMC-132054Target selector ignores "[distance="DuplicateMC-172825comparator output doesn't work fine with command blocksDuplicateMC-176536SuccessCount has wrong value for "/execute" commandDuplicateMC-206967Incorrect Command Block Success CountDuplicate
Created Issue:
Repeaters from command blocks no longer output results properly.
Using /execute if entity @e or /execute unless entity @e without "run" subcommands (which is a replacement for testfor commands) no longer gives off an output relative to result and will be successful in command blocks regardless of result.
Has the same issue for /execute if:unless block
Additionally, using comparators with things like /difficulty and /scoreboard players get no longer gives an output of "result", which was useful with doing complex calculations and computing using command blocks and comparators.
Repeaters from command blocks no longer output results properly.Comparators from command blocks no longer output results properly.
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
is duplicated by
relates to
Using /execute if entity @e or /execute unless entity @e without "run" subcommands (which is a replacement for testfor commands) no longer gives off an output relative to result and will be successful in command blocks regardless of result.
Has the same issue for /execute if:unless block
Additionally, using comparators with things like /difficulty and /scoreboard players get no longer gives an output of "result", which was useful with doing complex calculations and computing using command blocks andcomparators.Using /execute if entity @e or /execute unless entity @e without "run" subcommands (which is a replacement for testfor commands) no longer gives off an output relative to result and will be successful in command blocks regardless of result.
Has the same issue for /execute if:unless block
Commands such as /data get no longer have practical output using comparators.
Commands such as /scoreboard players get no longer have a practical output using comparators.
Additionally, using comparators with things like /difficulty and /scoreboard players get no longer gives an output of "result", which was useful with doing complex calculations and computing using command blocks and comparators.
Using /execute if entity @e or /execute unless entity @e without "run" subcommands (which is a replacement for testfor commands) no longer gives off an output relative to result and will be successful in command blocks regardless of result.
Has the same issue for /execute if:unless block
Commands such as /data get no longer have practical output using comparators.
Commands such as /scoreboard players get no longer have
apractical output using comparators.Additionally, using comparators with things like /difficulty and /scoreboard players get no longer gives an output of "result", which was useful with doing complex calculations and computing using command blocks and comparators.
Using /execute if entity @e or /execute unless entity @e without "run" subcommands (which is a replacement for testfor commands) no longer gives off an output relative to result and will be successful in command blocks regardless of result.
Has the same issue for /execute if:unless block
Commands such as /data get no longer have the practical output of "result" using comparators.
Commands such as /scoreboard players get no longer have the practical output of "result" using comparators.
Additionally, using comparators with things like /difficulty and /scoreboard players get no longer gives an output of "result", which was useful with doing complex calculations and computing using command blocks and comparators.
Using /execute if entity @e or /execute unless entity @e without "run" subcommands (which is a replacement for testfor commands) no longer gives off an output relative to result and will be successful in command blocks regardless of result.
Has the same issue for /execute if:unless block
Commands such as /data get no longer have the practical output of "result" using comparators.
Commands such as /scoreboard players get no longer have the practical output of "result" using comparators.
Additionally, using comparators with things like /difficulty and /scoreboard players get no longer gives an output of "result", which was useful with doing complex calculations and computing using command blocks and comparators.
Using /execute if entity @e or /execute unless entity @e without "run" subcommands (which is a replacement for testfor commands) no longer gives off an output relative to result and will be successful in command blocks regardless of result.
Has the same issue for /execute if:unless block
Commands such as /data get no longer have the practical output of "result" using comparators.
Commands such as /scoreboard players get no longer have the practical output of "result" using comparators.
Additionally, using comparators with things like /difficulty and /scoreboard players get no longer gives an output of "result", which was useful with doing complex calculations and computing using command blocks and comparators.
Using /execute if entity @e or /execute unless entity @e without "run" subcommands (which is a replacement for testfor commands) no longer gives off an output relative to result and will be successful in command blocks regardless of result.
Has the same issue for /execute if:unless block
Commands such as /data get no longer have the practical output of "result" using comparators.
Commands such as /scoreboard players get no longer have the practical output of "result" using comparators.
Additionally, using comparators with things like /difficulty and /scoreboard players get no longer gives an output of "result", which was useful with doing complex calculations and computing using command blocks and comparators.
Using /execute if entity @e or /execute unless entity @e without "run" subcommands (which is a replacement for testfor commands) no longer gives off an output relative to result and will be successful in command blocks regardless of result.
Has the same issue for /execute if:unless block
Commands such as /data get no longer have the practical output of "result" using comparators.
Commands such as /scoreboard players get no longer have the practical output of "result" using comparators.
Additionally, using comparators with things like /difficulty and /scoreboard players get no longer gives an output of "result", which was useful with doing complex calculations and computing using command blocks and comparators.
Comparators from command blocks no longer output results properly.
is duplicated by
![[Mod] Skylinerw](../../../data/assets/gravatar/skylinerw.png){kind=small}
relates to
is duplicated by
relates to
is duplicated by
is duplicated by
![[Mojang] Bartosz Bok](../../../data/avatars/users/10122.svg){kind=small}
[Mojang] Bartosz BokUsing /execute if entity @e or /execute unless entity @e without "run" subcommands (which is a replacement for testfor commands) no longer gives off an output relative to result and will be successful in command blocks regardless of result.
Has the same issue for /execute if:unless block
Commands such as /data get no longer have the practical output of "result" using comparators.
Commands such as /scoreboard players get no longer have the practical output of "result" using comparators.
Additionally, using comparators with things like /difficulty and /scoreboard players get no longer gives an output of "result", which was useful with doing complex calculations and computing using command blocks and comparators.
Using /execute if entity @e or /execute unless entity @e without "run" subcommands (which is a replacement for testfor commands) no longer gives off an output relative to result and will be successful in command blocks regardless of result.
Has the same issue for /execute if:unless block
Commands such as /data get no longer have the practical output of "result" using comparators.
Commands such as /scoreboard players get no longer have the practical output of "result" using comparators.
Additionally, using comparators with things like /difficulty and /scoreboard players get no longer gives an output of "result", which was useful with doing complex calculations and computing using command blocks and comparators.
is duplicated by
![[Mod] tryashtar](../../../data/avatars/users/41963.png){kind=small}
is duplicated by
is duplicated by
As a side note I must say that command blocks are INCREDIBLY less useful now as you can use result for so many more things then success. Like doing complex calculations using comparators or having a redstone output on a command block equal to difficulty or a scoreboard. They also just don't act as expected.
Suggested fix:
Add "ResultCount:" nbt for command blocks and have comparators pull output values from "ResultCount:" instead of "SuccessCount:".
Relates to
MC-131818.Secondary suggested fix:
Add a gui button to command blocks to allow players to toggle between "result" and "success" as the output for "SuccessCount"
After discussion inside team, we decided to keep success count as comparator output (i.e. 1.12 behavior) - there seems to be no significant loss in functionality, since all arithmetic or logic operations can still be performed with scoreboards only.
On the other hand, `/execute if|unless` will fail where it previously returned 0. It will restore previous conditional triggering behavior.