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, M Winther.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on 2009-10-12 UTC
I tested the Secutor, and (as expctd) it is stronger than the Dimachaer. Where a pair of Dimachaers clearly lost against a pair of Knights, (scoring only 44%) a pair of Secutors beat the Knights by 53% (over 1000 games). This was with the Secutor value set slightly below that of the Knight, so that the side playing the Secutors would trade them for Knights if he got the opportunity (and its opponent tried to avoid such trades).

I tried the same match with the value of the Secutor set higher than that of the Knight. In that case the Secutors won by 53.4%, i.e. not significantly better. (Statistical error is 1.3%..) So the opening value of the Secutor is marginaly stronger than the Knight (5-10 cP), but when you program a constant value for it during the game it doesn't hurt much if you choose that below the value of a Knight. This is likely caused by the fact that the value of the Secutor drops during the game, so that the average value during the game might very wel be below a Knight's value.

It is quite possible that the empirical value of the Dimachaer and Secutor would go up a little with better handling, e.g. when the value would be allowed to vary with the piece density. In that case the Secutor sid would initially avoid trading them for Bishops and Knights, in order to make use of their superior tactical possibilities on a densely populated board to create an advantage. But as the material thins out, it would start to seek trading it for Knight and Bishop, and conversely would try to avoid trading other material as long as it was still stuck with the Secutors (because it would devaluate them).

Edit Form

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