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, Feb 2 09:41 AM UTC in reply to A. M. DeWitt from 03:20 AM:

Indeed, availability for Zillions means nothing to me. I don't have it, and I don't intend to buy it.

It must be said that alternatives like Ai Ai, the Interactive Diagram or Jocly are not on par with it regarding playing strength. The ID and Jocly are written in JavaScript, which is much slower than naturally compiled languages like C. Both evolved from projects that primarily focused on the user interface, and don't use the most efficient code even by JavaScript standards. For the ID I did not care, as it was never intended to be of super-human strength. And especially the Jocly AI uses a very poor engine design for Chess (probably as a compromise to also work for entirely different games). Ludii I know absolutely nothing about.

ChessV is a strong engine, and in general stronger than Zillions. But it is not as versatile. The configurable multi-variant engines for WinBoard (Fairy-Max, Sjaak II, Nebiyu) are also much stronger than Zillions, and although perhaps somewhat more versatile than ChessV not very easy to configure.

Perhaps I should start a project for rewriting the AI of the Interactive Diagram in C, so it could be used as a strong engine in one of the available user interfaces (WinBoard or ChessV). It would be interesting to have Greg Strong's opinion on this.


Edit Form

Comment on the page Featured Chess Variants

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.