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

Enter Your Reply

The Comment You're Replying To
🕸Fergus Duniho wrote on Thu, Jan 11 05:37 PM UTC in reply to Kevin Pacey from Wed Jan 10 01:37 AM:

I tried a game with Joe Joyce, but after my first move as White the pieces all turned to question marks:

There is an inconsistency in your preset. On the one hand, you are using the alfaerie-many set, whose images are all .gif files, but on the other hand, you have this code in your preset:

set mypieces assoc
  P "wpawn.png" p "bpawn.png"
  B "wbishop.png" b "bbishop.png"
  R "wrook.png" r "brook.png"
  A "wram.png" a "bram.png"
  F "wbutterfly.png" f "bbutterfly.png"
  C "wcamelbishop.png" c "bcamelbishop.png"
  K "wking.png" k "bking.png";
setsystem dir "/graphics.dir/alfaeriePNG/";
setsystem pieces #mypieces;

The result of this inconsistency is that it is looking for .gif images in the /graphics.dir/alfaeriePNG/ directory, which has only .png images in it. So, the file names it is contructing do not match any actual image files, and it is replacing them with the question mark, which means the requested image file could not be found.

Although I came up with the idea, defining custom piece sets in your code is a very bad idea, and I do not recommend anyone do it. Just rely on your specified piece set and use aliases if the piece labels used by the set do not already match the notation you want to use.


Edit Form

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