The Chess Variant Pages



This page is written by the game's inventor, Jörg Knappen.

Enter Your Reply

The Comment You're Replying To
Chris Chradle wrote on 2016-12-01 UTCGood ★★★★

Hi Joerg,

 

inventing chessvariants is silver (computer-aided) playtesting is gold ;) If I don‘t err the Essential Knight Rider is your creation and the problem, that occurs for this army is as old as the piece itself => already in the starting position, it has impact on the enemy‘s camp. When I discovered the chessvariants-site in 2002 your article Nachmahr was my favorite entry for a long time. I never played that game, but I examined it, because it offers a nice overview of several Knight Riders. In those days I saw already the problem that the Essential Knight Rider on g1 can take the Narrow Diagonal Crooked Knight on c8, the pawns on the third rank don‘t prevent that.

 

It‘s funny that this kind of crooked Knight Rider was invented last, it actually is the most logic Knight Rider. It is a strong piece, but not too strong, so you can combine it with pieces like the Rook or – like in this game – with the bishop. I‘m currently working on a chessvariant with crooked pieces and I plan to use combination of Boyscout an Essential Knight Rider as promoting piece. The funny thing is that the second Essential Knight Rider move and the third Boyscout move „overlap“.

 

There is another chessvariant that has to deal with a powerful Knight Rider, it‘s Ubi Ubi Chess. The solution Bodlaender found, was to shift the opponents f-pawn and the d-pawn one square ahead. You can probably introduce that special rule to save your brilliant idea.

 

The idea is really beautiful, the theme of this army is in my point of view, that the minor pieces are weakened. I like the introduction of the Knave, which was a topical piece in those days. The choice of the rook could be a bit more creative. You actually can weaken the rook and put an amazon on d1.

 

You pointed out, that the player has to make the decision, if he should develop the Knave or the Diamond on the natural knight development squares. One possibility to solve that problem could be, to place the Diamonds on one Wing and the Knaves on the other. I prefer the Knaves on the kings wing, because they can attack the opponents pawns in an e4-game. Otherwise the Knaves will almost always placed on c3 and f3 and the Diamonds have to evade to d2 and e2. On those squares they can‘t attack the opponents pawn, but they can at least protect the own pawns.

 

Greetings Chris ;D


Edit Form

Comment on the page Sai squad

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.