I made a small tweek in betzaNew.js w.r.t. the entry of castling moves, in order to allow handling of free castling (as in this variant). This now requires clicking of the King origin, destination, and then the Rook destination. (Before the Rook origin had to be clicked instead of its destination, which made no sense, as it is always the nearest remaining Rook even if there would be multiple Rooks on the same side that can castle.) Castling moves have 'auto-completion', though, meaning their entry is considered to be complete if the previous clicks already uniquely defined the move. Usually this happens after entering the King move (except for O1 castling), which was why the bug never manifested itself. For free castling usually multiple Rook destinations are still possible with the same King move, though.
Note that there still is no way for specifying free castling in XBetza yet. To make it work for New-Chess some extra scripting had to be included in the page, for generating alternative Rook destinations when a standard castling is encountered.
I also limited the auto-completion of castlings to cases where the King destination is already entered, so that there is no immediate castling if the King is clicked and castling happens to be its only (as sometimes happens in Chess960, when the King starts at f1 and the Rook at g1).
I made a small tweek in betzaNew.js w.r.t. the entry of castling moves, in order to allow handling of free castling (as in this variant). This now requires clicking of the King origin, destination, and then the Rook destination. (Before the Rook origin had to be clicked instead of its destination, which made no sense, as it is always the nearest remaining Rook even if there would be multiple Rooks on the same side that can castle.) Castling moves have 'auto-completion', though, meaning their entry is considered to be complete if the previous clicks already uniquely defined the move. Usually this happens after entering the King move (except for O1 castling), which was why the bug never manifested itself. For free castling usually multiple Rook destinations are still possible with the same King move, though.
Note that there still is no way for specifying free castling in XBetza yet. To make it work for New-Chess some extra scripting had to be included in the page, for generating alternative Rook destinations when a standard castling is encountered.
I also limited the auto-completion of castlings to cases where the King destination is already entered, so that there is no immediate castling if the King is clicked and castling happens to be its only (as sometimes happens in Chess960, when the King starts at f1 and the Rook at g1).