-
Bug
-
Resolution: Fixed
-
Minecraft 1.13-pre3
-
Confirmed
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
-
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
-
MC-132054 Target selector ignores "[distance="
- Resolved
-
MC-172825 comparator output doesn't work fine with command blocks
- Resolved
-
MC-176536 SuccessCount has wrong value for "/execute" command
- Resolved
-
MC-206967 Incorrect Command Block Success Count
- Resolved
- relates to
-
MC-123362 SuccessCount of command blocks use the "result" return value of a command instead of "success"
- Resolved