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 the game's inventor, Fergus Duniho. This game is a favorite of its inventor.

This is one of our Featured Games. Click the link to check out our others.

Enter Your Reply

The Comment You're Replying To
Kevin Pacey wrote on 2017-04-12 UTC

I believe you're right Fergus, that pieces values are useful fictions (in chess-like games). Yet it's also true that equivalency formulae for tradeoffs of various piece [+ pawns(s), optionally] combinations don't seem to always hold in such games, as a general observation (it also seems to me such formulae are often implicitly based on presumed average piece values). This can depend on whether the position is an endgame, open or closed, and all sorts of other quirky characteristics. In the case of chess such characteristics have been extensively thought about, or have arisen time after time, but for a less explored game like Eurasian Chess I'd suppose there is still a lot to be learned.

Still, people (beginners at least) crave having a simple, single set of average case piece values to go by, for any such game. I based my values for Eurasian Chess heavily on the endgame, which admittedly may not be entirely correct, but it's a jumping off point if nothing else. For average middlegame (if not opening) piece values, if it turns out that there's an important distinction that should be made (as by a Chinese Chess book I've seen, regarding some of that game's piece values for the endgame vs. earlier phase), at the moment I have less of a clear idea about what the average values of some of the pieces should be in the earlier part(s) of a Eurasian Chess game, if the values are indeed significantly different than in the endgame.

Edit Form

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