Check out Atomic Chess, our featured variant for November, 2024.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Sun, Jan 7 07:46 AM UTC in reply to Fergus Duniho from Sat Jan 6 11:00 PM:

How much of this could be incorporated in the regular version of betzaNew.js for improving the behavior under 'size pressure'? I suppose the new cell-size directives would always be an improvement?

The rim-suppression color is a bit tricky, as I already made so many Diagrams that use FFFFFF for this. But I suppose it would not be harmfull to suppress it on both FFFFFF and FFFFF0. But perhaps it would be better to keep using FFFFFF as 'signalling code' for rim suppression, and let the Diagram use FFFFF0 in that case for the color of the part of the rim it still displays (as background for the coordinates). This method would be more robust in the hypothetical case we would ever want to change the page background color. The replacement color could be defined as a variable at the start of the script. Or perhaps the script could even be made smart enough to extract it from the surrounding HTML element?


Edit Form

Comment on the page Variants playable against the diagram's AI

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.
Avoid Inflammatory Comments
If you are feeling anger, keep it to yourself until you calm down. Avoid insulting, blaming, or attacking someone you are angry with. Focus criticisms on ideas rather than people, and understand that criticisms of your ideas are not personal attacks and do not justify an inflammatory response.
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.