The site has moved to a new server, and there are now some issues to fix. Please report anything needing fixing with a comment to the homepage.



The Chess Variant Pages




The Piececlopedia is intended as a scholarly reference concerning the history and naming conventions of pieces used in Chess variants. But it is not a set of standards concerning what you must call pieces in newly invented games.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on 2013-10-02 UTC
Thanks for your feedback!

I am not sure if it is really a disadvantage to be stuck with the Lion until the end-game. Preventing the game from reverting to regular FIDE sort of forces this on us. I must admit that I don't know what consequences this has for the drawishness of end-games. It would indeed be bad if KLQKL would be a general draw. I guess I should investigate this by building some tablebases. (5 men on 8x8 is quite easy, and even 6 men might be doable on modern hardware, but my tablebase generator should be modified to take account of the Lion-capture rules, and the possibility to do hit-and-run captures.)

If KLQKL is generally won, then KLPKL might be generally won. And if small advantage can still be converted to wins even in the presence of Lions, there isn't any harm in the Lions always being there.

Your suggestions for wider boards are also interesting. I picked 8x8 so that it would be easy for people to play this over the board using standard equipment. (Dressing up one Knight with a rubber band, or putting it on a pedestal to identify it as Lion. Or just use any object of which there is a pair at hand, like a stack of Chekers chips or pepper and salt shakers in case both Knights are kept.) 

If the board were expanded to 10x8 I would rather add Shogi-like pieces such as Dragon (RF) or Horse (BW) than Capablanca pieces. E.g. put Lion next to King and Dragon next to Queen. Chess players would have to learn two new pieces rather than one, however, which is a bit at odds with the goal to lower the threshold. Even though I agree that it would likely give a much better game, both through the wider board making the short-range Lion less dominant, as well as offer more interesting trading probabilities for Lion vs other material (in particular Q+D).

My reason for not allowing promotion to L was to avoid complicating the Lion-capture rules by the possibility for there to be multiple Lions.

In any case, it seems essential to make some end-game tablebases, to check if this game would need tweaking of the Lion-capture rules to prevent it from being drawish.

Btw, what do you think about my defining of the protection of the Lion in terms of pseudo-legal recapture? In Chu Shogi this is natural, as exposing your King to capture is not illegal there, just stupid. But in Chess it would be illegal. So it is debatable whether a piece that can be recaptured only by a pinned piece is protected or not. Even in the FIDE game this gives rise to a subtlety: it would be protected against capture by a King, but not against capture by any other piece. For simplicity as well as conformance to Chu Shogi I treated the Lion the same as a King here: you cannot make distant LxL capture if a King could not have legally captured that Lion.

Edit Form

Comment on the page Lion

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.