OK, to start with you should make the Diagram a bit smaller by using 35x35 pieces, as for many people it would not fit on their display now. So change the following to parameters as follows:
The Play-Test Applet does not pay any attention to diagram appearance; if you want to color the board you will also have to provide the lightShade and darkShade parameters yourself (specifying HTML-style colors, such as #FF000 for red), and to get coordinates displayed you have to set firstRank=1.
You currently have promoChoice=z, and since z is not a valid piece ID (which are all capitals) promotion does not work. If you want the Knight to promote you should add maxPromote=2 ; that would make the first 2 pieces in your table promote. It would then use the same promoChoice, though.
To get shogi-style promotions you could add promoOffset=7 . It then ignores the promoChoice (which you could delete), but always promotes Pawn to Amazon. Because the Amazon occurs 7 places later in the piece table. The Knight would then promote to Elephant, though. So you would have to re-order the piece specification lines to put the piece you want the Knight to promote to immediately after Amazon.
@Jean-Louis: redundant moves in the move description are not fatal, but are detrimental to the AI, which would then search these moves twice and would think much longer than needed. Sometimes it is hard to avoid duplicats (e.g. in a piece like RD it would be hard to make the Rook part avoid generating a move to the D-squares too, if the adjacent square in that direction was empty).
OK, to start with you should make the Diagram a bit smaller by using 35x35 pieces, as for many people it would not fit on their display now. So change the following to parameters as follows:
The Play-Test Applet does not pay any attention to diagram appearance; if you want to color the board you will also have to provide the lightShade and darkShade parameters yourself (specifying HTML-style colors, such as #FF000 for red), and to get coordinates displayed you have to set firstRank=1.
You currently have promoChoice=z, and since z is not a valid piece ID (which are all capitals) promotion does not work. If you want the Knight to promote you should add maxPromote=2 ; that would make the first 2 pieces in your table promote. It would then use the same promoChoice, though.
To get shogi-style promotions you could add promoOffset=7 . It then ignores the promoChoice (which you could delete), but always promotes Pawn to Amazon. Because the Amazon occurs 7 places later in the piece table. The Knight would then promote to Elephant, though. So you would have to re-order the piece specification lines to put the piece you want the Knight to promote to immediately after Amazon.
@Jean-Louis: redundant moves in the move description are not fatal, but are detrimental to the AI, which would then search these moves twice and would think much longer than needed. Sometimes it is hard to avoid duplicats (e.g. in a piece like RD it would be hard to make the Rook part avoid generating a move to the D-squares too, if the adjacent square in that direction was empty).