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 Sat, Dec 19, 2015 07:34 PM UTC:
I added some new automated sets, mainly for use with the Diagram Designer, though they may also be used with Game Courier. As automated sets, they read the contents of a directory, or in one case multiple directories, and populate the $pieces array with all the GIF or PNG images found within the appropriate size range. They can all be found in the Automatic group. They are provided for Abstract, Alfaerie, and Utrecht pieces. Unlike most sets, they do not normally use single letter labels. They base the labels on the file name. For the Abstract and Alfaerie, the initial w or b and the file extension both get chopped off, and the name is put into full uppercase or full lowercase. For the Utrecht pieces, the file extension gets chopped off for the label. To use pieces from these sets, you should enclose the piece label in braces, which you get by shifting a bracket key. There are two automated Alfaerie sets. One is just the contents of the alfaerie folder, and the other is all the pieces from all the alfaerie folders. That one is huge. Note that the Utrecht pieces do not follow the convention of using green transparent backgrounds. They are provided mainly for people who have previously used JavaScript to display diagrams with these images.

Edit Form

Comment on the page Diagram Designer

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.