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

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Tue, Nov 28, 2023 07:10 PM UTC in reply to François Houdebert from Mon Nov 27 09:31 AM:

The number of chess variants implemented in Jocly raelly starts to explode, and with it the size of the src/games/chessbase directory. (As each variant has several filles there: a model and a view, a thumbnail, a description, credits, rules...)

Perhaps we should make a cleanup attempt, where we create a sub-directory in chessbase for every variant, and move all files related to that variant there. That would make the sources a lot less messy. An alternative would be to put a modest number of variants that are somehow similar into a single sub-directory. E.g. all 10x8 chess with BN and RN, all variants invented by the same person, etc.

We should also decide on how to organize the res/fairy directory for new pieces. Perhaps it is a good idea to put pieces that are only slight variations on each other in the same subdirectory. I have for instance added many resized pieces (which can continue using the same normamap and diffusemap), to get a better correspondence between size and importance in many games. The alternative crowned bishop and crowned rook could likewise share the directory with the existing versions. When I create a distorted version of a piece (which also can use the same maps) I also put it in the directory of the piece it was derived from.


Edit Form

Comment on the page Zanzibar-S

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.