I'd like to add a little more information to this issue.
The bug seems to occur when many requests are made in a short period of time, even when less than 60 (the expected rate limit) requests were made. For example, a leaderboard project trying to get 50 usernames from their UUID, with fast internet and 0 delays added to the code, causes an unexpected 429 status code.
I'd like to add a little more information to this issue.
The bug seems to occur when many requests are made in a short period of time, even when less than 60 (the expected rate limit) requests were made. For example, a leaderboard project trying to get 50 usernames from their UUID, with fast internet and 0 delays added to the code, causes an unexpected 429 status code.
The second rate limit is similar to this old issue.