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

Enter Your Reply

The Comment You're Replying To
Kevin Pacey wrote on Sun, Feb 4 05:47 PM UTC in reply to Fergus Duniho from 04:18 PM:

I may not have the right understanding of en passant in Omega Chess, but I think a Black pawn on e3 should not be able to capture en passant (that is move to f2) after White takes a double step from f2 to f4. En passant for a double step does not work like that in chess after a double step there, and I looked at the Pawn Rules diagrams for Omega Chess' rules page, and nothing exactly like that type of attempted en passant capture is shown there either.

In my 12x12 Brawl Chess, I am allowed to make the analogue of taking a pawn moving by triple step to e5 with a Black pawn on d4 (it is not shown as legal, but it is allowed by the preset). But when I try capturing a pawn making a double step to f4 with a Black pawn on e3, the preset not only does not show the option, but also does not allow it. However, my current enforced version of Brawl Chess may be lacking some sort of code that the current enforced Omega Chess preset has.


Edit Form

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