I'm looking for some support and/or some insight from the Web Team with regards to recent changes to accessing the Lite Hiscores; these changes seem to be more with regards to what stands in front of the Lite Hiscores.
For those who might not be familiar with the Lite Hiscores, they are the resource that most community resources (fansites, tracking sites, discord bots, and so on) use to access player hiscores data in a more machine-readable format. Each line represents a line on the hiscores, giving the rank, level and experience the player has in that skill.
My clan hosts a skilling competition tracker which I developed which utilizes the RuneScape version of this API endpoint in order to update its stats; there typically are anywhere from 1-3 competitions running at once with anywhere from 20-150 players registered, and each competition updates its stats periodically a few times a day, depending on how often a stat update is requested by an accessing clanmate. When fetching stats, it fetches one player at a time, and usually waits a second or two between retrieving a user's stats and requesting the next user's stats to not spam the API endpoint. This setup has worked pretty much flawlessly for the past 4 years that we have been using it....
Until this week.
Starting yesterday, most of our stat updates have been failing, with the hiscores endpoint instead returning the following:
For those who might not be familiar with the Lite Hiscores, they are the resource that most community resources (fansites, tracking sites, discord bots, and so on) use to access player hiscores data in a more machine-readable format. Each line represents a line on the hiscores, giving the rank, level and experience the player has in that skill.
My clan hosts a skilling competition tracker which I developed which utilizes the RuneScape version of this API endpoint in order to update its stats; there typically are anywhere from 1-3 competitions running at once with anywhere from 20-150 players registered, and each competition updates its stats periodically a few times a day, depending on how often a stat update is requested by an accessing clanmate. When fetching stats, it fetches one player at a time, and usually waits a second or two between retrieving a user's stats and requesting the next user's stats to not spam the API endpoint. This setup has worked pretty much flawlessly for the past 4 years that we have been using it....
Until this week.
Starting yesterday, most of our stat updates have been failing, with the hiscores endpoint instead returning the following:
08-Jan-2021 01:37:47
