The site has moved to a new server, and there are now some issues to fix. Please report anything needing fixing with a comment to the homepage.

H. G. Muller wrote on 2022-08-06 UTC

I am not sure that this is feasible. Alice Chess is basically a 3-dimensional variant (with 2 levels), where all pieces have two-leg moves where the seccond leg changes level, and which are lame or (locust-)capturing by their orthodox move in the first leg. But the code in the include file used by the wizard assumes 2-dimensional boards.

Of course you can map the 3d board onto a wider 2d board (16x8, or perhaps 18x8 to allow a dead zone in between the boards that even Knights cannot cross, deleting the squares in that guard zone from the board in the Pre-Game code). And then define all moves as 2-leg moves that have a (dx, dy) = (+-18, 0) leap as second leg. There is no way to describe that in Betza notation, so the Interactive Diagram could not be used to generate the legdefs array with move definitions. But you could of course write that by hand. Either from scratch, or by adapting the code generated for orthodox chess, adding a second leg to each move. E.g. the Bishop in orthodox Chess would have

```1 99  1  1     3 // bishop(104)
1 99  1 -1     3
1 99 -1 -1     3
1 99 -1  1     3
0
```

and this would have to be changed to

```2 99  1  1     3 // bishop(???)
1 18  0     1
2 99  1 -1     3
1 18  0     1
2 99 -1 -1     3
1 18  0     1
2 99 -1  1     3
1 18  0     1
2 99  1  1     3
1 -18  0     1
2 99  1 -1     3
1 -18  0     1
2 99 -1 -1     3
1 -18  0     1
2 99 -1  1     3
1 -18  0     1
0
```

And you would have to determine the new starting index for Bishop in this array, and put it into the B and b function definitions instead of 104.

I am not sure whether this would have the desired effect for castlings and e.p. captures, though. (Or indeed how the latter are supposed to work in Alice Chess in the first place.)

Edit Form

Comment on the page A Wizard for GAME-Code Generation

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
• An URL by itself:

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.``````

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.
﻿