Check out Makruk (Thai Chess), our featured variant for March, 2025.

Enter Your Reply

The Comment You're Replying To
A. M. DeWitt wrote on Sun, Feb 23 04:06 PM UTC:

H. G.,

I think I may have an idea for how to handle drops with the Diagram's current limitations.

So you know how the Shogi GC Preset have areas to the sides of the board? I was thinking of using that along with the mU for drops in combination with the Tinker(move, distanceFromLastRank) script to do this, as well as a custome shade function for visual definition of each region.

So in the board definition you would make enough space for both the board and hand regions. In the board region pieces would move normally, and in the hand region they would move as mU (universal kleaper to empty square) to the board region. Upon capture pieces would be unloaded to the hand region rather than be put in the holdings (with the holdings acting as overflow if the hand fills up all the way). Pieces would be unable to move into the hand region since it is off the board.

I am currently testing out a Shogi diagram that implements this idea. I have most of it done except for the Pawn Drop Mate testing and the code that puts the pieces in the hand (or removes them when undoing moves).


Edit Form

Comment on the page Interactive diagrams

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.