Check out Glinski's Hexagonal Chess, our featured variant for May, 2024.

Enter Your Reply

The Comment You're Replying To
🕸Fergus Duniho wrote on Sun, May 30, 2021 04:30 PM UTC in reply to Aurelian Florea from 08:31 AM:

@Fergus It seems that the infinite loop was caused by the following code:

setelem op .JW + elem .JW op 1; setelem op .jw + elem .jw op 1;

That's two lines of code. In the first line, you are trying to increment #op[".JW"] by one, and in the second, you are trying to increment #op[".jw"] by one.

.jw is the wazir camel piece and I had wanted to to increase the number of them in reserve. Probably the dot is causing trouble. Do you agree?

Yes, it looks like it is causing trouble. In a test I ran, it incremented #op["JW"] and #op["jw"] by one instead of the elements you named. This is probably because the period is now used as a separator between array and element names, and the setelem command now just concatenates the array and element names by putting a period between them, and uses this concatenated name with the function for setting a user variable.

What I would recommend is to follow the instructions I have previously given for replacing piece labels without using aliases, which is in the comments for the Game Courier Developer's Guide. This would give you nice clean piece labels that you can use in your code without running into problems like this.


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