In the current implementation, every score can only be input as a whole-integer. This means that if there is some probability that there are 2 teams that end up with the exact same score.
To workaround this, we can use the iron grip activity to give the players a decimal amount of score. Instead of entering the total amount of points (which would usually be an integer), we can input the amount of time the team got, and then calculate the score in the backend. This means that we can set the score to a decimal calculated value, which can be used as a tie-breaker to decide who gets to the final.
Zikoat
commented
6 months ago
In the current implementation, every score can only be input as a whole-integer. This means that if there is some probability that there are 2 teams that end up with the exact same score.
To workaround this, we can use the iron grip activity to give the players a decimal amount of score. Instead of entering the total amount of points (which would usually be an integer), we can input the amount of time the team got, and then calculate the score in the backend. This means that we can set the score to a decimal calculated value, which can be used as a tie-breaker to decide who gets to the final.