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

Enter Your Reply

The Comment You're Replying To
Larry Smith wrote on Wed, Jan 21, 2004 12:31 AM UTC:
Since this is a game which involves the goal of a stalemate, the
possibility of a cluttered field is actually desired.  A player would be
wise not to impede their own progress with stone-throwing.

Capturing the opponent's Ariki will be an in-game strategy.  With three
of them, this will be a tough objective to capture them all.  But the
potential is there.  Impeding this piece's moves and stone throws would be a good tactic.

And once a player loses all their Ariki, they might not have the ability
to make their cell goal but they still might capture the opponent Moais. 
Or even to draw the game.

The Mato to’a can only be fully impeded by their own stones or enemy
pieces(not enemy stones).  They cannot be captured.  Send them into the fray.

Remember that the Moais can move swiftly across the field, it is merely
dependent on the connectivity of its stones.

The fact that a computer program has difficulty playing this game does not
negate its potential.  In fact, it increases it.  Once a game has been
fully quantified, although it may have a high degree of difficulty, it
becomes trivial.

For now, this game might best be played between two humans.  Once certain
patterns of play can be discovered, a good computer program might be
worked out.

Edit Form

Comment on the page Hanga Roa

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.