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

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Fri, Jan 6, 2023 02:47 PM UTC:

You get many draws. I hardly had any.

When white had 3N+C vs black 3C+N (setup below), white won 101 games, black 26, and 1 draw (79.3%).

With reversed colors black won 73 games, black 20, and 3 draws (77.6%)

Total result: Nightriders vs Cannons 176-48 (78.6%). Statistical error 3.3%.

I used C=350, N=460, Q=851, Half-Mao = 74. In my experience there are no self-fulfilling profecies here: if you let the engine believe the wrong piece is the more valuable, the better piece would still win. Because no matter whether their believe is correct or not, one of the players would still avoid they would be traded for each other. So the imbalance stays around a long time, during which you measure how much damage the pieces do to others. (Unless you go to extremes like Pawn > Queen, then it will of course quickly sac its Queen for a Pawn, as Pawns are way to weak, abundant and exposed to avoid such a trade.)

In fact the performance of the piece that the engine thinks is most valuable would suffer from this, ('leveling effect'), whether the believe is correct or not. Because its deployment will get hindered by the need to avoid 1-1 trades, from which the piece that is believed to be worth less does not care about that.


Edit Form

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