Comments by fhou

It is the Wild Mirza variant : Ships are replaced by Griffons and the Snake by a Rhino

I've got it, I'm adding a rhino movement diagram

yes, it would be logical for the promotion to be triggered when entering the zone only.

It must be a nice trip this time of year.

Don't hesitate to take what you think is useful on the shogivars branch, if you use the western skins for shogi, don't hesitate to turn the black generals, I turned them but it's not necessarily better!

Here's an install link to Shogi, seireigi, kyoto, mini, but note that this may change soon.

For the record, I tested the feasibility with chu seireigi but couldn't make the lion/eagle and falcon moves correctly. But it's still interesting to see what it could become.

I haven't heard of Hectochess yet, but I'll look into it.

The same link in https

For the Lion we probably could make it work with HGM (it needs to combine drop model + fairy move) but we might finish what we've started first.

Indeed we probably have already everything for hectochess. I might give it a try.

Here's a draft of hectochess, which can be accessed from this dashboard so that you can check the rules and thumbnails.

I've chosen to keep the usual representation for the Leo so that people used to Jocly can play directly without consulting the rules too much.

The link to hectochess is restored. I'm going to make some corrections to the shogi model, but I'll probably wait until I'm sure it's fully feasible before finishing it properly.

It should be better but castling is not yet fixed.

If you want to check the rules : try again on here and follow this image

I think it's working well now.

Any objections to the rules?

I think the 64-move rule could be operational now(not tested).

As for the size of the promotion panel, I can’t change it easily, but as the number of large pieces is not limited, I can't see a situation where a bishop, rook or knight would be chosen, so the question arises of keeping them or not.

thank you for the advice, I'll look into it but from my point of view, as it stands it's acceptable

It's true, especially since I thought I'd done it at the model level, but it must have been overwritten during compilation, so I'll have to dig deeper.

you're right, sorry to have wasted your time on this.

It should be fixed.

But the file may be in a cache. Press [ctrl] + f5 to force js reloading?

indeed, it works well

Finishing the capablanca model with its prelude should eventually allow similar variants to be grouped together:

For janus, if we put "ANBKQBNA" in setup (King before queen)

castling become :

    var janus={ // asymmetric, to b- or i-file
        "4/0": {k:[3,2,1],r:[1,2],n:"O-O"},
        "4/9": {k:[5,6,7,8],r:[8,7],n:"O-O-O"},
        "74/70": {k:[73,72,71],r:[71,72],n:"O-O"},
        "74/79": {k:[75,76,77,78],r:[78,77],n:"O-O-O"},
    }

Finally could we split fairy-piece-model and a fairy-move-model in 2 files?

It's better to know now.

For my part, I wanted to test the loading from a FEN syntax on a 12x12 board. I was looking for a standard candidate that would be interesting to add. Gross chess?

Yes, it would be easier to understand

I would say there is a there might be a bracket issue in fairy-piece-model.js : Error: unexpected token: '{'

It works with the latest commit.

Concerning castling, I was wondering if cbCastlingDef needs more parameters than that in the case of janus

var janus = this.cbCastlingDef(4, 0, 9, 74, 70, 79);