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 2020-11-09 UTC

Indeed, the Snail has 5 moves, the Alpaca effectively has 5.33 moves. One should take care with asymmetric pieces, though: it is not only that captures and non-captures contribute different value; forward and backward moves also differ in importance. Also here the empirical evidence shows that forward moves contribute about twice as much as sideway or backward moves. So one could say the fD move represents 2/5 of the value of the D, rather than 1/4, and thus should be counted as 2/5 x 4 = 1.6 move. So the Snail effectively has 5.6 'move units'. The inverted piece, with a bD move, would only have 4.8, and would thus be significantly less valuable. This quantifies what Betza called 'forwardness'.

According to this calculation the Snail would thus be expected to be worth slightly more than the Alpaca. Otherwise the caveat holds that ZoG values are also just estimates, based on some unknown algorithm, and are very often completely off. But, as you can see in the piece table accompanying the diagram below, (by clicking the header of the 'move' column), the estimation algorithm of the Interactive Diagram actually agrees quite well with ZoG's estimate for the Alpaca/Knight ratio. And it assigns Snail and Alpaca practically equal values.

files=8 ranks=8 graphicsDir=/membergraphics/MSelven-chess/ whitePrefix=w blackPrefix=b graphicsType=png squareSize=34 useMarkers=1 maxPromote=1 promoChoice=QNRBAS symmetry=mirror enableAI=2 pawn::::a2,b2,c2,d3,e3,f2,g2,h2 alpaca::WmD:camel:d2 snail::WfD:tower:e2 knight:N:::b1,g1 bishop::::c1,f1 rook::::a1,h1 queen::::d1 king::::e1

Edit Form

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