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

Enter Your Reply

The Comment You're Replying To
V. Reinhart wrote on Sat, Jul 22, 2017 07:57 PM UTC:

HGMuller's formula is interesting, and it's good to see there's a way to expand its scope by using ELC. Muller presented the formula as:

  value = 33*ELC + (33*ELC)*(33*ELC)/1584)

I prefer it a little more as:

  value = 33*ELC + 0.6875*(ELC)^2

In this form the variable occurs once for its linear component (33xELC) and once for its polynomial component (0.6875*(ELC)^2).

But this is just a minor stylistic preference. More generally, it's very interesting that a rather simple formula can be quite accurate for a wide range of leapers. Not sure if there's any future possibility (by Muller or others) to ammend it for longer range leapers. Of course, work like this always requires a lot of engine analysis, and follow-up evaluation of the data.

Good work on the formula!

Btw, do we know that Lasker's estimate of a king's value in an endgame (4) might not be too far off? The study that I did (which basically just confirmed previous work by Muller) was to estimate the value of a guard/commoner for the entirety of a chess-game (10x8 board).

From my study alone, I cannot dispute Lasker's estimate. As far as I know, it might be possible that a non-royal king might be worth a little more on an 8x8 board, and yet a little more in an end-game only situation.


Edit Form

Comment on the page Chess and a Half

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.