Cutechess sends uci commands before sending *uci* command

[JoAnnP38]

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

cutechess-cli 1.3.1 Using Qt version 5.15.2 Running on Windows 10 Version 2009/x86_64

Copyright (C) 2008-2023 Ilari Pihlajisto, Arto Jonsson and contributors This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

How did you run Cute Chess exactly?

Using a .BAT file: @ECHO OFF SET OG_PATH=%PATH% SET PATH=C:\Program Files (x86)\Cute Chess;C:\cygwin64\bin;%PATH% SET CUR_YYYY=%date:~10,4% SET CUR_MM=%date:~4,2% SET CUR_DD=%date:~7,2% SET PGNFILE=elo-gauntlet-%CUR_YYYY%-%CUR_MM%-%CUR_DD%-4015.pgn

cutechess-cli ^ -engine conf=Pedantic_2.0.0 name="Pedantic 2.0.0" ^ -engine conf=Sirius_7.0 name="Sirius 7.0" ^ -each tc=6:00+4 restart=on timemargin=75 -debug ^ -openings file="book-ply8-unifen-Q-0.25-0.40.pgn" format=pgn order=random plies=8 policy=round ^ -resign movecount=6 score=600 twosided=true ^ -games 2 -rounds 25 -repeat 2 -resultformat wide -recover -wait 75 ^ -maxmoves 200 -tb n:/tb/syzygy/3-4-5-6 -tbpieces 6 ^ -ratinginterval 10 -variant standard -concurrency 1 ^ -event elo-gauntlet -pgnout "%PGNFILE%" -site "Clearwater, FL USA" -tournament gauntlet

SET PATH=%OG_PATH%

from Engines.json: { "name":"Sirius_7.0", "command":"n:/chess_engines/Sirius_7.0/sirius-7.0-windows-x86-64-v4.exe", "protocol":"uci", "workingDirectory":"n:/chess_engines/Sirius_7.0", "stderrFile":"c:/chess/errors/sirius_7.0_errors.txt", "initStrings":[ "setoption name Hash value 256" ], "whitepov":false, "ponder":false }

Include the full command-line used to run the application. In case the -conf parameter was used, include the relevant engine configurations from the configuration file.

Expected behavior

Since the Sirius engine won't start accepting UCI commands util after first receiving the uci command, I would have expected uci to be sent first from cutechess-cli.

Describe what you'd like Cute Chess to do differently. Send uci before init strings.

Actual behavior

Indexing opening suite... 9376 >Pedantic 2.0.0(0): setoption name Hash value 256 9377 >Pedantic 2.0.0(0): setoption name Ponder value false 9377 >Pedantic 2.0.0(0): setoption name SyzygyPath value c:/tb/syzygy/3-4-5-6 9378 >Pedantic 2.0.0(0): setoption name Threads value 1 9379 >Pedantic 2.0.0(0): uci 9444 >Sirius 7.0(1): setoption name Hash value 256 9446 >Sirius 7.0(1): uci 9526 <Sirius 7.0(1): Unrecognized mode Terminating process of engine Sirius 7.0(1) 9832 <Pedantic 2.0.0(0): Pedantic 2.0.0 by JoAnn D. Peeler 10369 <Pedantic 2.0.0(0): Fast PEXT available: Yes 10732 <Pedantic 2.0.0(0): id name Pedantic 2.0.0 10737 <Pedantic 2.0.0(0): id author JoAnn D. Peeler 10738 <Pedantic 2.0.0(0): option name Clear Hash type button 10752 <Pedantic 2.0.0(0): option name Contempt type spin default 0 min -50 max 50 10752 <Pedantic 2.0.0(0): option name Hash type spin default 64 min 16 max 1024 10753 <Pedantic 2.0.0(0): option name Move Overhead type spin default 50 min 0 max 1000 10754 <Pedantic 2.0.0(0): option name Ponder type check default false 10754 <Pedantic 2.0.0(0): option name RandomSearch type check default false 10755 <Pedantic 2.0.0(0): option name SyzygyPath type string default 10755 <Pedantic 2.0.0(0): option name SyzygyProbeDepth type spin default 2 min 1 max 95 10756 <Pedantic 2.0.0(0): option name SyzygyProbeRoot type check default true 10767 <Pedantic 2.0.0(0): option name Threads type spin default 1 min 1 max 32 10768 <Pedantic 2.0.0(0): option name UCI_AnalyseMode type check default false 10768 <Pedantic 2.0.0(0): option name UCI_EngineAbout type string default Pedantic 2.0.0 by JoAnn D. Peeler, see https://github.com/JoAnnP38/PedanticRF 10769 <Pedantic 2.0.0(0): uciok 10770 >Pedantic 2.0.0(0): isready 10770 <Pedantic 2.0.0(0): readyok 10771 >Pedantic 2.0.0(0): quit

Player: Pedantic 2.0.0 Player: Sirius 7.0 Warning: Could not initialize player Sirius 7.0: Finished match

What you observed.

Steps to reproduce the behavior

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Screenshots If applicable, add screenshots to help explain your problem.