Daniel Shawul wrote:I wanted a cooler mover notation than g1f3 but did not want to implement SAN. The sub-standard SAN worked for me
and I didn't know it is a violation of the protocol. Does sending "feature san = 0" in the beginning mean that you stick to
the standard notation for the output as well ?
The specs only say that with "san=0" Xboard will send moves to the engine in long algebraic notation. But it's still probably best to use the same format for input and output.
Anyway I will switch to the standard e2e4 notation from the next version onwards.
Thanks, that's good to hear.
Thanks for cutechess-cli. Will it have ICC support? I want to run some games in the background without
my boss noticing
When Cute Chess gets ICC support, then I guess cutechess-cli will get it too. But that's going to take a while. We still have the following tasks to deal with first:
- Implement a human player
- Add graphical widgets for engine output, move list, UCI configuration, etc.
- Add menus and dialogs for stuff that's already implemented in our chesslib, like opening books, time controls, variants, etc.
- Tournament support (Gauntlet, Round Robin, etc.)
- Fix the QProcess problems on Windows
- Better error handling, unit tests, documentation, etc.