Single Comment

It occurred to me that the problem I was having with king moves might be because I was setting after in a for loop but not resetting it to false before the next piece was evaluated. Changing that does seem to solve the problem. There might still be better ways to do this with the fairychess system.

I do like the idea of having a non-displacement capture entered with only one click on the target piece because that's the easiest way I can see to disambiguate between a capture and a non-capture in cases where both would result in the moving piece landing on the same destination. The difficulty I have with that is making the notation work with it, since if I record the extra move, it isn't considered legal in some situations.