Computer Chess Club Archives


Search

Terms

Messages

Subject: Extensible Chess Interface (XCI) : updated draft

Author: Michael Yee

Date: 09:45:22 03/14/05


The protocol proposal has been updated to reflect several good
comments/suggestions.

(1) There is now a table of what commands are valid in each state. This makes
the protocol clearer and even look simpler than it did before (at least to me
:). Thanks to Harald for this suggestion.

(2) New commands from GUI to engine : getstartpos, getmovelist, getresult

This enables the protocol to be truly extensible since variants that aren't
officially supported by the GUI can still be supported by letting one engine be
the "referee" or "arbiter". This interesting idea came from Reinhard (also the
source of the move and position formats for officially supported variants
FRC/CRC).

(3) New command from engine to GUI : error

------

Even if people are dead set against introducing a new protocol into the mix, I'm
curious what UCI fans think about some of the extensions. Specifically,

- describing what options mean,
- custom thinking output, and even
- getstartpos, getmovelist, getresult

could be added without too much fuss (while maintaining the core philosophy of a
stateless engine)...

Thanks,
Michael



This page took 0.02 seconds to execute

Last modified: Thu, 15 Apr 21 08:11:13 -0700

Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.