UCI go command precedence

[KLc]

Suppose I send (for whatever stupid reason) the following UCI go commands (with white to move):

Code: Select all

go movetime 5000 wtime 1000

and

Code: Select all

go wtime 1000 movetime 5000

What’s the thinking time then? I checked and it seems the first time has precedence. However, this is not documented in the protocol and I’m not sure if I observed a general or an exceptional feature.

[Ras]

What’s the thinking time then?

These are contradictory parameters for mutually exclusive game modes, so the engine can follow either of them, whatever it likes.

[KLc]

What’s the thinking time then?

These are contradictory parameters for mutually exclusive game modes, so the engine can follow either of them, whatever it likes.

Thank you! Then it was just due to the parsing of the particular engine I tested I suppose. Good.

[Ras]

Thank you! Then it was just due to the parsing of the particular engine I tested I suppose. Good.

Yeah, my engine will follow the second one because that overwrites the time handling mode suggested by the first one.

[Ferdy]

Suppose I send (for whatever stupid reason) the following UCI go commands (with white to move):

Code: Select all

go movetime 5000 wtime 1000

and

Code: Select all

go wtime 1000 movetime 5000

What’s the thinking time then? I checked and it seems the first time has precedence. However, this is not documented in the protocol and I’m not sure if I observed a general or an exceptional feature.

There is a quote from the specs,

Code: Select all

If one command is not sent its value should be interpreted as it would not influence the search.

Since both are specified, determine the one that is higher and use it.

go movetime 5000 wtime 1000

movetime 5000
That is 5s.

wtime 1000
White has 1s left on the clock.

So select go movetime 5000.