You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some CECP interfaces or interfaces pretending to be CECP interfaces do not act as XBoard / (Winboard) in the regard that after new command they do not send "random" command as part of initialization string.
For example, this causes Monchester to play deterministically when running under lichess-bot.
Since this 1.0 branch of undead code is meant as fun scholastic engine, not the boring one to beat with once-discovered winning line(s), it is desirable to have the slight score randomization in effect at all times.
Will add a feature define in FEATURE_FORCE_SCORE_RANDOMIZATION in features.h, ON by default. This feature is actually conflicting with DISABLE_SCORE_RANDOMIZATION compile-time define, so give compile-time error, if they are both set at the same time. Completely removing non-deterministic play compile option is not desired, as deterministic behaviour compiles can be useful for testing purposes.
Problem at lichess was reported by Vambo, who perfected beating Monchester 1.0 at Lichess, in its deterministically preferred Nimzowitsch Defense: Woodchuck Variation
as ome CECP interfaces or interfaces pretending to be CECP interfaces
do not act as XBoard / (Winboard) in the regard that after new command
they do not send "random" command as part of initialization string.
Since this 1.0 branch of undead code is meant as fun scholastic engine,
not the boring one to beat with once-discovered winning line(s), it is
desirable to have the slight score randomization in effect at all times.
Completely removing non-deterministic play compile option was not desired,
as deterministic behaviour compiles can be useful for testing purposes.
Some CECP interfaces or interfaces pretending to be CECP interfaces do not act as XBoard / (Winboard) in the regard that after new command they do not send "random" command as part of initialization string.
For example, this causes Monchester to play deterministically when running under
lichess-bot.Since this 1.0 branch of undead code is meant as fun scholastic engine, not the boring one to beat with once-discovered winning line(s), it is desirable to have the slight score randomization in effect at all times.
Will add a feature define in
FEATURE_FORCE_SCORE_RANDOMIZATIONinfeatures.h, ON by default. This feature is actually conflicting withDISABLE_SCORE_RANDOMIZATIONcompile-time define, so give compile-time error, if they are both set at the same time. Completely removing non-deterministic play compile option is not desired, as deterministic behaviour compiles can be useful for testing purposes.Problem at lichess was reported by Vambo, who perfected beating Monchester 1.0 at Lichess, in its deterministically preferred Nimzowitsch Defense: Woodchuck Variation
The text was updated successfully, but these errors were encountered: