I was looking through player timeout ratios and I see some incorrect results for a few players:
Example: https://www.chess.com/games/archive/cryonicity?gameOwner=other_game&gameTypes%5B0%5D=chess960&gameTypes%5B1%5D=daily&gameType=daily&page=1
Notice their last timeout was in 2023.
Now hit the stats endpoint and you'll see it shows they have an 85% timeout ratio: https://api.chess.com/pub/player/cryonicity/stats
"chess_daily": {
"last": {
"rating": 869,
"date": 1721090624,
"rd": 125
},
"best": {
"rating": 1301,
"date": 1434908697,
"game": "https://www.chess.com/game/daily/61992096"
},
"record": {
"win": 113,
"loss": 178,
"draw": 1,
"time_per_move": 48498,
"timeout_percent": 85
}
},
This is extremely inconvenient for teams that reply on the API returning accurate information.
Is this a bug with the API or did something change with the response recently? If this is a bug, please prioritize this as it's causing a massive headache for people.
I reviewed the docs and see it should be the last 90 days still:
"timeout_percent": 9.99 // timeout percentage in the last 90 days