You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently the scoreboard has stats for points, wins, and canon. However there is nothing about movement. Generally it is assumes that robots the do the most damage to others robots will win but this is not always the case. Movement stats may show why robots are winning when damage inflicted is not the only factor.
Describe the solution you'd like
I propose 3 stats: Total distance moved, Avg distance from other robots (while health > 0). Total number of collisions.
Describe alternatives you've considered
Another option is average speed but this differs by class so it may not be as useful. We could have collision damage rather than Total number of collisions however that again differs by class.
The text was updated successfully, but these errors were encountered:
@JamesDarby345 , let's leave this one now. Also, I think you misunderstood this. We would not do this in the bots. This would be in the server and would appear on the server scoreboard. It's a bit of work to get right.
Is your feature request related to a problem? Please describe.
Currently the scoreboard has stats for points, wins, and canon. However there is nothing about movement. Generally it is assumes that robots the do the most damage to others robots will win but this is not always the case. Movement stats may show why robots are winning when damage inflicted is not the only factor.
Describe the solution you'd like
I propose 3 stats: Total distance moved, Avg distance from other robots (while health > 0). Total number of collisions.
Describe alternatives you've considered
Another option is average speed but this differs by class so it may not be as useful. We could have collision damage rather than Total number of collisions however that again differs by class.
The text was updated successfully, but these errors were encountered: