Author: Reinhard Scharnagl
Date: 01:55:29 06/19/04
Go up one level in this thread
CAPABLANCA RANDOM CHESS This definition of CRC should cover the following goals: a) creating an interesting drosophila for chess programmers b) using Capablancas 10x8 Chess board geometry c) using Capablancas piece set (incl. archbishop and chancellor) d) applying aligned Fischer Random Chess rules e) avoiding conflicts to any claimed patents The CRC rules are: a) creating a starting position (one of 24.000): 1) the queen must be placed upon a dark square 2) the bishops have to be placed upon different colored squares, same rule applies to the implicite bishop pieces: queen and archbishop 3) the king always has to be placed somewhere between the rooks b) describing a method of generating starting positions e.g. by using a dice or random number generator: 1) Archbishop combination rule: the archbishop has to be placed upon a bright square (5x) 2) Capablanca tradition rule: the queen has to be placed upon a dark square (5x) 3) the first bishop has to be placed upon a free bright square (4x) 4) the second bishop has to be placed upon a free dark square (4x) 5) the chancellor has to be placed upon one of the remaining 6 free squares (6x) 6) the two knights have to be placed randomly upon the remaining 5 free places (10x), to what already a well defined FRC distribution (0 to 9) matrix exists 7) the remainig three free fields are then to be filled with rook, king and rook in that sequence. 8) this establishes White's first row, the Black side has to be built up symmetrically to this 9) ten pawns placed similar to traditional chess in a row finally complete the initial setting as usual. c) nature of (asymetric Fischer-) castlings: 1) castlings are (like in traditional chess) only valid if neither the affected king or rook has been moved, or there would be a need to jump over any third piece, or the king would be in chess somewhere from his starting position to his target field (both included). 2) the alpha-castling (O-O-O): like in FRC the king will be placed at the c-file (two rows distant from the border), the rook at the d-file. 3) the omega-castling (O-O): like in FRC the king will be placed at the i-file (one row distant from the border), the rook at the h-file. d) performing castlings: within a GUI try to move the king upon the related rook or at least two squares into that direction; manually: 1) move the king outside of the board 2) move the rook to its end position (if need to) 3) move the king to his end position e) extended FEN encoding: 1) the extended FRC-FEN could be used as a base 2) 'a'/'A' are used to identify archbishops 3) 'c'/'C' are used to identify chancellors 4) '9' is used to mark nine empty fields 5) '0' is used to mark ten empty fields 6) if a castling enabled rook is not the most outer one at that side, the letter of his file has to be placed immediately following his castling marker symbol, where 'q'/'Q' are used for the alpha-, 'k'/'K' for omega-side. (Because of the three black fields a1, c1, e1 which are candidates for the queen's starting position, from White's view the left alpha-side is more related to the queen than the right side, according to the naming conventions within traditional chess.) f) notation rules for castling moves: According to UCI convention the castling moves should be written by using both coordinates (source and target field) of the involved king. But there are castlings, where the king does only one or none simple step. In that cases the castling should be distinguishable by appending a 'k', like already practized in promotion moves to make them unique. Overmore an engine should accept O-O or O-O-O (no zeroes), but only use them, when the GUI would demand for such a less precise notation.
This page took 0 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.