Ratings & Comments

I think this is a very good way to present a group of variants that is so closely related. But I still have a few suggestions for further improvement:

The gatable pieces start in the piece table, but this table starts closed, and it might not occur to the reader to open it. You can force a piece table that is open from the beginning by including <table id="KevinTable"></table>, e.g. where you now have the KevinList. (Which such an open table you would need to also include enableAI=2 in the diagram definition to keep the AI available.)

The board uses a square size 35x35, because that is the I.D.'s default, and you did not specify a size in the initial Diagram. But then you use 50x50 piece images. This is no problem, as betzaNew.js scales the images to fit the board size. (Unlike betza.js, which would do the opposit.) But this makes the piece table, which does not have such scaling, look unnaturally large compared to the board. Which would become all the more obvious when you would always display them side by side. You could cure that by using the alfaeriePNG35 set. (Or put squareSize=50 in the initial Diagram, but then board and piece table might be too wide to display side by side.)

Actually I like the way you solved the placement issue in the GC preset (gatable pieces starting in the center of the board) better than dragging the pieces from the table. But the I.D. doesn't allow it! Even though it would allow illegal moves in general, it does not allow moves to 'hole' squares. Perhaps I should allow those too? Or at least allow those for virgin pieces on the central rank(s)?

Instead of writing "choose your desired diagram" I would say "choose the desired setup". You should add some instructions for how to place the Griffon / Falcon / Manticore too before starting normal play (and opening the AI panel), especially if these come from the table. I guess I could have the I.D. suppress the AI from replying to moves that were not at least pseudo-legal (i.e. to non-highlighted destinations). Then it would not matter when you opened the AI panel.

I think it is site policy to have pages that only look acceptable for viewers with JavaScript switched on. So I think you should at least provide a static image of one of the start positions (and perhaps of all three), within <noscript> tags.

[Edit] I now made the proposed changes to the Diagram script. So it should be possible to start the gatable pieces on the central rank.

Since I can’t insert third-party links in the game description, I’ll do it in the comments. shogitter.com - https://shogitter.com/ Description and online game Mini-Shogi Gold and Silver: https://shogitter.com/rule/5%E4%BA%94%E5%B0%86%E6%A3%8B%20%E9%87%91%E9%8A%80

Now when I try to move in any game other than secret intelligence chess it says You may not move one of your opponent's pieces or similar

@fergus I am playing a copper pocket shogi game, and when you play against another person there is a preview button and a confirm button. It seems to me that when you press the confirm button I am getting error messages in the "post move section of the code". If I had to guess the variable dollar moved is either not getting populated or it is getting populated in a different way. If I had to guess, when you get to the confirm button the variable dollar moved contains the previous move, and not the preview move. If you want we could play a shogi game so that you can see what I mean. Jim.

*** you fixed it thank you.

Now when I try to move in any game other than secret intelligence chess it says You may not move one of your opponent's pieces or similar

I added some new code today for which I neglected to include $nopreview as one of the conjuncts of the condition, figuring that it wasn't necessary to do that. But apparently it was necessary, for adding it allowed making a move to work properly. The code is supposed to change $submit from "Send" to "Preview" when $moves is empty, and it looks like it was doing that when a player was confirming a move. So now it looks like this:

if ($nopreview && empty($moves) && ($submit == "Send"))
    $submit = "Preview";

This was in conjunction with using the Test rendering method to test changes to movepiece.js that would prevent moves started by clicking on an empty space when $nopreview is true, as allowing this type of move could cause moves to be accidentally made, and when $nopreview is true, they can't be undone without editing the log and the database.

There is now the issue of whether any logs were damaged by this bug and are in need of repair. [EDIT: As far as I can tell, this bug stopped moves from being recorded, and the recent logs all seem fine. But if I'm wrong, let me know.]

@fergus, one of our games is stuck. The error message is:

Syntax Error on line 396

MOVE: @ f2-f1 is not a valid expression, because @ is not a recognized piece, coordinate, command, or subroutine.

Drawish positions in the sense that there are conditions arise for repeating the position. Yes, there is sennichite, but nevertheless... I meant drawish = boring

That is amazing! Thanks! How can I implement it inside the main body of the page? Just thinking about those who may access it from their smartphone, which are very unlikely to check out the comment section!

I tried to recreate the same Interactive Diagram with the Betza notation you used but I got some troubles with the pieces' image... How do I get to know their filenames?

Yeah I’ve found a time to finish writing this, so it’s ready, please review it.

Please review this page.

Please review this page.

Also how to enlarge the list of non-English pages which are MS rather than games’ pages?