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

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Thu, Oct 3, 2013 06:20 AM UTC:
Thanks for your suggestions.

@Joe: I did consider Seirawan-style gating for the Lion, but decided against it because it introduces yet another 'weirdness' from the POV of the naive Chess player. Your idea with the extra square is interesting, but it is not logically different from allowing a piece drop inside the 'Palace' (to speak in Xiangqi terms) and starting with the Lion in hand. (Well, OK, the rule that you can kamikaze-capture the Lion there makes it different, but in practice no one would be so foolish to allow his Lion to be taken by another piece, so that is a pretty moot point.) And if a resticted drop is going to be used to introduce the Lion, I would prefer restricting the drop to the back-rank.

I am in doubt whether the rule complication needed for introducing the Lion into the game is worth it, just to have a more aestethically pleasing array, with a uniform Pawn rank. Leaving out the third-rank Pawn give you a Rook on an half-open file immediately, which strategically would be a very large departure from FIDE. Especially in a mirror-symmetric setup, where the one to last moves his Knight away gets it soft-pinned on the Rook in a very nasty way. Indeed centro-symmetric setups appeal to me more, but on the down-side, they are a larger departure from FIDE. And the half-open Rook file then would point directly to the King side, making castling to either side unattractive.

@Greg: Using a non-8x8 board is a real discouragement for people to play it over the board. Here in the Netherlands 10x10 boards are common, because more people play interntational draughts here than Chess. So 8x8 and 10x10 boards are typically sold back-to-back. But in the rest of the World the situation is pretty dismal. So if possible at all, I would like to keep it 8x8.

@Antoine: I thought some more about the end-game problem, and it seems a real problem. Even without tablebases it is easy to see that KLPKL is much more drawish than FIDE KPK. Kings are safe from being driven to mate by the enemy Lion (and even from perpetual check) when they take shelter next to their own Lion, even in the middle of the board. And when the defending side parks his Lion next to the Pawn file in front of the Pawn, ready to igui it away when it comes in range, protected by its King, there is just no way to chase it away.

So it seems a bit of tweaking of the Lion-capture rules is needed. First I thought (inspired by Antoine's remark) of allowing distant LxL capture when only Pawns and Lions are left. But then I got an idea that accomplishes nearly the same in a natural way:

Forbid distant Lion x Lion capture during the entire game only if pseudo-legal recapture BY A NON-KING is possible. When you are then down to King + Lion, there is no way you can protect your Lion from being traded anymore. This will be enough to make advantages that are winning in FIDE also winning with a pair of Lions added. During the middle-game you would not normally want to use your King as only protector of your Lion anyway, so there seems little danger that this rule modification would lead to early Lion trading.

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.