Closed jthuermann closed 1 year ago
There are daily limits as well as rate limits for challenges. I think the maximum number of challenges in a day is 400. This corresponds to a matchmaking: challenge_timeout
of 3.6 minutes. Plus, every declined or ignored challenge is followed by another challenge after waiting 1 minute. So it's reasonable that your bot hit that limit after 10 hours. Setting challenge_timeout
to 5 minutes should allow your bot to issue challenges without hitting daily limits.
As of now, I can see a few possible changes to lichess-bot that could alleviate this for all users:
@AttackingOrDefending Thoughts?
The problem with 2 and 3 is that the bot will use matchmaking for some hours (e.g. 10) and then not use it for the rest of the day (14 hours in this example). A way to make sure that the bot always uses matchmaking is to keep a list of timers and if they exceed 100 multiply the minimum time by 5 (also for declined or cancelled challenges), which guarantees a minimum wait time of 5 minutes. When they drop below 90 divide it by 5. We could also add 3 as a fail-safe.
@jthuermann Please try PR #679 and let us know if you still run into rate limiting.
Hey, my new bot wont work anymore. After about 10 hours of matchmaking it returns a JSONDecodeError and the HTML error code 429. I already read #501 and #510 and already incresead the challenge timeout to 2 minutes but even after pausing the bot for some time i still get this error:
This is my matchmaking config: