The Chess Variant Pages



Enter Your Reply

The Comment You're Replying To
George Duke wrote on 2012-05-10 UTC
Wa Shogi's Heavenly Horse is not only a Nightranker, it is the Nightranker. To grasp ''Nightblinker is Nightranker capturing as a Nightfiler,'' there are already two more Suffixes assumed, Ranker and Filer. The subclass Ranker requires moves covering more ranks than files, and Filer more files than ranks. In themselves they are non-divergent, meaning capture and non-capture modes alike. They are intended for oblique directional piece-types, but separating x- and y-axes for the lengths. Outwards that includes Knight, Camel, Zebra, and then the rest of them up to 11 or 12 spaces so far defined. Restricting Knight to half his directions is Nighrranker, the Heavenly Horse (value 2.0); and Nightfiler too has only 4-squares potential from a starting square all different from Nightranker's four. A couple of earlier chapters are mostly divergent p-t naming, like M&B16 -- which refers back to the others, M&B06 M&B10. There in M&B16 is found the divergent Nightblinker of the introductory sentence among the Blinkers. Also for follow-up is Contrablinker as well as facility just going back and forth and expanding among all these Right-, Left-, and Contra-blinker, Ranker and Filer -- the same way done recently among related Scout, Dueller, and Guide -- with specific made-up piece-types. For one, CamelFiler from a starting square e4 travels, presumably leaping and not more interesting multi-path, to any and only a3, a5, h3, h5.________________________________________ CamelFiler is more restricted even than mediaeval Alfil, who reaches 1/4 the 64-square board. CamelFiler starting at a1 can only access a1, a3, a5, a7, d8, d6, d4, d2, g7, g5, g3, g1. //// The possibilities can hardly get exhausted. I don't think Charles mentions a NightrankerBlinker who reaches four squares from any given departure square, only two of which are non-capturing (value 1.25).

Edit Form

Comment on the page Suffix Index to Man and Beast

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.