You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Handle new error message when challenging bots
Reference issue: lichess-bot-devs#1135
Detect when the rate limiting status code (429) is due to issuing more
than 100 challenges in a day. The change to matchmaking prevents adding
other bots to the block list in case the error is due to this rate
limit.
* Remove tracking of daily challenges
The purpose of tracking daily challenges was to slow down the issuing of
challenges when the rate limit of 400/day was being approached. However,
now that the number of games is limited to 100/day (whether the bot
issues or receives the challenge), this tracking is redundant.
The rate at which challenges are issued is now entirely controlled by
the matchmaking: challenge_timeout configuration, which specifies how
long after a game ends to issue a new challenge.
* Remove unneeded Timer attributes
Now that challenge times aren't recorded, there's no need for backdated
Timers or the recording of when a Timer was created.
* Delete unused type
* Put daily game limit info in user messages
Put the rate-limit timeout into the RateLimitedError exception so other parts of the program can use it.
Add a rate-limit Timer to the Matchmaking class so that the user's logs aren't fill with rate-limited messages. Also, change the format of the "Next challenge will be created after" message to include the date since the delay may last into the next day.
* Put back Matchmaking.min_wait_time
This serves as a general rate limit on challenges and is still useful.
* Undo unneeded parenthesis move
* Handle daily game limit on first failed challenge
Create a function to handle the daily game limit. Update types to
accomodate the response error message.
* Update wiki regarding daily bot game limits
Copy file name to clipboardExpand all lines: wiki/Configure-lichess-bot.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -242,6 +242,9 @@ will precede the `go` command to start thinking with `sd 5`. The other `go_comma
242
242
- `allow_during_games`: Whether to issue new challenges while the bot is already playing games. If true, no more than 10 minutes will pass between matchmaking challenges.
243
243
- `challenge_variant`: The variant for the challenges. If set to `random` a variant from the ones enabled in `challenge.variants` will be chosen at random.
244
244
- `challenge_timeout`: The time (in minutes) the bot has to be idle before it creates a challenge.
245
+
246
+
Bots are limited to playing 100 games against other bots per day, so setting `challenge_timeout` to a small value will result in this limit being reached quickly. There is no limit to the number of games a bot can play against humans.
247
+
245
248
- `challenge_initial_time`: A list of initial times (in seconds and to be chosen at random) for the challenges.
246
249
- `challenge_increment`: A list of increments (in seconds and to be chosen at random) for the challenges.
247
250
- `challenge_days`: A list of number of days for a correspondence challenge (to be chosen at random).
0 commit comments