The Chess Variant Pages
Custom Search



Enter Your Reply

The Comment You're Replying To
George Duke wrote on 2010-07-07 UTC
This continues from Cazaux's Jetan article. Cazaux himself implicates the second older and original variant by Burroughs with clearly non-jumping Odwar. I saw it too in the text of 'Chessmen of Mars' separate from the two main sets of rules. Jetan is a literary CV that never polished clear-cut rules but did come rather close, and the job has to be finished for him. Non-jumping Flyer is superior, made fully multi-path by clear specific pathways along diagonals always three-step. Otherwise, if full leaper instead -- ignoring for now the yet other hybrid interpretation mixing both stepping and leaping -- Flyer/Odwar becomes plain tri-compound of Ferz (1,1), Camel (1,3) and (3,3), the latter which Gilman dredges from our problemist past as ''Tripper'' by ways of George Jeliss. There are no other destination squares. Jetan's best main-line formulation, attributable to Burroughs, reserves jumping to Princess and Thoat exclusively in the natural order of things (further justified in follow-up comment). The Odwar should not leap because the diagonal pathways are interesting in themselves and because those destinations combining Ferz, Camel, or Tripper are meaningless without the idea of three diagonal steps inclusive of them all. Any leaper to those grouped squares is inferior to other popular organizations of target squares, such as Gilman's duals as bi-compounds or Buffalo (Ca, Z, N) as tri-compound. The latter is aesthetic for instance because the squares are adjacent to themselves and away from the departure square. Particular Jetan Odwar leaping becomes on the same ordinary level of Canadian Omega Chess Champion as more or less arbitrary tri-compound. That jumper Flyer ruins his whole point of existence, because the player does not then regard the underlying structure in similarity of three required steps on the diagonals of 10x10.

Edit Form

Comment on the page The Game of Jetan page

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.