The Chess Variant Pages

Check out Hectochess, our featured variant for November, 2023.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Thu, Oct 8, 2020 01:53 PM UTC:

Isn't it a bit strange that we rely on (old and disagreeing) western sources, while in this age of the internet it should be easy to get feedback directly from Korean players? Discussing disagreements between Gollon, Murray and Pritchard might be interesting in an article reviewing their books, but mistakes they might have made do not deserve to be mentioned in a rule description of the game. I never mention the 'Murray Lion' in the Chu Shogi article...

The Fairy-Stockfish developer has included Janggi in his engine now, and claims to have received a lot of feedback during its implementation from Korean amateur and pro Janggi players. I believe him. Which means I consider the current rule implementation in Stockfish to be reliable. Notable point in this are:

  • Turn passing is always unconditionally allowed, not just when it is forced.
  • The Bikjang rule for King facing is not applied in every tournament. If it is not, King facing is legal.
  • If it is, but is declined, it has (indeed) no effect on the possibility to win later for either player.
  • The point-counting tie breaker is not applied in every tournament.

So there are actually four sub-variants, bepending on application of Bikjang and point-counting rule.

It also seems wrong to describe Bikjang as "the Generals checking each other". Check is an imminent loss because of King capture. There is neither loss or King capture here, just a draw offer that can be accepted or declined. The whole idea that King facing is a check seems to be contamination by Xiangqi concepts.

Edit Form

Comment on the page Janggi - 장기 - Korean Chess

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.