I don't get it. The Diagram is preloaded with a long game, which seems to consist exclusively of illegal moves. When not shown in isolation something goes disastrously wrong (probably because it then uses betzaNew.js from a later Diagram in the Comment listing), and Kings appear everywhere.
What is the purpose of all the holes? Why iiK?
The Diagram as defined would not do what the title suggests: check has no effect on its ability to move at all. It can move from e1/e8 even when in check, and cannot move without capture elsewhere even when in check.
I also don't understand what it has to do with Shatranj...
[Edit] OK, I see: the pre-loaded game tries to capture all the Kings. For some reason this doesn't work with betzaNew.js. You try to make use of the fact that initial moves on royals are forbidden when in check. Inventive, but awful.
[Edit2] Pre-loading games doesn't appear to be Diagram-specific, so it tries to pre-load the wrong game when not viewed in isolation.
[Edit3] The latter is now fixed; it was caused by the fact that the game specified with moveList was loaded with a delay, like it was pasted, but by that time another Diagram on the same page could already be the 'active' one. The script now first sets the active Diagram to the one it uses the move list of.
I don't get it. The Diagram is preloaded with a long game, which seems to consist exclusively of illegal moves. When not shown in isolation something goes disastrously wrong (probably because it then uses betzaNew.js from a later Diagram in the Comment listing), and Kings appear everywhere.
What is the purpose of all the holes? Why iiK?
The Diagram as defined would not do what the title suggests: check has no effect on its ability to move at all. It can move from e1/e8 even when in check, and cannot move without capture elsewhere even when in check.
I also don't understand what it has to do with Shatranj...
[Edit] OK, I see: the pre-loaded game tries to capture all the Kings. For some reason this doesn't work with betzaNew.js. You try to make use of the fact that initial moves on royals are forbidden when in check. Inventive, but awful.
[Edit2] Pre-loading games doesn't appear to be Diagram-specific, so it tries to pre-load the wrong game when not viewed in isolation.
[Edit3] The latter is now fixed; it was caused by the fact that the game specified with moveList was loaded with a delay, like it was pasted, but by that time another Diagram on the same page could already be the 'active' one. The script now first sets the active Diagram to the one it uses the move list of.