X-Git-Url: http://winboard.nl/cgi-bin?a=blobdiff_plain;f=data%2Ffmax.ini;h=a68c32893f6868c575c12e17b65e39306064ea8a;hb=1791a18da3fdc051bdc8d1942827fd30a0cc2333;hp=ca697beb5cd8f1f46780458c5854b32b7c6c71aa;hpb=b5f6da5924abac2187d0aac1006c7ebd13eb4e9a;p=fairymax.git

diff --git a/data/fmax.ini b/data/fmax.ini
index ca697be..a68c328 100644
--- a/data/fmax.ini
+++ b/data/fmax.ini
@@ -200,6 +200,13 @@ value assumed for them will be the absolute value of what you defined.
 With a value -1, however, loss of the first piece of that type loses the game.
 For royal piece types larger than 7 there is the special rule that it is not
 allowed to leave more than one of them under attack ('duple check').
+A royal value of -2 is currently used as a kludge to enable an alternative
+winning condition, namely when the royal piece reaches (and survives in)
+one of the four central squares.
+
+NOTE: Any piece value that (in decimal notation) ends in '3' will not be 
+accepted as promotion choice. (And neither will be absolute royalty,
+i.e. piece value -1).
 
 The individual bits in the move-mode descriptor have the following meaning:
 In the last hexadecimal digit: