Check out Grant Acedrex, our featured variant for April, 2024.

Enter Your Reply

The Comment You're Replying To
Kevin Pacey wrote on Mon, Feb 5 12:37 AM UTC in reply to H. G. Muller from Sun Feb 4 07:57 AM:

@ H.G.:

I made a rules enforcing preset for 12x12 Brawl Chess generated by the Play-Test Applet, apparently not needing to use the custom set, as I followed your advice about altering IDs and/or moves of pieces (in my case to match the labels of the Sac Chess group, Sac Chess: Standard piece set, which uses labels of one character per the 14 piece types).

When I tested the preset (see link below), in Move Mode, the (Omega) Pawns were allowed to move initially up to 3 squares. However, I tested a case where early on in a 'game' I played vs. myself I moved a Black pawn up to d5, then made White pawn do triple step e3-e6. At that point the preset indicated taking en passant to e4 by the Black pawn was allowed - but when I played the move I got a fatal error message.

[edit: I had some other bugs with the preset, but then I realized I fouled up a couple of table entries for the Applet, so I went back and re-did them, and re-did the possibly affected parts of the Applet's 12x12 setup diagram for Brawl Chess, and then generated Game Code for my preset again. After that only the preset's bug with Omega Pawns seems to have remained. edit2: it seems any form of en passant is recognized by the preset as a legal possibility, but then a fatal error message results when it is actually attempted to be played.]:

https://www.chessvariants.com/play/pbm/play.php?game=Brawl+Chess&settings=enf02


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