The Chess Variant Pages
Custom Search



Enter Your Reply

The Comment You're Replying To
Kevin Pacey wrote on 2020-12-14 UTC

I had considered the Q as a basic (FIDE) piece, and so I knighted it twice to produce the two Amazons (crowning a Q, in addition, not being 'possible'), as I had similarly knighted and/or crowned the R,N, and B twice (then there was also the angle of the Q starting out as the sole wife of the K in FIDE Chess). At least that's how I chose to carry out the theme for Sac Chess that I picked.

I neglected to mention that for a final setup I didn't wish to have more than one R-like piece on any file, as I disliked doubled R-like pieces being on a file that may be opened, possibly resulting in two very quick trades, or else heavy pressure perhaps being thus quickly created on a semi-open file. Next, I didn't want the Amazons in corners, nor the Chancellors preventing the analogues to Fool's and Scholar's Mate. Having decided on all that, and where to put the Centaurs (which I'd called Judges without being aware of the more conventional name - they are useful to protect a castled K where I put them, anyway, I think, and not deep hitting like Archbishops), I wasn't left with much choice where to put the Archbishops and the Missionaries. I preferred to have the Archbishops not on central files in case an enemy rook could suddenly wipe one out (Missionaries being slightly less valuable than Rs on 10x10 in my estimation), and in my final setup the Archbishops each ultimately point at an enemy Judge, which I estimate as weaker than an A on 10x10.

Anyone is welcome to try to improve on the setup of Sac Chess with a CV of their own. At least Sac Chess has had over 50 games of playtesting on Game Courier now, and the range of playable openings doesn't seem too small (nothing like FIDE chess in the early stages of a game, but I think it's tough for most if not all CVs to outdo that game in that way).


Edit Form

Comment on the page Sac 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.

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.