Ratings & Comments

I guess the drop model still needs some tweeking. The square painting on the hand ranks should be the same as that of the other hand squares. Now there seems to be no coloring at all, so that the rim texture shines through. I suppose the logical way to do this is that the square-painting array that has to be defined in the game's view file should include the extra ranks.

It is also not clear to me why the 'counter piece' in the lower-right corner is larger than the others.

[Edit] The array boardLayout defined in the view file is accessed in two places in grid-board-view.js, inside nested loops over rows and columns. The loop over rows was modified to skip the extra hand ranks. I suppose this was a bad idea; especially in the 'paintCells' function it should have run over all ranks, requiring the boardLayout to also specify how the cells in these extra hand ranks should be colored. There is a second routine 'paintInCoordinates' that also loops over all cells, which does more complex things and might need more subtle modification than just changing the loop limits. But it seems this function is not normally used.

The handLayout[-1] in the view file appears to have a 16 where there should be a 17, which causes misplacement of the 'counter piece' on 15 rather than 16.

Talking about background it doesn't seem to work on my device even though it used to work. Interactive Diagrams that use backgrounds like Eurasian Chess, Chak, VaoQi don't seem to have backgrounds on my device.

Done!

This is an excellent concept. There's just one tweak I'd like to see. Pawns on the a-file cannot move any further to the left, so that could be a problem. One way to remedy that might be to divide the board vertically down the middle, giving pawns on files A-D a move to the RIGHT, and on files E-H to the LEFT, as you have currently done for all pawns.

How about switching Diamonds & Onyxes? or Onyxes with Lame Ducks?

I filled in the board size metadata as 8x8, but perhaps it would be better as 8x15 (still with 64 cells)?

You must also put

set opaque (EA FA BA SM AR ea fa ba sm ar);

there to make the flying pieces block each other.

Thanks.

For the terror trading rule, would it work to have set protected (EA T t) in pre-move 1 and set protected (ea T t) in pre-move 2?

or maybe they should be in post-game 2 and 1?

The author, HaruN Y, has updated this page.

Here are the errors I didn't find before or are new:

Incorrect 3d Kanji Readings (all should be colored red)

• Promoted Lance (should say 奔虎)
• Promoted Gold General (should say 大象)
• Promoted Kirin (should say 角行)
• Promoted Phoenix (should say 飛車)

You should add the western-style piece images for the rest of the pieces in the Pieces section (to align with the interactive diagram).

I have done it and it seems to be working fine!

I made some corrections.

ctrl+f5 : may help to reload scripts in case of cache issues

No Move Zero rule? I doubt this army is weak.

I saw you added the 3d Kanjis back to Chu Seireigi. I went through and tested everything, and here are the errors I found

Incorrect 3d Kanji Readings

• Unpromoted Great Leopard (should say 大豹)
• Promoted Knight (should say 天馬)
• Promoted Silver (should say 走狼)

Other

• Promoted Lance, Gold seem to crash/softlock the game
• Promoted Copper General (大豹), Promoted Running Wolf (奔猪) assets doesn't load
• Promoted Kirin (角行), Promoted Phoenix (飛車) indistinguishable from unpromoted counterparts (kanji should be colored red)

P.S.

I was surprised that they didn't have the same movements. I wondered whether a different adjective might be better to distinguish them: e.g. cunning fox and vigilant rabbit, Same for the whale with chu shogi.

That was because I found the Wa Running Rabbit to be too similar to the Lance, and knew that it would add too much defense after testing with the Old Kite. So I gave the Running Rabbit the ranging moves from its Taikyoku counterpart while omitting the stepping moves. The reason it has the same name as the Wa Running Rabbit is because it is one of only two Taikyoku pieces to be a rabbit, and I thought the running kanji fit better. As for the whale, its backward bias was a problem, so I replaced that move with the current one.

Did not knew that! Still in the evening, but thanks!

The author, A. M. DeWitt, has updated this page.

I've updated the title and will try to update the svg a little later, I'll be a little less available.

Bringing back the kanjis would be interesting to give a Japanese aesthetic, but I feel that to play a mnemonic skin would be a better alternative from my point of view.

The correct query for opening the preset in Edit mode is &submit=Edit, not &edit=true.

The problem appears to be the fast castling, and now that I think about it, I believe I never implemented fast castling in the betza.txt GAME-code include file. So the entries in the legdefs table that would be interpreted by the JavaScript powering the Interactive Diagram as fast castling are mistaken for something that makes the GAME code crash.

For now I recommend commenting out the four lines that define the fast castling at the end of legdefs, like:

1  1 -1  1     3
//2 99  1  0    88
//   1  9  0    25
//2 99 -1  0    88
//   1 -9  0    25
0);

The King will then not be able to castle, but at least you can continue implementing the other aspects of the variant in the preset. In the mean time I will try to support fast castling in betza.txt. And when I have done that, you can uncomment the lines again.

Much better.

The only improvements I can think of are reintroducing the 3d pieces, naming the game Chu Seireigi instead of Chu Seireigi Shogi (for the same reasons as with normal Seireigi), and maybe having the hand spaces all colored solid brown. But for the latter the wood is colored similarly enough that it doesn't really matter whether you do it or not.

Also, could you update that SVG for the laser cutter? I might want to make a plywood set in the future. But for now, the cutouts I made will do.

https://www.chessvariants.com/play/pbm/play.php?game=Megalomachy&settings=default