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 both of the game's inventors, Omar Syed and Aamir Syed.

Enter Your Reply

The Comment You're Replying To
Larry Smith wrote on 2009-05-16 UTC
Thanks for the heads-up on the info, Omar.

Kinda thought the piece values would be based upon not only their rank(power hierarchy) but also upon their position in relation to the opposing pieces. For example, the Elephant would be a very powerful piece but the opposing Elephant could lower that value simply by being within its area of movement(and this effect could be mutual). Blocking an equal, or even lower, ranked piece could be considered an asset to its value. 

Particularly when it relates to Rabbits. Keeping the opposing Rabbits as far from their last rank could be considered a positive field position. So, not only the value of the Rabbit could be based upon its particular position on the field but the values of all the player's Rabbits could be used to calculate an effective field position.

And Freezing would also be a value. The piece which is 'frozen', and the pieces which is doing the 'freezing', could have their overall value(or simply a sub-value) modified by this condition. This could also be further modified by the positions of other pieces in relation to these.

I've already coded a ZRF so that the engine 'randomly' initiates a set-up pattern for both sides. This allows me to test out a large number of potential set-up patterns. Of course, the current code is rather dim, being able to only look-ahead a few full turns. But I can manually create possible positions on the field and see how they will play out(if I have a lot of patience).

A simple translation of this code into Axiom will be the first step of the project.

Edit Form

Comment on the page Arimaa

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.