Check out Janggi (Korean Chess), our featured variant for December, 2024.

Enter Your Reply

The Comment You're Replying To
George Duke wrote on Sat, Aug 29, 2009 03:49 PM UTC:
Planar is correct as new piece-type. Also, as I see it on reflection, Planar is most closely associated with Leaper. Planar is a provisional leaper in the classification index of piece-types. Planar is compound leaper with restriction for intermediacy. Now the introduction (well, Gavin Smith's and couple of others preceded) to them here has no set values for their axes. Let's take just one leg of Jiaoye's qualified leap from c1 to d4, visualizing regular squares that we are used to calling Camel's destination. If any of d2, c3, or a3 are occupied, Jiaoye cannot leap to d4. So we can say Planar is subset of Leaper. Simplified, the Planar unit cannot go some specific place(s) if there is certain specific occupation(s). The intervening piece voids the move. However, Leaper can easily encompass other categories Slider, Rider, and Multi-path if we are very careful of definitions. New thread CBM10 follows this up.

Edit Form

Comment on the page LiQi

Conduct Guidelines
This is a Chess variants website, not a general forum.
Please limit your comments to Chess variants or the operation of this site.
Keep this website a safe space for Chess variant hobbyists of all stripes.
Because we want people to feel comfortable here no matter what their political or religious beliefs might be, we ask you to avoid discussing politics, religion, or other controversial subjects here. No matter how passionately you feel about any of these subjects, just take it someplace else.
Avoid Inflammatory Comments
If you are feeling anger, keep it to yourself until you calm down. Avoid insulting, blaming, or attacking someone you are angry with. Focus criticisms on ideas rather than people, and understand that criticisms of your ideas are not personal attacks and do not justify an inflammatory response.
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.