Skip to content

Setting inconsistent engine options for fischerandom #667

@magehrke

Description

@magehrke

Output of cutechess-cli --version / cutechess --version

cutechess-cli 1.2.0
Using Qt version 5.15.2
Running on Ubuntu 18.04.5 LTS/x86_64

How did you run Cute Chess exactly?

Tournament with cli

/.../cutechess/projects/cli/cutechess-cli -variant fischerandom -event Ara-FairySF-rapid -rounds 5  -games 2 
-engine name=MultiAra dir=/.../Cutechess-Tournaments/Engine/ cmd=MultiAra 
-engine name=FairyStockfish dir=/.../Engines/fairy-stockfish/ cmd=fairy-stockfish
-each proto=uci tc=0/10+0.1 -debug

Expected behavior

I expect that cutechess sends:

setoption name UCI_Variant value fischerandom
setoption name UCI_Chess960 value true

Or I expect:

setoption name UCI_Variant value chess
setoption name UCI_Chess960 value true

Actual behavior

setoption name UCI_Variant value chess960

Steps to reproduce the behavior

Open the GUI, select 1 engine, select new game, select fischerandom, observe what cutechess sends to the engine


  • To me this seems inconsistent. I would like that cutechess sends the variant to the engine, that has been set. Also, I think it would be good if the UCI_Chess960 flag would be set in any case.
  • I think it cannot be expected that the engine correctly processes a variant name that the user did not set and the engine might not know.
  • For example fairy-stockfish does not work with cutechess at the moment, which can be seen here Illegal move after opponent castles in chess960 fairy-stockfish/Fairy-Stockfish#318

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions