Universal Chess Interface
In November 2000, the UCI protocol was released. Designed by Rudolf Huber and Stefan Meyer-Kahlen, the author of Shredder, UCI rivals the older "Chess Engine Communication Protocol" introduced with XBoard/WinBoard.
As of 2007[update], well over 100 engines are known to directly support UCI.
By design, UCI assigns some tasks to the user interface (i.e., presentation layer) which have traditionally been handled by the engine (at the business layer) itself.
Most notably, the opening book is usually expected to be handled by the UI, by simply selecting moves to play until it is out of book, and only then starting up the engine for calculation in the resulting position. UCI does not specify any on-disk format for the opening book. Different UIs usually have their own proprietary formats.
While the UI can also take responsibility for handling endgame tablebases, this is arguably better handled in the engine itself, as having tablebase information can be useful for considering possible future positions.
- e1g1 (white short castling)
- e7e8q (for promotion)
The uci_limitstrength parameter tells engines with this feature to play at a lower level. The uci_elo parameter specifies the Elo rating at which the engine will aim to play.
- Universal Shogi Interface (USI), a dialect for shogi;
- Universal Chinese Chess Interface (UCCI), a dialect for xiangqi.
Each of these protocols may also define variants of PGN and FEN. The XBoard CECP is said to require far fewer changes to support variants.
- "Chess engines". Business World Online. 2017-04-06. Retrieved 2018-06-14.
- Torres, JC (2014-06-23). "Lichess embraces blind players with new chess site features". SlashGear. Retrieved 2018-06-14.
- Chess Life. United States Chess Federation. 2003.
- "UCI protocol". wbec-ridderkerk.nl. Retrieved 2018-06-14.
- Evert. "UCI protocol for chess variants". TalkChess.com.
- "The Universal Shogi Interface (USI)". hgm.nubati.net.
- "中国象棋电脑应用规范(五)：中国象棋通用引擎协议". www.xqbase.com.