You are on the backup site for Chessvariants.com. 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, Fergus Duniho. This game is a favorite of its inventor.

Enter Your Reply

The Comment You're Replying To
Fergus Duniho wrote on 2010-06-02 UTC
I once did a Shogi adaptation of Smess, called Smegi, which added Shogi dropping rules to Smess. But a Smess adaptation of Shogi is more of a challenge. It cannot work as straightforwardly as a Smess adaptation of Chinese Chess, because the pieces are not so easily distinguished by types of movement. Instead, they are distinguished mainly by directions and ranges of movement. So what I would suggest is this. Add the rule that certain pieces may only move in forward directions, either vertically forward or diagonally forward. For this rule to work effectively, every space would need to have both forward and backward arrows on it, for one player's backward is the other player's forward. This would leave the forward moving pieces available directions to move in. As in Shogi, the Knight should be able to leap. This is important, because it is easy to build barricades in Shogi, and it sometimes takes the leaping ability of the Knight to get through them. With a vertical forward arrow, I would allow the Knight to leap as it does in Shogi. With a diagonal forward arrow, I would allow it to leap to either of the two spaces it could reach by moving once diagonally, then once orthogonally outward.

Edit Form

Comment on the page Storm the Ivory Tower

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.