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

Enter Your Reply

The Comment You're Replying To
Jose Carrillo wrote on Sat, Mar 22, 2008 03:34 PM UTC:
I'm working on the code for two new presets for Chess Courier for randomized variants for Modern Chess:

Modern Random Chess and Modern Fischer Random Chess

I'm trying to reuse some of the code already done for Fischer Random Chess, and found a statement that is too specific in the fischer.txt include file, that prevents this include file to be general enough to be used for 9x9 variants.

In the subroutine to evaluate actual moves by the Black Rook, in the elseif statement there is a reference to a physical coordinate (f8), rather than to a label (#roo):

sub r from to;
  set legal fn R #from #to;
  if not var legal or == old k:
    if == #to #rooo:
      castle #k #kooo #from #rooo;
      set k #kooo;
    elseif == #to f8:
      castle #k #koo #from #roo;
      set k #koo;
    endif;
  endif;
  unsetflag #from;
endsub;

The same is not the case for the subroutine for evaluating actual moves by the White Rook:

sub R from to;
  set legal fn R #from #to;
  if not var legal or == old K:
    if == #to #ROOO:
      castle #K #KOOO #from #ROOO;
      set K #KOOO;
    elseif == #to #ROO:
      castle #K #KOO #from #ROO;
      set K #KOO;
    endif;
  endif;
  unsetflag #from;
endsub;

Here the elseif has a #ROO label that allows this subroutine to be general enough to work for a 9x9 chess variant.

Can someone update the subroutine for black in fischer.txt to have the label #roo instead of f8?

Second question, how do I upload a new file into the include library?

I'm working on the code for a new modern-adjustment.txt file that will be general enough to provide for my new Bishop Adjustment in the randomized versions I'm working on, as well as for the Bishop Commuting found in the modern.txt include file.

Thanks.

Edit Form

Comment on the page Modern 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.