If I try to run /variant suicide in Winboard, it again reports that the variant is not known to the engine. Can you recommend how to inject the additional variants feature (preferably without having to compile the code myself) or tell winboard to ignore the variant feature received.
Ah. That is actually not the latest UCI2WB. The UCI_Variant option is a recent invention, which was introduced after the release of WinBoard 4.8.0, which is probably what you have been using.
More recently I released a WinBoard 4.9 beta version that is configured to use UCI2WB 2.3 by default for all UCI engines. It can be found at http://hgm.nubati.net/WinBoard-AA.zip .
hgm wrote:Ah. That is actually not the latest UCI2WB. The UCI_Variant option is a recent invention, which was introduced after the release of WinBoard 4.8.0, which is probably what you have been using.
More recently I released a WinBoard 4.9 beta version that is configured to use UCI2WB 2.3 by default for all UCI engines. It can be found at http://hgm.nubati.net/WinBoard-AA.zip .
Thank you very much for that work! Indeed, now UCI2WB recognizes the variant.
Now I am stuck receiving the command setoption. For debug purposes I let the engine echo every command with a "" in advance and run UCI2WB in debug mode. Apparently the engine is not receiving the consecutive ucinewgame/isready command.
Other than that, checking the Anticrux javascript code, it is only reacting to ucinewgame commands issued after a first isready/readyok sequence; but that seems incorrect; for me I disabled that additional check in the source code.
It seems to me getting the engine run would be getting more cumbersome than I originally expected.
Maybe at some point the author of Anticrux could confirm whether he managed to pass the code through UCI2WB.