Possibly Monchester CECP chatter could be amended so that Arena autodetect for it would function, anyone have idea how Arena does the CECP engine autodetection or what open-source CECP/XBoard engines are definitely and reliably autodetected by Arena?
This is how Monchester acts at startup ('#' prefix is CECP/XBoard commentary that interface should ignore, 'command' is Monchester's user-friendly' prompt that will be switched off after 'xboard' command is received, bold text is command/protocol input given):
If it were to receive 'uci' instead as first input, Monchester behaves as follows:$ ./monchester
# Monchester 1.0-20-g094fcee ~(9325 kN/s)
command : xboard
# received xboard
protover 2
feature myname="Monchester 1.0-20-g094fcee" name=1 setboard=1 ping=1 edit=0 memory=0 usermove=0 analyze=0 colors=0 sigint=0 sigterm=0 done=1
$ ./monchester
# Monchester 1.0-20-g094fcee ~(9287 kN/s)
command : uci
Unrecognized command
command :
For comparison, the Hippocampe that Arena also supposedly does not detect as CECP engine behaves as follows when fed 'xboard' and then 'protover 2', it is completely quiet when fed 'uci' as first input.
$ ./hippocampe
xboard
protover 2
feature myname="Hippocampe 0.4.2.0.2"
feature ping=1
feature sigint=0
feature sigterm=0
feature variants="normal"
feature done=1