V. Reinhart wrote on 2017-03-08 UTC

About the piece images, I think the ones used make a lot of sense, because they match your abstract styles very well. The orthodox pieces all follow the normal shapes in your set. But since some unusual pieces are used, I selected piece shapes that best represent what they do.

For the guard (or "mann") I used the circle shape with triangle, to indicate it moves both orthogonally, and diagonally. It is a very basic shape just as the king (which has the same moves).

Your set does not have a hawk, so I used the tall triangle shape because it appears "sharp", just as a hawk has sharp talons and beak.

Also, there is no huygens, so I chose the pyramid shape piece with the "+" shape cut-out. The pyramid is a symbol of mystery, just like prime numbers, and the "+" shape represents the orthogonal moves of the huygens.

I hope you'll agree that these images are good choices for both "Trappist-1" and "Chess on an Infinite Plane".

Last, on the topic of playing on an Infinite Plane, a player can move a piece 50-million squares away. There is no problem with that (although the play would be questionable at best). If someone does this, the piece simply is not shown in the chess diagram. There is only a supplemental note added to the game status such as "white rook is in square (50,000,000, 2)". (file and rank of the piece). But in actual play, I don't believe there is ever any reason to move a piece this far away because there is nothing of interest so far out. The piece would be less effective at attacking because it could not create forks.

In all the games played so far, the farthest span of pieces ever played was 36 ranks I believe. Then the distant pieces moved back in. (I'll send you a link if you'd like to see the game's moves).

Anyway, thanks so much for your comments. I really appreciate them. There's currently several games in progress.

Edit Form

Comment on the page Trappist-1

## 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
• An URL by itself:

### 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.

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.
﻿