Check out Glinski's Hexagonal Chess, our featured variant for May, 2024.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Tue, Jan 26, 2021 09:49 AM UTC in reply to Aurelian Florea from 03:19 AM:

I think movement-diagram-inspired piece symbols can work, when you don't try to reproduce the movement diagram too literally. After all, the purpose of a piece representation in a game position is not to teach a completely unintiated player how the piece moves. Perhaps only to give him a hint for that. But he can be expected to know how these hints are encoded in the shape. The most important is that the shapes are strikingly different. Then the palyer will identify them at first glance, just like he would be able to distinguis the picture of a camel and a horse in a pictorial representation, or the various kanji in an oriental representation. In the end these are all just shapes that have to be distinguished from each other; camel or horse heads mean just as little to a person who has never seen an animal in his life as kanji do to a westerner.

Your Knight, Camel and Zebra representations fail the criterion of easy distinction. They are 'topologically similar', and the distinction has to come from carefully examining the distances. It would be much better to indicate smaller distances by making those touch, as touching / non-touching is an absolute difference. Like:

People that would no longer be able to recognize it as the move diagram can simply memorize "this shape is a Camel, and that shape is a Zebra", which still doesn't make them off any worse then whether they had to memorize which kanji stands for Gold and which for Silver.

I also would not make the arow you use to indicate sliding too long; it causes too much disparity in the size of symbols, and also makes the symbols for Rooks and Bishops have too little 'body'. Much better to indicate infinite-range sliding by something in the width of the lines. E.g. like making it extra thick.


Edit Form
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.