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, Hans Aberg.

Enter Your Reply

The Comment You're Replying To
H.G.Muller wrote on 2008-05-01 UTC
I still can't see the point you are tring to make. If piece values cannot
be used to predict outcomes of games, they would be useless in the first
place. Why would you want to be an exchange or a piece ahead, if it might
as frequently mean you are losing as that you are winning? Fact is that I
OBSERVE that the piece values I have given below do statistically predict
the outcome of games with good precision.

If, according to you, that should not be the case, than apparently you are
wrong. If, according to you, that is not what 'good' piece values should
do, than that satisfactorily explains why you would consider your set of
piece values, which would cause whatever entity that uses them to play by
to lose consistently, in your eyes can still be 'good', and further
discussion could add nothing to that.

What you say about opponent modelling doesn't have anything to do with
piece values. Precisely knowing the limitations of your opponent allows
you to play a theoretically losing strategy (e.g. doing bad trades) in
order to set a trap. In general, this is a losing strategy, as in practice
one cannot be sufficiently sure about where the opponent's horizon will
be. So it will backfire more often than not.

And the datasets that are analyzed by me or Kaufman are not dominated by
players engaging in such opponent modelling. I can be certain of that for
my own data, as I wrote the engine(s) generating it myself. So I know they
only attempt theoretically optimal play that would work against any
opponent.

Edit Form

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