ELO conflict in match participations
lladdy opened this issue · comments
Turns out the ELO conflict we're seeing isn't unintentional.
starting_elo = models.SmallIntegerField(null=True)
"""The bot's ELO at the time the match started
Note that this isn't necessarily the same as resultant_elo - elo_change."""
This is confusing though. If I can't think of any reason for keeping it this way, I will change this behavior to instead have starting_elo be the ELO value before the result adjustment is applied.
This begs the question of why yatahunt appeared to initially observe the ELO value for their bot reverting randomly when re-loading the rankings page, as detailed here: https://discord.com/channels/430111136822722590/853250973325328384/1159576233416343667
Potentially this is caused by some less critical issue, such as caching.
Possible suggestion:
As per my reply above, change starting_elo to be the ELO value before the result adjustment is applied. Then this can be used to more easily either confirm or rule out an ELO allocation issue.
Update:
There is actually some sort of issue causing ELOs to drift.
The total ELO stays constant though.
This issue has risen in occurrence since the rise in AC api usage (potentially due to micro ladder + more ACs).
No longer urgent to fix before next seasons, as AWS is running as a single container and thus this won't be an issue.