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 Thu, Feb 9, 2023 09:13 PM UTC in reply to A. M. DeWitt from 07:46 PM:

You could increase the cap of instances of one type for trackPieces to four without much trouble.

Well, that is actually not so easy, because then you would have to examine all entries to see which one has to be replaced, as all others could contain valid data for the other pieces. With two I only have to examine the first entry, and if the piece is not there it must be in the second.

If pieces were numbered, rather than piece types, life would be easier. The piece encoding could consist of a color bit, a virgin bit, a number of bits for types (now 7, to allow 511 types, which is perhaps a bit generous), and 2 bits for an instance number. Then the type could still be examined by masking out the type bits, but type+color+instance number could be used to index the location[] array, where each instance would then have its private entry, which would be adapted when that instance moves. The spell-zone marking would then have to loop through all 4 instances, and check if the colored type is indeed in the recorded location (since we don't track capture), and mark its spell zone if it is.

The problem is that I use many of the bits in the board[y][x] elements to indicate markers; the old move-entry system used that to know whether a destination click would have to trigger a castling or e.p. move, or whether it was a locust square. So I would have to be careful not to collide with these bits.

The work-around of defining two (identical) types of Chariot Soldiers, promoting to two (identical) types of Tertarchs is an extremely simple one, though. It would only require that both types will get their spell zone marked. I could add a parameter trackedTypes=M for that, which in combination with trackPieces=N would put spell zones around type N to type N+M-1. And leave it to the user to make sure there are never more than two instances of each sub-type. That would only require me to put the spell-zone-marking code I have now in a loop (with M iterations) over these piece types.

 


Edit Form

Comment on the page Interactive diagrams

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.