Check out Grant Acedrex, our featured variant for April, 2024.

Enter Your Reply

The Comment You're Replying To
Anonymous wrote on Thu, Mar 11, 2010 12:35 PM UTC:
Good game, but it did'nt deserve to be called 'Eurasian'. There are only
one piece wich is exactly Asian (Pao) and only one piece wich is exactly
European (Queen). Vao is fairy chess piece, so it's neither European, nor
Asian. Using piecec, wich are both European and Asian is primitive. To call
game 'Eurasian' i can suggest to add these pieces:
for 'Asia': Alibaba (someone might say what it also fairy piece, altrough
it's combinatian of two Asian pieces, but they are wrong: there was such
piece in game wich is even older than Chaturanga, it was called 'Boat',
when it was replaced with alfil; i did'nt suggest to use alfil because
it's to weak); Bodyguard (from Hiashatar, Mongolians and Buriatians are
Asians, aren't they?); some piece, wich was used ONLY in Shogi (for
example, lion from Chu Shogi); Camel from Tamerlane chess;
for 'Europe': Gryghon (from Grande Acedrexe); Chanselor and Archbishop
(they are pretty old pieces, and was invented in Europe); i would suggest
something from Bulgarian chess, but these games are not very known, so i
don't suggest it; and the main... PIECE FROM TAFL GAMES (see 'Pincer
pawn' in Piececlopedia)!!! This piece is really European, and it's even
older than all chess pieces!!!
If there will be game, wich uses these pieces, it will really deserve to be
called Eurasian!

Edit Form

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