Check out Symmetric Chess, our featured variant for March, 2024.

Enter Your Reply

The Comment You're Replying To
Joost Brugh wrote on Mon, May 9, 2005 11:17 PM UTC:
I haven't thought about notation while creating the game. Zillions'
notation is clear. But one might want a more beautiful notation.

Position naming: My Zillions file uses a 21x11 grid (a..u by 1..11,
lefmost cell is a6, three adjacent cells are b5, c6 and b7, etc). Naming
by segments or roads is probably more elegant. The position names should
have the same symmetry as the starting position.

Piece abbreviations: Zillions uses the whole piece name. It's possible to
abbreviate it to a letter and one might even use no letter for a Pawn. To
prevent ambiguity, use a T for Star, M for Pawn Master and an R for Prince
when using the letter P for Pawn.

Triggered effects: A Pawn Master creates Pawns. A King can create a Pawn
Master. The Disruptor, Star and Elephant can capture more pieces. Choose
whether or not to notate the effect.

Promotion move: In Zilions, the promotion move is executed by dragging one
invading Pawn to the Pawn Master and choose the piece. The Pawn captures
the Pawn Master and becomes the promoted piece and as an extra effect, the
other invading Pawns are removed. This creates ugly moves like 'Pawn p5 x
r5 x n5 = Disruptor on r5'. A promotion move can be notated by naming the
segment and the promoted piece.

Wizard move: In Zillions, a move caused by a Wizard is notated like
'PawnMaster g4 x i2', which looks very strange, especially when you move
an enemy piece. Notation should indicate that the move is caused by a
Wizard. Also a good idea is to notate whether the moved piece is a
friendly piece or an enemy piece.

Check, mate, stalemate: Can be done like in chess.

Edit Form

Comment on the page Hexa Decimal

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.