All reports
battleoflits_displayed reports
#8374: "ELO reward was nonsymmetric, and inappropriate"
notupdated: This report has been closed automatically because there was no vote/comment on it for a long time
1
What is this report about?
What happened ? Please select from below
Rules: a rule of the game has not been respected
Detailed description
• Which part of the rules was not respected by the BGA adaptation
In a two player game, other than the 100-ELO baseline and lower, the ELO reward and penalty are supposed to be symmetric. In this case, I (the winner) was rewarded 19 points whereas my opponent lost 11.
• Is the rules violation visible on game replay? If yes, at which move number?
Game summary/result, I think.• What is your browser?
Mozilla v5
Report history
6. Oct 2017 7:10 • Marphod • Bug has not been reproduced by delopers yet:
I believe I've seen this at a few other tables, but I do not recall which.
I suspect that this may have to do with winning due to a tiebreaker. I have not confirmed that, but I suspect if there was a true tie, my opponent would have gained around 4 ELO (and I would have lost that much), given I had a higher ELO to start. I further suspect that a normal win would have been a 15 point ELO shift, and somehow we both had the '4' from a tie added to our ELO reward/penalty.
This is, admittedly, supposition.
I suspect that this may have to do with winning due to a tiebreaker. I have not confirmed that, but I suspect if there was a true tie, my opponent would have gained around 4 ELO (and I would have lost that much), given I had a higher ELO to start. I further suspect that a normal win would have been a 15 point ELO shift, and somehow we both had the '4' from a tie added to our ELO reward/penalty.
This is, admittedly, supposition.
22. Feb 2019 11:16 • Sourisdudesert • This report has been closed automatically because there was no vote/comment on it for a long time:
Report closed automatically because it has not been upvoted or commented for a while.
Your bug has probably been fixed already, or was linked to a temporary failure of BGA service.
In any case, when filling a bug report, make sure to have an explicit title linked to the incident (ex: with error message), so other players can recognize it and vote for it.
Your bug has probably been fixed already, or was linked to a temporary failure of BGA service.
In any case, when filling a bug report, make sure to have an explicit title linked to the incident (ex: with error message), so other players can recognize it and vote for it.
Add something to this report
Please add here anything that seems relevant to reproduce this bug or understand your suggestion:
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appears several time? Everytime? Randomly?
- If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
