The Chess Variant Pages



This page is written by the game's inventor, João Neto.

Enter Your Reply

The Comment You're Replying To
Peter Aronson wrote on 2003-05-30 UTC
I hacked together a crude ZRF for the game last night (I'll clean it up and post it today or tomorrow), and it was interesting. Zillions, with its usual preoccupation with material, seemed to head to armies of 13 Knights, 1 Queen and 1 King per side. Nothing very surprising there. <p> However, on reflection I find myself wondering if the game doesn't make it too easy to make passive moves. A pair of Knights, for example, could pass back and forth a stone all day without substantially changing the board position. I wonder if a two move approach, as used in many of Ralph's recent board connecting games might be better. Each player would have two moves a turn: the first is obligatory, and requires moving a stack from one space to another; the second is optional, and consists of moving a stone from one stack to another. Or alternately, maybe a player could be forbidden to make two transfers in a row. <p> Another issue (and this one was illuminated both by Zillions' play and John's earlier comments) is that the relation between the number of stones in a stack and the power of a stack is very irregular. Two stones are much more powerful than one stone, but three stones are hardly any stronger than two, while four stones are a fair bit stronger than three, and five stones are no stronger than four and six stones are much stronger than five. I wonder about this approach: <table border=1> <tr><td><b># of Stones</b></td><td><b>Piece Type</b></td></tr> <tr><td align=center>1</td><td>Pawn (mfWcfF)</td></tr> <tr><td align=center>2</td><td>Mao</td></tr> <tr><td align=center>3</td><td>Bishop</td></tr> <tr><td align=center>4</td><td>Rook</td></tr> <tr><td align=center>5</td><td>Cardinal</td></tr> <tr><td align=center>6</td><td>Queen</td></tr> </table> Yes, I realize it isn't FIDE Chess anymore, but at least there's a more even power gradiant.

Edit Form

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

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.