The Chess Variant Pages
Custom Search



Enter Your Reply

The Comment You're Replying To
Charles Gilman wrote on 2011-02-27 UTC
It occurs to me that as this is, apart from the Point funnelling, a Glinsky-orientation variant and has an unusual shape it is not particularly suited to ffen diagrams. The fact that the 60° turning of the board suits the funnelling of each player's left-hand Points is counterbalanced by how it obscures that of their right-hand ones. So given that I'm not going to create a custom image file, who thinks that the following Ascii Art diagram would suit the variant better?
____________ ___ ___________________ ___ ____________
___________ /Rb2\___ ___________ ___/Sg2\ ___________
___________ \___/Rb2\___ ___ ___/Sg2\___/ ___________
___________ /Rb2\___/Ch2\___/Ge2\___/Sg2\ ___________
___________ \___/Fh2\___/Rk2\___/Fh2\___/ ___________
___________ /Sn2\___/Pt2\___/Pt2\___/Sn2\ ___________
___________ \___/Pt2\___/Pt2\___/Pt2\___/ ___________
________ ___/Pt2\___/ . \___/ . \___/Pt2\___ ________
____ ___/Pt2\___/ . \___/ . \___/ . \___/Pt2\___ ____
 ___/ . \___/ . \___/ . \___/ . \___/ . \___/ . \___
/ . \___/ . \___/ . \___/ . \___/ . \___/ . \___/ . \
\___/ . \___/ . \___/ . \___/ . \___/ . \___/ . \___/
___ \___/Pt1\___/ . \___/ . \___/ . \___/Pt1\___/ ___
_______ \___/Pt1\___/ . \___/ . \___/Pt1\___/ _______
___________ \___/Pt1\___/Pt1\___/Pt1\___/ ___________
___________ /Sn1\___/Pt1\___/Pt1\___/Sn1\ ___________
___________ \___/Fh1\___/Rk1\___/Fh1\___/ ___________
___________ /Rb1\___/Ch1\___/Ge1\___/Sg1\ ___________
___________ \___/Rb1\___/ _ \___/Sg1\___/ ___________
___________ /Rb1\___/ _________ \___/Sg1\ ___________
___________ \___/ _________________ \___/ ___________
Note that this not a general question about hex variants as Wellisch-orientation ones (except for my recent Stelliform 6-player Chess) are not that suited to Ascii Art, which inflicts the same awkward turning on them that ffen does on Glinsky ones.

Edit Form

Comment on the page Flatstar page

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.