Check out Kyoto Shogi, our featured variant for June, 2025.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Fri, Sep 8, 2017 07:19 AM UTC:

Tai Shogi features a royal Kraken (called Emperor), and in Maka Dai Dai Shogi the King can promote to such an Emperor. To make this work, there is a sort of anti-trading rule for Krakens, similar to the Lion-trading ban in Chu Shogi: an Emperor is not allowed to capture a protected Emperor. Or actually, it is not allowed to capture any protected royal (you can have multiple royals in these games.) The historic rules are not entirely clear, and some interpretations are even that it can never capture any protected piece. (Mostly moot, as doing so would lose you your Emperor, which you certainly would not want.)

This issue is related to the definition of check, whether it is in terms of pseudo-legal moves (as in FIDE Chess), or in terms of legal moves for capturing the King. Or, in other words, whether the checking rules are applied front-to-back or back-to-front. In FIDE rules a piece that is pinned on its own King can still deliver check; that by actually capturing the King it would expose his own King to capture is of no import. In a recursive formulation of the rules a pinned piece would not deliver check, because the ban to expose its own King weighs more heavily than the fact that it captures that of the opponent. Its captures would not be legal moves, so the opponent King can safely go to the squares that the piece would target if it had not been pinned.

Under the recursive rules you could also step next to the enemy King as long as you are protected. In any contiguous sequence of captures of royals, it would be the last capture that decides the game rather than the first. So the game proceeds as long as royals can be captured, even when the player making such a capture has already lost all his own royals. (This is reminiscent of the Shatranj baring rule, where King baring doesn't grant an instant win, but the opponent gets one more turn to also bare the other King.)

A royal Kraken is perfectly feasible with these recursive checking rules; as long as you keep it protected it is save from capture by its counterpart. (Not that it would make a very nice game, IMO; a royal Kraken is very hard to checkmate, so you can only win by practically exterminating its entire army, so that there is no way to keep it protected against capture by your own Emperor. So the game loses the character of Chess, with a royal piece that has to be protected at all cost, and becomes more Checkers-like.)

For a non-royal Kraken you can solve it by some ad-hoc rules. Like that a Kraken capturing royalty becomes 'tainted', and that the game ends on the following conditions, applied in that order:

  1. When you capture a tainted Kraken, you win
  2. When you had no royal before your move, you lose

It would also be possible to simply declare the royal immune to Kraken capture. This would be more a property of the King than of the Kraken.


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.
Avoid Inflammatory Comments
If you are feeling anger, keep it to yourself until you calm down. Avoid insulting, blaming, or attacking someone you are angry with. Focus criticisms on ideas rather than people, and understand that criticisms of your ideas are not personal attacks and do not justify an inflammatory response.
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.