You are on the backup site for Chessvariants.com. Any posts, moves, or other changes you make here will not be permanent, because the pages and database from the main site will be backed up here every midnight EST. Additionally, things may not be working right, because this site is also a testbed for newer system software. So, if you are not here to test, develop, or merely read this site, you may want to change .org to .com in the navigation bar and go to the main site.

The Piececlopedia is intended as a scholarly reference concerning the history and naming conventions of pieces used in Chess variants. But it is not a set of standards concerning what you must call pieces in newly invented games.

H. G. Muller wrote on 2008-10-17 UTC
I have been play-testing the Cannon in a Chess context, and it seems its opening value is about equal,
perhaps slightly less than that of a Knight. When I replace two Knight by two Cannons in the FIDE array,
the Knights win about 52%, which is barey significant. (Giving Pawn odds would result in a 68% victory.)
Replacing the Bishops by Cannons leads to a 58% victory for the Bishops (over a 400-game match),
which is approximately what the Bishop pair wins over two Knights.

Using the Kaufman value N=325 (centiPawn), this means that Cannon = 320. This makes it appreciably
stronger than the other well-known hopper, the Grasshopper, which has a value of 175 cP.

You are right about the mating potential of C+N and C+F. I adapted my tablebase generator to handle
a Cannon. The mate with C+F apparently can only be enforced in te corner of the Ferz color,
and it migt take 59 moves to drive the bare King there. Cannon + Wazir is also a general win,
and goes slightly faster, as the mate can be performed in any corner (41 moves max).
Cannon+Knight is easy by comparizon: only 30 moves. With Cannon+Alfil it is almost always draw.
There are some mating sequences, though (0.5% with wtm, 0.1% btm). The longest takes 13 moves:
White: Kd6, Cc5, Aa7; black: Ka1 (wtm).

Staunton-style Cannon

Edit Form

Comment on the page Pao

## 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
• An URL by itself:

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

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