It is a best practice on BRYTER to not use value referencing when managing calculations but instead add a value node for each step and assemble the score at the end. It does help with ease of debugging and also ensure that whatever path the user follow the score is correct.
For instance, when end users follow the workflow and also sometimes go back and forth to adjust their choices, when building up a score and using reference the score will not reset and instead keep adding calculations on top of the previous ones leading to errors eventually.
Instead use value node and create the sum at the end to make sure that whatever path the end user follows the calculation will be correct.
So no Score = Score + 1
Maybe rather a version in this direction:
Depending on the path input1 = 1 or input1 = 0
And at the end Score = input1 + input2