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

Enter Your Reply

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

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.

I have made the arrows long in order to fit all the bend riders I want to build. Look at the next succesions:

and

The reason for the arrows to be that long is that the last 2 bent riders in each lineup should fit. I'm not sure if that is the best solution but it is a first attemp.

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. 

 If that was the case I would not be able to properly represend the vulture (name you had chosen for the 43&41 falcon - good one).

 

I am considering using a tileset with 2 english letters per picture. Maybe this will make things clearer.

All that because remember I have 0 tallent for this. But I am open to any suggestions.


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.