Negative values could increase the engine priority, which is not recommended.\r
@item -firstOptions string\r
@itemx -secondOptions string\r
-@cindex firstOptions option\r
+@cindex firstOptions, option\r
@cindex secondOptions, option\r
The given string is a comma-separated list of (option name, option value) pairs, \r
like the following example: style=Karpov,blunder rate=0. \r
it would be set to the given value (i.e. Karpov or 0) \r
through a corresponding option command to the engine. \r
This provided that the type of the value (text or numeric) matches as well.\r
+@item -firstNeedsNoncompliantFEN string\r
+@itemx -secondNeedsNoncompliantFEN string\r
+@cindex firstNeedsNoncompliantFEN, option\r
+@cindex secondNeedsNoncompliantFEN, option\r
+The castling rights and e.p. fields of the FEN sent to the mentioned engine \r
+with the setboard command will be replaced by the given string. This can for \r
+instance be used to run engines that do not understand Chess960 FENs in \r
+variant fischerandom, to make them at least understand the opening position, \r
+through setting the string to KQkq -. (Note you also have to give the e.p. field!) \r
+Other possible applications are to provide work-arounds for engines that want to see \r
+castling and e.p. fields in variants that do not have castling or e.p. \r
+(shatranj, courier, xiangqi, shogi) so that WinBoard would normally omit them \r
+(string = - -), or to add variant-specific fields that are not yet supported by WinBoard \r
+(e.g. to indicate the number of checks in 3check).\r
@end table\r
\r
@node UCI + WB Engine Settings\r