Author: Andrey Popov
Date: 06:12:38 04/03/04
In UCI II protocol specification we can read:
Move format:
------------
The move format is in long algebraic notation.
A nullmove from the Engine to the GUI should be send as 0000.
Examples: e2e4, e7e5, e1g1 (white short castling), e7e8q (for promotion)
In another part of that document we can read:
Here are some strings for the example below:
"setoption name Nullmove value true\n"
"setoption name Selectivity value 3\n"
"setoption name Style value Risky\n"
"setoption name Clear Hash\n"
"setoption name NalimovPath value c:\chess\tb\4;c:\chess\tb\5\n"
Does the "Nullmove" option show that the engine support new 0000 move format?
Or does this option trigger the null muve pruning in the search?
If the second is true, how can GUI know about engine's 0000 support?
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.