v1.6.6

• Display Ceres splash screen when using Ceres
• Display tbhits in the infobar (only when a tablebase is loaded)
• "Previous sibling" menu item, thanks to @Zenzizenzizenzike

v1.6.5-rc3

• Fix changing behaviour when receiving a "bestmove" due to node limit, if the search position was locked.

v1.6.5-rc2

• Minor improvements to display of M and D when such values are not known.
• Better logging.

As far as I can tell, the engine-comms rewrite seems OK. Let me know if you have any issues, especially if you ever see any "desync" messages.

v1.6.5

No important change from RC 3.

To recap then, v1.6.5 is mostly an internal cleanup of how Nibbler communicates with the engine. There are also some very minor improvements to the GUI, barely worth mentioning.

The engine-comms rewrite seems to be working as far as I can tell, but do let me know of any issues, especially desynchonisation messages.

This version may or may not be more reliable for the upcoming Ceres 0.89.

v1.6.5-rc1

Rewrote the code that communicates with the engine. All being well, this should make it much harder for the engine and Nibbler to end up out-of-sync with each other.

However, this was a substantial change in logic, and one cannot rule out the possiblity of bugs...

If all is well, there should be no noticeable change for the user.

v1.6.4

• Improve behaviour of logfile menu item.
• Remove arrow filtering by U (now using N instead). This works better for Ceres and arguably for Leela as well.

v1.6.3

Fix another issue with Ceres compatiblity where the stated node count for a position would be wrong, causing absurd numbers and all possible arrows to appear.

v1.6.2

Fix a compatibility issue with Ceres (the Leela-ish alternate engine) in locales where decimal numbers use commas.

Note that Ceres must be configured before use in Nibbler (try running Ceres in the console and answering its questions).

Also, for best results with Ceres, note that using an N-based arrow filter (Display menu --> Arrow filter) is strongly recommended.

v1.6.1

When Leela reports that it has spent 0 nodes analysing a move, display its winrate as "?" rather than "50%". Most noticably, this improves the display of losing moves in tablebase positions.

v1.6.0

• Some compatibility improvements for the upcoming Ceres 0.87.
• A clickable halt button when the engine is running normally (thanks to @eahova)