The Chess Variant Pages



Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on 2018-04-01 UTC

I think the points raised by Greg are moot:

In Shogi, stalemate is a win, and making an illegal move a loss. That makes win by checkmate equivalent to win by King capture. When I played my mini-Shogi program on 81Dojo, I had to modify it to actually capture the King. Because the server allowed people to play on in a checkmated position, and considered the illegal-move claim that the engine would respond with as an illegal move in itself, awarding the win to the checkmated player. OTOH, the server admin has issued a warning that people who do play on in a checkmated position, rather than resigning, will be banned! Point is that in Shogi etiquette it is essential that the losing player explicitly admits his defeat. So unlike chess, checkmate does not end the game automatically, the losing player must say 'makemashita' in response, and that ends the game. So basically the situation is that there is only one legal response to a checkmate, wich is resigning. Any other response is illegal, and thus forfeits the game. Making illegal moves intentionally is considered unsportsmanlike, and lack of sportsmanship can result in a ban.

As to mate by Pawn drop: pieces can be dropped with either side up. So if you can mate through a Pawn drop, you can certainly mate through a Rook drop instead. So from a game-theoretical point of view a rule forbidding mate by Pawn drop has no effect on the game at all.

A more important question is whether it would be allowed to drop a Pawns in a file where there already is one. My guess is that this would be allowed. You can get two Pawns in the same file anyway by moving a Rook to a file with a Pawn, so forbidding it would achieve little (although it does affect the game in a minor way). You have at most two Pawns, so long strings of Pawns can never arise. In addition, players would not be very happy having a Pawn, when there is a Rook on the flip side. They would prefer to drop as a Rook, and when they have a Pawn, move it as soon as they can to make it a Rook.

The phrase "is played like standard shogi" should be taken with a large grain of salt. Lance,  Knight and Pawn can move to and be dropped on locations where they would not be allowed in regular Shogi, and with the promoted side up. So why not also in files that already contain a Pawn?


Edit Form

Comment on the page Kyoto Shogi

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.

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.