Repository navigation
v2.2.8
Full Changelog: v2.2.7...v2.2.8
v2.2.8
Fixed: bot played one move behind after a reconnect
After the connection dropped and the game was resumed, the bot could
start reading the engine's answer to the previous search instead of
the current one. Each move then came instantly and was meant for an
older position. Eventually FICS rejected the moves as illegal, and the
bot lost on time.
The bot now keeps track of whether the engine is still searching:
- Before starting a new search, it stops any search still running.
- It discards any leftover engine output, so an old answer can't be
taken for the new one.
If a leftover answer is ever discarded, the log says
discarding a stale engine answer: ….