Check out Grant Acedrex, our featured variant for April, 2024.

Enter Your Reply

The Comment You're Replying To
Peter Aronson wrote on Thu, Apr 25, 2002 03:48 PM UTC:
I spent some (to much!) time last night fooling around with Ruddigore Chess. I started by hacking and slashing up Fergus's Duniho's Chessgi ZRF, and seeing what happened. (Zillions is hardly the only tool suitable for this sort of thing, of course, but it is the one that usually comes to hand for me. Occasionally I worry about the effect this has on my game designing, since if the only tool you have is a hammer, everthing starts to look like a nail. However, the essay <u>Zillions of Games: threat or menace</u>, will have to wait for another day.) <p> As a frame, the battle represents a Loser-take-all battle between Sir Ruthven Murgatroyd (white) and Sir Despard Murgatroyd (black) as to who will be stuck being the cursed Bad Baronet of Ruddigore. <p> The initial rules were: <ol> <p> <li><b>Ruddigore</b> Chess is a <a href='../other.dir/chesgi.html'>Chessgi</a> variant, and all rules of that game apply except when contradicted below.</li> <p> <li>Each turn that a player does not perform a wicked deed by capturing a piece (their's or their opponent's), they must sacrifice a piece to the curse. Pieces in hand may be sacrificed. Sacrificed pieces are out of the game.</li> <p> <li>You may capture your own pieces ('If a man can't capture his own, pieces, <strong>whose</strong> pieces <em>can</em> he capture?'). Pieces of your own you capture go into your hand.</li> <p> <li>The first three turns are a Bank Holiday, and there are no captures or sacrifices then.</li> <p> <li>If you run out of other pieces to sacrifice, and you must sacrifice, you must sacrifice your King and lose.</li> </ol> <p> The problem with this game, as a few minutes of thought would have told me, is that it is far, far easier to capture your own pieces than the opponent's. What you get is mostly self captures with occasional threats in order to force a piece loss on the opponent, with the goal of having them run out of pieces to sacrifice first. Not very Chess-like. <p> The made the follow changes then, attempting to get more pieces engaged: <ul> <p> <li>Only the King, renamed the Baronet and given the ability to capture (but not move without capturing) like a Knight in addition to moving like a King [WFcN], can capture friendly pieces (if you want something done right . . .).</li> <p> <li>The Knights are replaced by Gentlemen, which are limited Nightriders (NN2).</li> <p> <li>Pawns are now Quickpawns which can always move two forward, and I've eliminated en passant to encourage them.</li> </ul> <p> This made a small difference, but not enough. So I eliminated the Bank Holiday, and made sacrifices required only on even turns (Sir Despard did all of his wicked deeds in the morning, and did good in the afternoon). This helped a lot, now you can capture your own piece on an even turn, and deploy it on an odd one. Now, though, I'm wondering if the Gentlemen are too powerful, since when dropped they can fork like anything. Maybe Halfling Nightriders? <p> I also find I'm tempted to rename everything: Pawns into Farmers, Bishops into Vicars, Rooks into Squires, and Queens to Stewards. But on the other hand, if the move hasn't changed, it is confusing to change the name of the piece. <p> Anyway, this is still very much an on-going project, and I'd appreciate any advice anyone has.

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.
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.