-
Notifications
You must be signed in to change notification settings - Fork 455
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bot gets stuck sometimes at the end of the game #1067
Comments
Please upload the entire log file A separate issue seems to be that your bot refuses to make a move on a game that ended in a draw. I'm guessing this from the log lines
which indicate your engine isn't choosing a move. Just in case we don't find a problem on our end, check that your engine picks a move when given a position that is a threefold repetition or 50-move draw. |
|
Thanks for the logs. I can see the problem now. When your bot's opponent makes a move that triggers a draw condition (threefold or fifty-move), lichess sends two messages in a row like the following:
Notice that the only difference between these messages is the at the far right: The immediate solution is to have your bot play a move despite the draw condition. It doesn't even have to be a legal move-- On our end, we'll think about if this can be fixed within lichess-bot. Currently, we expect that every time |
Describe the bug
Sometimes (not always) at the end of the game, the bot stops creating challenges or accepting challenge requests. When it happens, there is no log entry "INFO won!" and there is no in-game chat of bot saying "GG", it seems the bot doesn't realize the game ended and blocks new games due to max concurrent game constraint.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Bot should always realize the game is over after it is over
Logs
lichess-bot.log:
config.log:
Desktop (please complete the following information):
Additional context
It's very probable the issue is caused by engine misbehaving somehow, but the bot wrapper should hopefully be able to deal with terminating it more sternly.
The text was updated successfully, but these errors were encountered: