The site has moved to a new server, and there are now some issues to fix. Please report anything needing fixing with a comment to the homepage.



The Chess Variant Pages



This page is written by the game's inventor, Doug Chatham.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on 2022-10-21 UTC

The challenge in making an Interactive Diagram for this variant was to implement the unusual winning condition (marriage). The Diagram already supported winning conditions on a move with the royal piece to a certain area, by letting the user-supplied JavaScript function BadZone() return the value -1 for a move that goes there. (Where a return value 1 simply forbids the move.) This winning condition is a 'delayed one' (like baring), to ensure stepping into check with it can still be punished in the next ply.

I could have the routine test whether a Queen move lands to the friendly King, but then this mechanism should also be made to work for non-royal pieces. Perhaps this is the most flexible solution. But instead I tried to also implement user-defined 'immediate' winning conditions (like King capture), by having BadZone() return -2, and let King-captures-friendly-Queen return this value. (Forbidding friendly capture of all other piece types by returning 1.)

This also causes the one-ply delay required to test whether the Queen move was legal. But it had the side effect that the win can also be pre-empted by capturing the Queen on the next ply. When I thought about it, this seemed actually more logical. If there is no win when the King is killed before the marriage can be consumed, why should not the same be the case when the Queen dies? In view of the prospect of breeding a successor this should certainly be worse!?


Edit Form

Comment on the page Bachelor Chess

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.
Here is some preformatted text.
  This line begins with some indentation.
    This begins with even more indentation.
And this line has no indentation.

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.