Check out Atomic Chess, our featured variant for November, 2024.

Enter Your Reply

The Comment You're Replying To
George Duke wrote on Mon, Aug 9, 2010 03:43 PM UTC:
Devapala, that's a Camel, not a Giraffe, so the piece can negotiate the Archipelago. Charles Gilman asks that too in the first comment here seven years ago! I am sure Camel is the intent as well the optimization. And Yavana is intended Camel and Wazir. My earlier comment reference to Giraffe is sidetracked by topic of board symmetry, which discussion was including several threads, unusually so seeming out of context, in which Ramayana only figured. This now corrects March 2009 comment's error, as types board symmetry would hardly bear on whether the piece-type is Camel or Giraffe. Campos' perfectly good serious CV, Ramayana, must have Devapala as Camel. For example, move sequence by starting Devapala at a8, as a8-d9-c6-f5-i4-h1-i4-l5-m8-p9. Also convincing is that in compounds all the other regulars are there: Knight, Wazir, Ferz, Alfil, and Dabbabah. Although 84 squares, the board is thought of as 11x16.

Edit Form

Comment on the page Ramayana Chess

Conduct Guidelines
This is a Chess variants website, not a general forum.
Please limit your comments to Chess variants or the operation of this site.
Keep this website a safe space for Chess variant hobbyists of all stripes.
Because we want people to feel comfortable here no matter what their political or religious beliefs might be, we ask you to avoid discussing politics, religion, or other controversial subjects here. No matter how passionately you feel about any of these subjects, just take it someplace else.
Avoid Inflammatory Comments
If you are feeling anger, keep it to yourself until you calm down. Avoid insulting, blaming, or attacking someone you are angry with. Focus criticisms on ideas rather than people, and understand that criticisms of your ideas are not personal attacks and do not justify an inflammatory response.
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.