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

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Sun, Nov 20, 2016 11:12 PM UTC:

"For example, if I put a move like 15,FFFF070 (-16) then a piece can move from g8 through f7 to e7. If put 15,1070 (+1) then a piece can move from g8 through f7 to... d6. But any other tries with -1 and +16 do nothing. I need help for it."

I agree, for pieces that change direction the definitions are awful. But the latest Fairy-Max version (5.0b) actually improved on that. Rather than having to specify the step change in hexadecimal in the upper bits of the move rights, (which is how it is interally stored) it allows you to simply write the secondary step as an (optional) 3rd element in the move definition. So 17,3,1 would now be a Griffon move, a slide that first steps diagonally (17), and then continues orthogonally (1). Fairy-Max itself then calculates what bits have to be changed to make a 1 from a 17.

The 'Skip Rook' in a sense is also a 'bent slider' like the Griffon, except that the move step does not change direction, but only length. The first step of the slide is that of a Dababbah, then the slide continues with single steps. The description of moves that do this would look like 2,3,1 32,3,16 -2,3,-1 etc. The 'lame Knights' move description would be like 1,43,17 (blockable orthogonally) or 17,43,1 (blockable diagonally).
 

I might equip future versions of Fairy-Max with a compiler for Betza notation, so that the piece definitions can be given in this form. That wouldmake it a lot more user-friendly.


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.