Example for change of engine option UCI_Chess960 #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Due to a recent issue regarding this engine option in Stockfish I consider the description of the UCI specification unsatisfactory with respect to the engine option UCI_Chess960. In the part "Chess960" it is said that this engine option should be set to true.
To make this immediately clear the command to change this engine option should be explicitly given, i.e. the following text update is proposed:
Whenever a Chess960 game is played, the GUI should set this engine option to 'true':
setoption name UCI_Chess960 value true
I do not see any strong arguments against such update and for me this would be the logic consequence, too, since the related engine message 'option name UCI_Chess960 type check default false' has been mentioned before. Last but not least, it would directly answer any questions how to do it, in particular coming from such users with still limited knowledge of UCI specification.