I now fixed the FastCastle routine in the betza.txt include file, so that it only generates the move if the King is still virgin. As it was it only tested that for the Rook. Normally the presence of an i in the XBetza castling definition would automatically suppress the move, but because of the way I encoded fast castling in betza.txt the original modifiers are no longer available in the preset. But I suppose it is safe enough to assume there will never be any need for a fast castling for a non-virgin piece.
This would have solved the problem in your game, because only one of the generated moves would have matched your K h10-i10 input. It does not solve the general disambiguation problem yet, when a virgin King would attempt a single step. This problem could also arise with O1 normal castling. I suppose 'capturing' your own Rook could be used to enter the castling, in that case.
I now fixed the FastCastle routine in the betza.txt include file, so that it only generates the move if the King is still virgin. As it was it only tested that for the Rook. Normally the presence of an i in the XBetza castling definition would automatically suppress the move, but because of the way I encoded fast castling in betza.txt the original modifiers are no longer available in the preset. But I suppose it is safe enough to assume there will never be any need for a fast castling for a non-virgin piece.
This would have solved the problem in your game, because only one of the generated moves would have matched your K h10-i10 input. It does not solve the general disambiguation problem yet, when a virgin King would attempt a single step. This problem could also arise with O1 normal castling. I suppose 'capturing' your own Rook could be used to enter the castling, in that case.