Check out Symmetric Chess, our featured variant for March, 2024.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Tue, May 30, 2023 07:18 AM UTC in reply to hirosi Kano from 04:55 AM:

At the stage of the Design Wizard where you have to define the pieces you have to type the name of the piece, the name of the image, and how you want it to move. You can type anything there, including names with spaces. If you don't type anything in any of those fields, the Diagram will use the default for that item. (Which for the image name is the same as the name, and only well-known piece names have a default move.)

Of course the name you type for the image (or that used by default) should be the name of an existing image file of the correct graphics type, otherwise the piece won't show up in the Diagram when your browser tries to display it. And none of the filenames from the standard piece sets have spaces in their name. So if you specify a name like "asian pawn", you should specify the name of the image you want to use for that (probably 'chinesepawn'). To know which images exist you should look on the page that describes the piece set that you have selected for use in the first step of the Design Wizard. Of course when you are using a piece set that you uploaded yourself, you could have given those images any name you wanted.

This is a bit cumbersome, and this is why I later constructed the Play-Test Applet, which shows you which images are available in the Alfaerie set in the applet itself, often with a name and move specified, so that you can simply drag those to the board instead of first having to define the piece table. It still offers the opportunity to change the name and the move used in the table.

But the Play-Test Applet doesn't offer you the freedom to use other piece sets than Alfaerie, or control the square colors.


Edit Form

Comment on the page Interactive diagrams

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.