right now. if we want to manipulate scores, we have /scoreboard players add remove, set, or operation, but the main problem i see is that whatever we can do with /scoreboard (add|remove|set), we can do with /scoreboard players operation. the only justification i can give to /scoreboard (add|remove|set) is that they do not require fake player names that serve as "constants", but this means that the need for fake players is fairly inconsistent. to solve this problem, I think a reorganization of the syntax is necessary to simplify mathematical operations using /scoreboard as a whole.
new syntax, changes highlighted in bold:
/scoreboard players operation <targets> <targetObjective> <operation> (score|value)
... score <source> <sourceObjective>
... value <value>
in short, if the new parameter is set to "score", the command will act as it did before, requiring a source objective to be used. if the new parameter is set to "value", the command will use a fixed value as defined by the player, instead of using the value of a scoreboard. if the >< operator is used, the command would automatically request a source score.
with this, the need for (set|add|remove) is, well, removed. condensing it down into a single subcommand. and while it shouldn't outright remove the ability to use fake players, it provides a straightforward alternative that allows users to directly define it in the command itself instead.
Please sign in to leave a comment.
0 Comments