Releases: rooklift/nibbler
v2.1.5
v2.1.4
v2.1.3
- If multiple engines are known, you can now quickly switch between them with
Engine --> Choose known engine...
(without going through a tedious file dialog).
v2.1.2
- Engine related options will now be stored for each engine individually.
- Support setting the EvalFile option for Stockfish.
- Fix parsing of some PGN files (thanks to @flori for discussion).
- Unified paste FEN and paste PGN commands (thanks to @krisan, this was in 2.1.0 but I neglected to mention it).
Engine options are now stored in a new file, engines.json
. If you had previously added special engine options manually (i.e. with a text editor) your old options will be stored in config.json
so you can migrate them.
v2.1.0
v2.1.0-rc1
Big improvements around large PGN file handling, viz:
- The loading process is about 100 times faster (really).
- The loading process no longer totally takes over the application.
- When over 100 games are present in the file, we no longer try to show them all at once.
This is such an improvement I'll call it 2.1.0. But there were big internal changes in the code to accomodate this, so I'll call it RC1. Please report any bugs, here or on the Leela Discord.
v2.0.2
v2.0.1
v2.0.0
Version 2.0.0 marks the completion of the effort to make Stockfish (and similar engines) work reasonably well.
We've come a long way since 1.0.0, when Nibbler needed to be manually configured with a text file...
Since then, we've gained - inter alia - Chess960 support, end-of-game detection, a legal moves display and movegen code, PGN and FEN compatibility improvements, a winrate graph, play versus engine and engine self-play, better engine configuration, full-game evaluation, custom pieces and custom backgrounds, various aesthetic improvements, a compliant UCI implementation, bugfixes, bugs, bugfixes, and finally Stockfish and A/B engine support.
P.S. Since many people complained - focus buttons are again (by default) shown when the engine is running.
v2.0.0-rc3
By popular demand:
- An option to always show the searchmoves buttons.
- An option to allow the app to stay in "analysis" mode even after a node limit is reached.
These both make certain aspects of the GUI unintuitive, so they are hidden away in Dev --> Non-recommended options
. But they should not cause actual bugs, I hope.