The Chess Variant Pages
Custom Search

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on 2009-07-10 UTC
I am occasionally still doing some work on Fairy-Max, but I have way too many programming projects. Lately work on Fairy-Max was limitd to making derivatives of it dedicated to a specific variant with unique properties. MaxQi for playing Xiangqi was one result of this (included in the Debian package). Currently I am working on implementing drop moves in Fairy-Max, to make it play Twilight Chess.

The 8-rank restriction is not very easy to lift. The board size is unfortunately very much intertwined with the promotion evaluation code, which uses properties of the specific bit patterns of the rank numbers to derive the bonuses of 64 'centiPawn' for pushing a Pawn from 5th to 6th or 6th to 7th rank. This is a legacy of its micro-Max ancestry, where compctness of the code was the only criterion. So the promotion evaluation would have to be re-written when the number of ranks is different.

Fairy-Max also uses the most-significant bit of the toSquare as a flag to indicate the move is valid, and on boards with more than 8 ranks this bit would be needed for the rank number. I already did solve that in MaxQi, which needs of course more than 8 ranks, with its 9x10 board. Xiangqi has no promotion, of course, so I did not have to deal with that. MaxQi is a bit of an odd-ball version of Fairy-Max, though, because I layed out the board sideways, to facilitate the testing for eye-to-eye Kings. Despite
that it would still be a better starting point for making an 8+ ranks 
Fairy-Max, rotating back the board so that the original fmax.ini files 
can be understood again (this only affects the code for board setup and
translation of input and output moves to square numbers in the interface),
and newle written promotion code can then be added.

Unfortunately micro-Max was not designed for easy code maintenance...

Edit Form

Comment on the page Fairy-Max: an AI for playing user-defined Chess variants page

Quick Markdown Guide

By default, new comments may be entered as Markdown, simple markup syntax designed to be readable and not look like markup. Comments stored as Markdown will be converted to HTML by Parsedown before displaying them. This follows the Github Flavored Markdown Spec with support for Markdown Extra. For a good overview of Markdown in general, check out the Markdown Guide. Here is a quick comparison of some commonly used Markdown with the rendered result:

Top level header: <H1>

Block quote

Second paragraph in block quote

First Paragraph of response. Italics, bold, and bold italics.

Second Paragraph after blank line. Here is some HTML code mixed in with the Markdown, and here is the same <U>HTML code</U> enclosed by backticks.

Secondary Header: <H2>

  • Unordered list item
  • Second unordered list item
  • New unordered list
    • Nested list item

Third Level header <H3>

  1. An ordered list item.
  2. A second ordered list item with the same number.
  3. A third ordered list item.

Alt text for a graphic image

A definition list
A list of terms, each with one or more definitions following it.
An HTML construct using the tags <DL>, <DT> and <DD>.
A term
Its definition after a colon.
A second definition.
A third definition.
Another term following a blank line
The definition of that term.