Well, there is not much difference between UCI and CECP, other than in layout (at least for the things that are not impossible in UCI): UCI wants to have lots of commands on the same line, while in CECP each command has to be on a separate line.abik wrote:Ah, thanks for that clarification. This becomes a bit more like UCI then. It makes sense, as it avoids clock drift between GUI and engine.
Note that the UCI specs also do not require that wtime or btime commands are sent with the go command.
UCI specs wrote:* go
start calculating on the current position set up with the "position" command.
There are a number of commands that can follow this command, all will be sent in the same string.
If one command is not sent its value should be interpreted as it would not influence the search.
...
* wtime <x>
white has x msec left on the clock
* btime <x>
black has x msec left on the clock
...
* movestogo <x>
there are x moves to the next time control,
this will only be sent if x > 0,
if you don't get this and get the wtime and btime it's sudden death
