H. G. Muller wrote on Tue, Nov 7, 2017 08:06 PM UTC:
Hmm, there is a small problem that I had not foreseen. If a player makes a capture, and it gets refused, this cannot be done by simply making the reverse move: the captured piece will not come back. I can solve that by altering the game into a drop game, with unlimited pieces in hand, so that you could drop the captured piece back. This is a bit cumbersome, though. Perhaps it is better if we tell the opponent in advance when we are going to refuse a capture. (E.g. through the chat.) This will also speed up the game, as we can immediately do a move that will not be refused, rather than having to wait an extra roudtrip.
E.g. after the already played 1. e4 c5 2. Qh5, I expect the computer to play 2... d3 (to protect the c4 Pawn). Then I would say "3. Qxf7+ {refuse 3... Kxf7}", so black can immediately play Kd7 (the only legal alternative, which I now cannot refuse, as I already used up my refusal pre-emptively). Then I can continue with "4. Qxd8+ {refuse 4... Kxd8}", etc.
Hmm, there is a small problem that I had not foreseen. If a player makes a capture, and it gets refused, this cannot be done by simply making the reverse move: the captured piece will not come back. I can solve that by altering the game into a drop game, with unlimited pieces in hand, so that you could drop the captured piece back. This is a bit cumbersome, though. Perhaps it is better if we tell the opponent in advance when we are going to refuse a capture. (E.g. through the chat.) This will also speed up the game, as we can immediately do a move that will not be refused, rather than having to wait an extra roudtrip.
E.g. after the already played 1. e4 c5 2. Qh5, I expect the computer to play 2... d3 (to protect the c4 Pawn). Then I would say "3. Qxf7+ {refuse 3... Kxf7}", so black can immediately play Kd7 (the only legal alternative, which I now cannot refuse, as I already used up my refusal pre-emptively). Then I can continue with "4. Qxd8+ {refuse 4... Kxd8}", etc.