Add uncertainty to player page

[jauggy]

Feature

Removed units produced column (because useless)
Instead added uncertainty column. This is the prematch value.

[L-e-x-o-n]

Can you put this on the left side, after the team column and if possible sort players by rating (after sorting by team)?

[jauggy]

Yeah sure will do. I just realised I could probably add num_matches too. So you know if someone is nooby or not.

[jauggy]

Added also num_matches. This will show the number of matches you played prior to this match (to be consistent with rating and uncertainty which is prematch). This allows players to understand the balance more since new players will be treated special by the balancer. If you have more than 1000 matches it is obfuscated and just shows >1000.

Old matches won't have this value, but I tested by manually adjusting teiserver_game_rating_logs value column e.g.

{"skill": 21.948025791764863, "num_matches": 123, "uncertainty": 5.09997450626287, "rating_value": 16.84805128550199, "skill_change": -1.0064758196425458, "uncertainty_change": -0.06046185070328658, "rating_value_change": -0.9460139689392584}

[L-e-x-o-n]

Added also num_matches. This will show the number of matches you played prior to this match (to be consistent with rating and uncertainty which is prematch). This allows players to understand the balance more since new players will be treated special by the balancer. If you have more than 1000 matches it is obfuscated and just shows >1000.

Old matches won't have this value, but I tested by manually adjusting teiserver_game_rating_logs value column e.g.

{"skill": 21.948025791764863, "num_matches": 123, "uncertainty": 5.09997450626287, "rating_value": 16.84805128550199, "skill_change": -1.0064758196425458, "uncertainty_change": -0.06046185070328658, "rating_value_change": -0.9460139689392584}

What is the reasoning behind obfuscating the number if the user has more than 1000 matches, I think people would still want to know it and I can't think of any disadvantages?

[jauggy]

I'm happy to show the number. Can reuse the normalise function Teifion made which will use "K" when it gets above 1000. He uses this function for the damage values. Will update.

[jauggy]

Updated.

Using Teifion's normalize function it looks like this.

[L-e-x-o-n]

Thanks