Check out Atomic Chess, our featured variant for November, 2024.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Tue, Oct 30, 2018 12:26 PM UTC:

I would recommend to forget about the protected-Pawn restrictions in the numbering system. The inconvenience of not having direct mapping formulas between numbers and positions seems much worse than having some numbers that correspond to invalid positions.

Note that WinBoard already allows positions to be entered by number, and that the World probably would not become a better place by having ChessV and WinBoard use incompatible numbering systems.

The WinBoard system is a generalization of the traditional Chess960 numbering, to make that applicable to almost any variant. For each piece type you divide the total number by the number of placements for that type (for determining placement of subsequent pieces), and use the remainder as placement code for the current piece type. If the variant has normal castling rather than Fischer castling, you first place the  King and Rooks (or whatever serves as castling partner) in their normal positions. If the board width is even you then place all pairs of color-bound pieces such that they are on different shade. Then you place all remaining pieces on the still open squares, ignoring square shade. In games with Fischer castling you are then left with 3 opens squares, and occupy them by the King between the castling partners.

Currently the WinBoard implementation has some limitations: numbering is not unique if a certain color-bound type occurs in more than two copies. (As this never happened in any of the supported variants, I did not bother with that case.) Also, the order in which pieces are placed depends on the piece encoding WinBoard happens to use, traversed high to low in order to make sure Q is placed before N. And it only recognizes Bishop, Ferz and Alfil as color bound, placing them in the order A, F, B. (Relevant for 'Courier960'!)

Especially the piece order seems hard to objectively define so it would cover every conceivable variant. I want to propose to derive it from a 'mother position', which for Chess960 obviously would be the FIDE array. The pieces can then be ordered according to where they stand on the baseline in this reference position, e.g. for white from left to right this would lead to the order R, N, B, Q, K. They would then be placed in top-down order: K, Q, B, N, R. But B is color bound and present in multiple copies, so it gets precedence: B, K, Q, N, R. Now in variants with castling K and R drop out (either done first or last, but always in a predetermined way), so the final order is B, Q, N, as in Chess960. For CRC it seems logical to use the Capablanca position as reference (as the name suggests that).

It should be easy to write a universal shuffling routine that takes a given position and a random number, and then shuffles that position according to the number. Unfortunately WinBoard now places the super-pieces in the order C, A, Q, which is not what the Capablanca start position would suggest when traversed from left to right.


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.