pychess
pychess copied to clipboard
pychess
FICS resume after disconnection
According to the PyChess "About" page, "you can login to FICS ... and resume an unfinished game after being disconnected." This happened to me: PyChess disconnected during a game, and a dialogue box came up offering to reconnect. Upon reconnecting, I discovered that the game had been lost due to the disconnection (although there was plenty of time left on the clock). For future reference, how does one resume a FICS game if PyChess loses the connection to the FICS server?
Update: PyChess 1.0.3 dropped the connection to FICS again today in the middle of a game, and it was immediately registered as a forfeit by disconnection. The log files in the ~/.local/share/pychess/ directory included this yesterday:
20:08:37.954 ('freechess.org', 'raw') INFO: FICSConnection.run: ConnectionResetError(104, 'Connection reset by peer') 20:08:37.954 ('aljoiner', 'raw') INFO: 120 abort 20:08:37.954 ('aljoiner', 'raw') INFO: 121 quit 20:08:37.955 ('aljoiner', 'raw') INFO: 122 abort 20:08:37.955 ('aljoiner', 'raw') INFO: 123 quit 20:08:37.977 Default WARNING: FICS.on_connection_error: ConnectionResetError(104, 'Connection reset by peer') 20:08:37.977 ('aljoiner', 'raw') INFO: 124 abort 20:08:37.978 unknown WARNING: socket.send() raised exception. 20:08:37.978 ('aljoiner', 'raw') INFO: 125 resign 20:08:37.978 unknown WARNING: socket.send() raised exception. 20:09:20.343 Default ERROR: 0 29 27 1 2
The log files included this today:
19:46:09.389 ('freechess.org', 'raw') INFO: FICSConnection.run: ConnectionResetError(104, 'Connection reset by peer') 19:46:09.389 ('aljoiner', 'raw') INFO: 114 abort 19:46:09.390 ('aljoiner', 'raw') INFO: 115 quit 19:46:09.390 ('aljoiner', 'raw') INFO: 116 abort 19:46:09.390 ('aljoiner', 'raw') INFO: 117 quit 19:46:09.409 Default WARNING: FICS.on_connection_error: ConnectionResetError(104, 'Connection reset by peer') 19:46:09.410 ('aljoiner', 'raw') INFO: 118 abort 19:46:09.410 unknown WARNING: socket.send() raised exception. 19:46:09.410 ('aljoiner', 'raw') INFO: 119 resign 19:46:09.410 unknown WARNING: socket.send() raised exception.
I wasn't doing anything except moving pieces during the game.
FICS is slowly dying. I suggest everyone to play on https://lichess.org It offers everything what FICS ever offered, plus endless other features. Not to mention that lichess GUI is lightning years better. It is forever free, open source ad less.
I'm sorry to say, but after I started a new chess variant server https://www.pychess.org I had no time for desktop pychess development.
FICS is slowly dying. I suggest everyone to play on https://lichess.org It offers everything what FICS ever offered, plus endless other features. Not to mention that lichess GUI is lightning years better. It is forever free, open source ad less.
I'm sorry to say, but after I started a new chess variant server https://www.pychess.org I had no time for desktop pychess development.
I have reasons for wanting to play chess on FICS. Are you telling me that PyChess is no longer being maintained and I should look for different software to use as an interface to FICS?
Pychess maintenance is not stopped completely. I accept/merge PRs sent by others and sometimes I fix some bugs myself. But this happens very sporadically. Finally I push out new releases in every year.
May I ask you why don't you want to play on lichess.org instead of FICS? I know one reason only, but I'm curious what is yours :)