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 Thu, Oct 17, 2013 12:24 PM UTC:

Inspired by Gregs suggestions for 10x10, I think I found an ideal setup for the next step from Chess to Chu Shogi. I call it Chu Chess. I did not want to use the RN compound, as it does not occur in Chu Shogi. Of the pieces that do, it seems Dragon Horse and Dragon King (Crowned Bishop and Crowned Rook) are the most suitable. They are just a small variation on Rook and Bishop, and as their pictograms also look similar to those, Chess players should not have much trouble handling them. The Crowned Bishop is similar in value to Rook, and the Crowned Rook an in-between for Rook and Queen. That strengthens the heavy end of the spectrum, to make life more difficult for the Lion. And it does provide better trading possibilities for the Lion than in Mighty-Lion Chess, namely L for Q + DK or DK + R + R, so that you are not stuck with it as much, and one Lion versus other material will be more common without the game being immediately decided. (Three-for-one trades are not as difficult with Lion as in ordinary Chess, as a Lion can capture two pieces, and could then be traded for a third.) Yet they don't disturb the ratio of Queen-class pieces to Rook-class pieces very much, if you count the Crowned Rook (to be called 'Crook?') as a bit of both.

The addition of those would make the piece spectrum a bit top-heavy, though. So I also wanted to add some Knight-class pieces. From the Chu pieces Gold would be a logical choice, but it is a bit frightening to Chess players because of its asymmetry. So instead I picked the Commoner, symbolizing the unification of all Generals and other steppers that are so abundant in Chu Shogi. It has a move familiar to Chess players.

I don't want it to be over-crowded, as Chu Shogi definitely is, so I don't want two full rows of pieces behind the Pawns. Yet 10x8 is too small to accomodate all the pieces I want. So 10x10 with a Grand-Chess-like sparsely-populated back rank seems an obvious choice. I don't want to disband castling, though, in my opinion that is a flaw in Grand Chess, where you have to march the King to a safe place in many steps, like in 'ranging Rook' games of (regular) Shogi. So I put the King on the back rank, ready to castle, making room for the Lion to stand shoulder to shoulder with the Queen in Chu-like fashion.

With castling the need for easy opening of the Rook files seems not so great, and the a-/j-file vacancies would even become a severe weakness after castling. They can be nicely filled with the Commoners. An extra Commoner as defender to make the King fortress more Lion-proof definitely would not be a luxory. On the side where you did not castle, the Commoner can be developed by playing up the Knight Pawn, and moving it out diagonally towards the center, putting the Bishop behind it afterwards. Unlike Knights, Commoners are 'Lion proof' when protected: the Lion cannot step next to them for an igui attack. The Rooks in the mean time are free to roam the back rank.

I thought about allowing promotion of some pieces, but that seems a little bit too un-Chess-like. I also thought about allowing the Pawn to promote to Commoner only, (In Shogi they promote to Gold, after all), but I am afraid this would make the end-game to radically different and drawish (when the first to promote has no way to stop opponent passers from also promoting, even if they still need 3 or 4 moves to do it). Extend the depth of the promotion zone to 3 ranks (including the initial Pawn rank, as in Chu) does seem a good idea, thoug, and again is reminiscent of Grand Chess.


Edit Form

Comment on the page Lion

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.