The site has moved to a new server, and there are now some issues to fix. Please report anything needing fixing with a comment to the homepage.



The Chess Variant Pages



This page is written by the game's inventor, Peter Aronson.

Enter Your Reply

The Comment You're Replying To
Greg Strong wrote on 2020-10-08 UTC

As far as I got it, the only unusual aspects of this variant is the piece confinement and the mandatory capture. So it should not be that difficult. The only special-purpose code that is needed would be for rejecting moves that end on an edge square and do not specify a locust victim (which could be added as the end of the Post-Move sections), and for apparently pseudo-legal moves with non-edge pieces or non-captures with edge pieces, a test whether any of the edge pieces has a capture.

Ok, perhaps I should have said it would be very difficult for me...

I have added full support to ChessV though.  This required a couple of special rules, but I added support for basic capture-by-overtake to the internal move generator.  My quandry now is what the pieces should be worth...  The Rook, Bishop, and Queen are modified in the same way so I assume their relative value should be similar to Chess... The board is enlarged, but use of the outer ring is limited and landing on it hurts your options on the following move significantly, so I think the values should probably not change much from 8x8 values.  The Knight is interesting - he has a choice of captures, so maybe his value is augmented.  The Pawn, when capturing, moves forward two spaces instead of one, getting it to the other side faster, so maybe it should be worth more as well.  But these are just guesses.

EDIT: Upon further consideration ... the Knight has a choice of captures, but no choice where he lands.  The Bishop, Rook, and Queen, though, unlike in Chess, can capture and still choose which square to land on (if there is space.)  So maybe the Knight is not more powerful.


Edit Form

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