@H.G.: There seems to be something wrong with my Vanguard game. I'm not sure whether it's my coding or yours, but I'm getting the list of legal moves, and the rifle capture I'm trying to do isn't among them; it's not letting me do my move.
The move was amongst them, but screwed up as h12-#to; @-i10. This problem was caused by the fact that the second leg of the rifle capture was marked as an 'iso' leg; apparently the ID you produced the code from had defined this move as caibN instead of the correct cabN. Since i in a continuation leg means 'as many leaps as the preceding rider leg, and N is not a rider atom, this produced an undefined value for the destination square. The ID is apparently able to handle that, but the GAME code wasn't. I made it resistant to this error by defaulting the number of leaps in the latest rider leg to 1.
Unfortunately this uncovered another problem, in the JavaScript for move entry. The move now shows up in the 'legalList' as h12-h12; @-i10. That is correct, but the script expects the second click to go on the destination, but cannot handle the case where the destination is equal to the origin. (This collides with the normal function of a second click on the selected piece, to deselect it.) The desired clicking sequence here would be h12, i10.
So I will have to redesign the move-entry script to handle these kind of moves. In the mean time you should be able to continue the game by typing the move, I expect.
The move was amongst them, but screwed up as h12-#to; @-i10. This problem was caused by the fact that the second leg of the rifle capture was marked as an 'iso' leg; apparently the ID you produced the code from had defined this move as caibN instead of the correct cabN. Since i in a continuation leg means 'as many leaps as the preceding rider leg, and N is not a rider atom, this produced an undefined value for the destination square. The ID is apparently able to handle that, but the GAME code wasn't. I made it resistant to this error by defaulting the number of leaps in the latest rider leg to 1.
Unfortunately this uncovered another problem, in the JavaScript for move entry. The move now shows up in the 'legalList' as h12-h12; @-i10. That is correct, but the script expects the second click to go on the destination, but cannot handle the case where the destination is equal to the origin. (This collides with the normal function of a second click on the selected piece, to deselect it.) The desired clicking sequence here would be h12, i10.
So I will have to redesign the move-entry script to handle these kind of moves. In the mean time you should be able to continue the game by typing the move, I expect.