Scoreboard comparisons should include the ability to use constants as well as make comparisons between two scoreboard objectives. For example, to see if a player's dDiaScore is greater than zero, I currently have to do this:
execute if score @p dDiaScore > dDiaDude dNull run title @p title "v"
(displays v in the middle of the screen if score in dDiaScore is greater than zero)
This works only if the dummy player 'dDiaDude' has its variable dNull set to zero. But this command won't work correctly if something happens some time during the game that sets dDiaDude's score in dNull to something besides zero. To fix that potential problem, I think we should also be able to do this:
execute if score @p dDiaScore > 0 run title @p title "v"
In summary, I think the ability to use constants in scoreboard comparisons should be added to the already implemented ability to perform comparisons between two scoreboard objectives. It would really help to simplify and clarify code in long functions, and also prevent unwanted results if the 'constant' operand is saved in another scoreboard objective instead of being used by itself.
Scoreboard comparisons should include the ability to use constants as well as make comparisons between two scoreboard objectives. For example, to see if a player's dDiaScore is greater than zero, I currently have to do this:
execute if score @p dDiaScore > dDiaDude dNull run title @p title "v"
(displays v in the middle of the screen if score in dDiaScore is greater than zero)
This works only if the dummy player 'dDiaDude' has its variable dNull set to zero. But this command won't work correctly if something happens some time during the game that sets dDiaDude's score in dNull to something besides zero. To fix that potential problem, I think we should also be able to do this:
execute if score @p dDiaScore > 0 run title @p title "v"
In summary, I think the ability to use constants in scoreboard comparisons should be added to the already implemented ability to perform comparisons between two scoreboard objectives. It would really help to simplify and clarify code in long functions, and also prevent unwanted results if the 'constant' operand is saved in another scoreboard objective instead of being used by itself.