Since you’re here...

We hope you will consider supporting us today. We need your support to continue to exist, because good entries are more and more work time. Every reader contribution, however big or small, is so valuable. Support "Chess Engines Diary" even a small amount– and it only takes a minute. Thank you.
============================== My email: jotes@go2.pl



ShakeyBot 1.1.0 - new version chess engine


ShakeyBot is a UCI chess engine written in C++.
It uses hand-crafted evaluation. In local testing against FabChess Version 1.8, a public engine with a listed strength around 2400 Elo, ShakeyBot scored slightly ahead. This is a local estimate, not an official rating-list result.
Author: Daniel John Collins

ShakeyBot 1.1.0 what's new?
Summary
ShakeyBot v1.1.0 is a stronger hand-crafted-evaluation release focused on search stability, tactical pruning safety, transposition-table correctness, and repository cleanup.

This release keeps ShakeyBot as a classical HCE engine. No neural-network evaluation is used (yet).

Strength Estimate
Local match against FabChess Version 1.8 at 10 seconds per 50 moves:

Score of ShakeyBot vs FabChess Version 1.8: 355 - 285 - 106 [0.547]
...      ShakeyBot  playing White: 171 - 142 - 60  [0.539] 373
...      ShakeyBot playing Black: 184 - 143 - 46  [0.555] 373
...      White vs Black: 314 - 326 - 106  [0.492] 746
Elo difference: 32.7 +/- 23.2, LOS: 99.7 %, DrawRatio: 14.2 %
746 of 20000 games finished.
FabChess Version 1.8 is publicly listed around 2400 Elo, so this suggests ShakeyBot is roughly competitive with 2400-class HCE engines under this local setup. This is not an official rating-list result.

Main Changes Since v1.0.0
Search and pruning updates from the recent tuning cycle.
Qsearch now protects immediate recaptures from delta pruning and SEE pruning.
Continuation history and correction history are disabled after negative A/B results.
Transposition-table generation handling was fixed around clear/new-search wrapping.
ProbCut and move-ordering work from the patch stack are included.
README and developer docs were updated for current build/test workflow.
Code comments, formatting, and stale tuning notes were cleaned up.



Comments