[ List Earliest Comments Only For Pages | Games | Rated Pages | Rated Games | Subjects of Discussion ]
Check out Janggi (Korean Chess), our featured variant for December, 2024.
Check out Janggi (Korean Chess), our featured variant for December, 2024.
I pushed everything I have to the pullreq branch now. Capablanca Chess appears to work for 10 variants now, selectable through a prelude: Capablanca, Gothic, Bird, Carrera, Embassy, Ladorean, Grotesque, Schoolbook, Univers and Janus Chess. There is a large variety of castlings involved (2-step, 3-step, and since the initial King location also varies, which requires a different castling descriptor in Jocly, that already makes four). Carrera has no castling (at least that was easy), but there is no standard support for flexible castling, so I had to implement that myself.
Apart from the buttons with the icons indicating the pieces between the corner Rooks, I used a background image with the names of the variants:
A blemish on the implementation of flexible castling is that, after you select the King, it highlights the Rook for the 2-step castling, and the King destination for 3 or 4 steps. (This because the standard way for Jocly to enter a castling is highlighting the Rook, but obviously you have to use something else if more than one castling with the same Rook is possible.) This looks a bit unnatural. It would be better to let all castlings be indicated by the King destination. But for the tabulated castling in the castle field Jocly does it the way it always does it, highlighting the Rook. And since the extra castlings are defined relative to the tabulated castling, one of the castlings has to be tabulated, and then the Jocly standard code would offer that as a choice.
I suppose I could try to tabulate a 1-step castling, and prevent that Jocly tries it by removing the 'castle' properties from the Rooks. The standard code will then think there are no pieces to castle with, and ignore the tabulated 1-step castling!