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

Enter Your Reply

The Comment You're Replying To
Bn Em wrote on Wed, Jun 14, 2023 10:48 PM UTC:

@Aurelian

The pieces you're proposing, with, as you say, less emphasis on centralisation in exchange for greater power at range, remind me a little of a more organic way to achieve what Big Outer Chess was going for. I wouldn't worry a priori about a ‘lack of personality’ from being part‐leaper and part‐rider; even things like the Archbishop have plenty of character, and there's certainly a distinctiveness to such a dispersed pattern of movement

As for partial bent riders, if not the chiral ones what about Ships/Snaketongues or their sideways or (as yet unattested afaik) crabwise counterparts?

The compound cannon would indeed probably deserve careful handling

@Jean‐Louis

Your Godzilla is not particularly less new than your Simurgh/Qilin: Gilman gives the latter two as respectively Metropolitan and Ancress — and even uses them in Four‐Linepiece Fusion — though ofc it makes sense that you minght prefer to stick with the monster theme for the names.

That said, whilst duplication of ‘Simurgh’ is fine (Gilman uses it for the viceroy‐then‐bishop viceroy‐then‐rook which only exists in 3D (or hex)), it seems odd to me that you'd choose to duplicate Qilin, which is just the Chinese version of Japanese Kirin, i.e. the familiar FD


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.