Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Example for change of engine option UCI_Chess960 #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

anewerla
Copy link

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.

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant