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

Enter Your Reply

The Comment You're Replying To
🕸Fergus Duniho wrote on Tue, Aug 1, 2006 01:11 PM UTC:
These are some instructional comments for making a better preset.

1) There is no need to use the * as a file label for files without any
spaces. Additional whitespace is not redundant in the Files field. When
two empty spaces occur side by side, Game Courier reads a null space
between them, and it will use a null file label. This is what I've done
in presets for Shogi and Chessgi.

2) You can use the alias command to avoid the two-character labels being
used for some pieces. It will allow you to use more intuitive one-letter
labels, such as k/K for King, p/P for Pawn, and e/E for Elephant.

3) If you program it to automatically place captured pieces into a certain
area, you can use the * operator to drop pieces from that area. This will
also eliminate the need to display the file labels for the off-board area.
These can be made invisible by preceding each one with a ! in the Files
field. See a Shogi or Chessgi preset for an example.

4) With the Shatranji and Chessgi include files already available, it
shouldn't be too difficult for someone to write a preset that will
enforce the rules of this game. Start with the code from the Shatranji
preset as a template. After including the Shatranji include file, add some
functions for the Dabbabah and Wazir. If you want to use the same images
for Elephant and King as you are now, also add new functions and
subroutines for these pieces. Copy the Elephant functions from
Shatranji.txt, and call them 1e and 1E. It will be a bit easier to just
use the k/K images for the King instead of the sp/SP images. You'll have
to be careful if you decide not to. Add new ATTACKEDBYB and ATTACKEDBYW
functions that cover the piece set used in this game. Modify the
appropriate lines in the Post-Move code to reflect the pieces used in this
game. Use their actual labels here, not their aliases.

Edit Form

Comment on the page Shatranjian Shogi

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.