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, Abdul-Rahman Sibahi.

Enter Your Reply

The Comment You're Replying To
George Duke wrote on 2007-09-14 UTC
[Taking exception to Gilman's 'never has a switching property' for a later Comment, let's start with basics:] With also ARS's indulgence, the colour changes get interesting in hexagonal. In squares the categories Slider, Leaper, and Multi-path are descriptive enough that we usually omit a colour-describing trailer. For example, a Dabbabah-Rider is understandably colour-bound. Most of us are content with using 'colourbound' for such as Bishop and Camel too. Easily understood. On the other hand, we hardly bother with 'colour-switching'...except Gilman. Now Knight is 'colour-switching', an informative description, in that each successive move alternates White to Black, and we would like to preserve the quality and integrity of the definitions from squares to hexes. First, in hexes new adjective 'colour-changing' we propose for a (mandatory) move to either of the other 2 colours, as with Glinski-FHC Knight and Falcon both. By their three-colour alternations they can reach every square, a desideratum for design. Please refer to the extended definition of 'colour-changing' in our earlier Comment. The famous problem theme of Knight Tour and Falcon Tour becomes possible when all squares and/or hexes can be reached. Are there 1000 possible Knight tours on these 121 hexes? Are there 10,000 Falcon tours on ARS's 121? We have no idea immediately even an approximation the answer to this topic for research. ['Noncolourbound' also to be taken up separately]

Edit Form

Comment on the page Falcon Hexagonal 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.