The problem with using nN as a separate move is that this move will also be available when the distant N2 square does contain an enemy piece, and thus makes the capture optional. The verbal description suggests that the capture should be a mandatory side effect.
I need to fix the text description. It's supposed to be optional.
As it is, moving the Bowman crashes the ID. This probably has to do with the way I implemented n on oblique atoms; I will look into that later.
I did notice this, yes. I'd assumed that it was something I'd done wrong, but I'll give you time to work on that, then recheck the move tomorrow.
[F?fW3] or even [F?fsW3] do not work (yet). The bracket notation, which strictly speaking is not XBetza but Betza 2.0, is still in development, and the ID only implements it in the most rudimentary form. (Where it ignores the direction implied by the atom of a continuation leg, purely relying on the directional prefixes, and only allows range 1 or infinite.)
I'll figure out something else to deal with the Wizard's move, then. (It's supposed to be blockable only along the given path.)
I need to fix the text description. It's supposed to be optional.
I did notice this, yes. I'd assumed that it was something I'd done wrong, but I'll give you time to work on that, then recheck the move tomorrow.
I'll figure out something else to deal with the Wizard's move, then. (It's supposed to be blockable only along the given path.)