The Chess Variant Pages



Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on 2019-10-18 UTC

Alfaerie is one of the six preconfigured settings in the design wizard for the interactive diagram, (setting the right values for the image directory, square size, white/black prefix and graphics type at the press of a button), and in fact the default choice. Other buttons give you Abstract, Motif, Utrecht, 2 sizes XBoard presets. And of course you could use your own uploaded graphics, by supplying the location and other parameters to the design wizard explicitly.

For the pieces I needed Alfaerie was not too bad. I had to improvise a bit for the (Mounted) Veteran, using the Wazir(-Knight) instead, thus only indicating the non-capture move correctly. But that seemed acceptible.

Some of the other Alfaerie pieces look embarrasingly simplistic (e.g. Elephant), so I usually prefer the XBoard theme when I need any of those. Even the orthodox pieces look pretty ugly in Alfaerie; they are not anti-aliased, giving them a very ragged appearance. This is so 20th-century... I think it is high time someone would take the trouble replacing all the Alfaerie image files by anti-aliased versions (with alpha channel).

versus  

BTW, I am happy you like Veteran Chess. I have not programmed it into any engine yet, but I play-tested it against a regular participant of the Dutch Superchess championship over the board, and it seemed quite playable. That 1:1 trading is discouraged by leaving the opponent with a promoted piece seems compensated well enough by that in 2:1 trading you can promote your second piece to compensate for the loss of the first. E.g. a Pawn protected by a Pawn is pretty much unassailable in orthodox Chess, but here after BxP, PxP, NxP=M promoting the Knight to a Rook-class piece plus capture of two Pawns seems enough compensation for the Bishop. So you don't get into stand-off situations too easily.


Edit Form

Comment on the page Veteran Chess

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.

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.