Check out Modern Chess, our featured variant for January, 2025.

Enter Your Reply

The Comment You're Replying To
Kevin Pacey wrote on Tue, Nov 14, 2017 04:56 AM UTC:

An idea occured to me how I might make my Phoenix Chess variant idea more palatable, that is by using an alternative setup that I'll diagram below; I'm not sure if I'll have the kings move two or three squares sideways when castling to either side, but I'm inclined to still have them move three squares (if castling kingside, that would put the king where the rook would initially be). [edit: I now think moving the K three squares for queenside castling and moving it two squares for kingside castling may be best, e.g. to give the j-file phoenix more roon in case of kingside castling. P.S. Perhaps moving the K four squares to castle queenside, and moving it 3 squares to castle kingside, is an option, too.] The only problem might be if Game Courier somehow cannot handle this kingside castling possibility during play. This latest setup still has all pawns protected at the start, but would make smoothly developing the minor pieces more possible in a real game, it seems (btw, I did a minor edit on my last post that had diagrams); castling rules would be as for chess [edit: I'll have to think about using an analogous setup optionally in the case of my Hannibal Chess, Lieutenant Chess & perhaps even Frog Chess variant ideas also, but perhaps this could make for too many {test} diagrams or presets. P.S.: I thought about all this a bit, and it seems it's best to keep the rooks on the outer files in the case of these other 3 variants.]:


Edit Form
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.