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 {color:#59afe1}/data get{color} 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 by 9
MC-131812
"/execute if" is totally broken
Resolved
MC-131818
Testforblock Replacement Doesn't Work or Give an Output
Resolved
MC-131861
Repeating Command Blocks don't reset a comparator status
Resolved
MC-131876
Execute if always gives an output!
Resolved
MC-131896
execute if entity @p[distance..3] always returns true on repeating cmd block, despite being out of range.
Resolved
relates to 1
Comments 5
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.
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.