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
I contacted Chess.com regarding the Stats API like I mentioned. They got back to me and acknowledged that the stats API does have a bug. It seems to be returning the wrong values entirely. He said the Devs will work on it but he is not sure when they will get to it as they are a bit busy.
Nearly a month now this doesn't work properly, checking them i find only 2 or 3 out of 10 that are correct. Very annoying, check, check, doublecheck! Lot of handwork!
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
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: