Check out Glinski's Hexagonal Chess, our featured variant for May, 2024.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Sat, Mar 16 08:34 AM UTC:

You don't have to attack your own King for forcing checkmate with a Rook, do you?

It is not completely clear what "being in check by your own pieces" means. In FIDE rules the checking rule is formulated as that you cannot expose your King to (pseudo-legal) capture. But my own move would never do that for my own pieces, as after that it is not my turn to move anymore. And it is conceivable that the opponent is forced to resolve the self-check before it becomes your turn again, or that this turn will never come. E.g.

When white plays Qe2 here black is checkmated, and if that terminates the game there is no danger that the white King would be captured by its own Queen. Also, if black is on move here, can he play Ke2, because the Queen is not allowed to capture him, as this would also attack her own King? In FIDE rules capturing a King trumps the checking rule, and is allowed by any pseudo-legal move. But in Atomic Chess the rule that you cannot blow up your own King trumps capturing/blowing up the enemy King, and Ke2 would indeed be allowed in the given position.

So it is important to specify the priority of the rules, in particular what would happen in a position where you can both capture your own King and the enemy King. The opponent could put you in a discovered check from your own piece. Can he do that while exposing his own King to capture elsewhere, because you must save your own King from self-capture first? Would you already have lost, because you must capture your own King even when you can also capture the opponent's?


Edit Form

Comment on the page Sacrificial Chess

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.