"/execute store success" is supposed to store the success count of the following command, so I would expect this command:
/execute store success score @s a as @a run say test… to store 2 in my "a" scoreboard. What actually happens is that 1 gets stored there.
I have tried various configuration and never got any result different from 0 or 1.
Comments 5
No, "result" is a completely different thing! Example: "/execute store result score @s a as @e run scoreboard players add @a b 3" returns 6 if there are two entities. With "success" instead of "result", I would expect 2, but I get 1. And your suggestion doesn't even work for the example given in the report, it still saves 1 in the scoreboard.
This is more of a feature request rather than bug report. Because "success" is just used to store whether the command succeeds (0 or 1), though it's true that there is no way to record the number of affected entities by /execute command now.
This is actually WAI. "execute as" splits the execution and the entire thing after it runs twice. So it either stores 1 into the scoreboard once or does that twice, but those are two independent actions. "execute if" is a special thing that can return more than 1 as its success value, nothing else does that. So this is not a bug, just unintuitive.
Use
resultinstead