You are on the backup site for Any posts, moves, or other changes you make here will not be permanent, because the pages and database from the main site will be backed up here every midnight EST. Additionally, things may not be working right, because this site is also a testbed for newer system software. So, if you are not here to test, develop, or merely read this site, you may want to change .org to .com in the navigation bar and go to the main site.

The Chess Variant Pages

This page is written by the game's inventor, Charles Gilman.

Enter Your Reply

The Comment You're Replying To
Joe Joyce wrote on 2007-02-26 UTC
Not even if you always get white and I tie one pawn behind my back? :-)
While I don't consider myself a veteran CVer, I'd probably pass for one
to most people, so I can't argue too much with you on learning curves.
But I think a good part of that learning curve is avoidable with more
user-friendly rules. [For me, that came about when I got people to play my
games and they made me give them simple, understandable rules, another
reason to suspect little general game play for Hoo Mitregi]. And maybe a
different piece set. I know when I see the same symbol used right side up,
upside down, sideways and inside-out, it bothers me, mostly because I'm
used to reading upside down and sideways, and I more or less automatically
'correct' what I'm seeing to right side up. This can make the diagrams
confusing as heck for me. I guess this is my point: the game itself looks
simple and nice and should play well - I might reduce the number of ranged
pieces, probably replace the forward-onlies with medium range pieces, but
that's me, not Charles, and his game looks good, once you understand it.
The learning curve is maybe more figuring out what is being said; but now
I am criticising another's rules-writing techniques and abilities, and
after some stuff I've put up, I shouldn't be saying much. As for some of
the other things you've said, I'd like to continue that discussion in
another comment.

Edit Form

Comment on the page Hoo Mitregi

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.

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.