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

Enter Your Reply

The Comment You're Replying To
Anonymous wrote on Sun, Jan 19, 2003 08:08 PM UTC:
' Another problem (aside from the Graphics issue) with toggling on and off
movement capabilities is if there is only one type of piece with toggles,
Zillions will think them all to have the same piece value. So a Queen of
the Night (RBNN) and a Barc will have the same value. This wouldn't lead
to good play.  '

Maybe I don't understand ZOG as well as I thought.  Don't attributes stick
to individual pieces, and not to piece types?  Can't you give each piece a
whole set of attributes, such as wazir, ferz, barc, crab, doublewazir,
doubleferz, doublebarc, doublecrab?  And each piece gets a unique name. 
Then, when you drop or remove a part, you reset the appropriate
attribute(s).  For example, if you drop a wazir on a piece that is only a
ferz, you turn on the wazir attribute, leaving the ferz attribute alone. 
If you drop a wazir on a piece that is already a wazir, you turn off the
wazir attribute and turn on the doublewazir attribute.  Then, each piece
gets the same moves definition.  Each move block would look something like
(verify wazir?) (leap1 n) (leap1 s) (leap1 e) (leap1 w) and so on for each
of the eight attributes.  That way, a piece would only move according to
whichever attributes were currently on.  Am I missing something?  Of
course, this doesn't solve the problem of pieces changing powers but not
changing appearance.

Edit Form

Comment on the page Mad Scientist Chess

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.