Check out Glinski's Hexagonal Chess, our featured variant for May, 2024.

Enter Your Reply

The Comment You're Replying To
H.G.Muller wrote on Thu, Apr 24, 2008 08:11 PM UTC:
Reinhard,

Apparently my point is not yet clear. My conclusion on piece values has
nothing to do with the fact that Joker80 ends consistently above Smirf in
10x8 Chess tourneys, and that Joker values pieces in one way, and Smirf
values them in another. This indeed is not proof for anything.

The result is 100% based on the fact that if I let engines play positions
with material imbalance, certain combinations of pieces systematically
beat other combinations, if the players are equally strong (e.g. because
they are identical). This is independent of the engine used, provided it
is not completely silly. No matter how you PROGRAMMED Smirf to value the
Archbishop, you cannot prevent that Smirf that plays a complex position
with where it has A will systematically beat the Smirf that has B+N+P in
stead. Because A is much stronger than B+N+P, and Smirf's search will
discover that, because it can use the A to gobble up Pawns which the B+N
will not be able to defend. And even if it could trade the A for B+N, and
wuld think it is an equal trade, it will most of the time prefer to win a
Pawn. And by the time it has captured the Pawn, the win of the other Pawn
will be within the horizon, and then another. And when the opponent is out
of Pawns, its own passers will get the promotion within the horizon. Most
of the time you will not be able to fool the search by giving it faulty
piece values.

Edit Form

Comment on the page Aberg variation of Capablanca's 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.