Check out Glinski's Hexagonal Chess, our featured variant for May, 2024.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Tue, Nov 22, 2016 06:03 PM UTC:

Ah, I misunderstood your new Pegasus. This explains why the Elves were crushed so badly by the Orcs in my tests with Fairy-Max. (They scored only about 10%). I fixed that now on the web page.

The Wyvern and Hunter were already as you say, however. They cannot be blocked on the square adjacent to them.

What is unclear in your main article is how en-passant capture works with Orkish and Elvish Pawns. You write that all rules arethe same as in orthodox Chess, so that suggests there must also be en-passant capture. But if a Human or Orkish Pawn moves e2e4 while there is an Elvish Pawn on d4, can this Elvish Pawn then capture e4 by moving to e3? Can it move to e3 without capturing e4? Fairy-Max should never e.p.-capture other pieces than Pawns (i.e. the first piece defined for each color). Do you have an example game where this happens? Fairy-Max assumes that a move with capture rights to the e.p. square (i.e. a square where the preceding initial double-push could have been blocked) is an e.p. capture of that last-moved piece. You can define an initial double-push in an alternative way, either as a jump or as a lame move that does not create e.p. rights.


Edit Form

Comment on the page Asymmetric Chess

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