Board reports legal moves after drawn position

To reproduce, use the code snippet below for MyBot and play g1 to g3, then shuffle the rook back and forth. The computer should do the same in the opposite corner, and a repetition draw will (correctly) occur after a few moves back and forth.

public class MyBot : IChessBot
{
    public Move Think(Board board, Timer timer)
    {
        Move[] moves = board.GetLegalMoves();
        Move moveToPlay = moves[0];

        board.MakeMove(moveToPlay);
        if (board.IsDraw())
        {
            System.Console.WriteLine(
                "Number of legal positions from drawn position: {0}",
                board.GetLegalMoves().Length
            );
        }
        board.UndoMove(moveToPlay);

        return moveToPlay;
    }
}

Doing so produces the following output:

Launching Chess-Challenge version 1.13
Number of legal positions from drawn position: 19
Number of legal positions from drawn position: 20
Number of legal positions from drawn position: 19
Game Over: Repetition

There should be no legal moves following a draw, as the game has ended. Further, the bot misreports that its next move will be a draw twice too early, but I think https://github.com/SebLague/Chess-Challenge/issues/170 deals with this already.

[WorstWizard]

A simple tree search (the way I’ve implemented it for instance) will usually only evaluate the state of the board at the leaf nodes. The easiest way to do this is to get a list of legal moves, and then recursively evaluate on the board state following those moves.

With the current behaviour, you would have to check whether the board is a draw at each internal node if you don’t want to search an invalid state space, rather than just the leaves. Since we’re constrained on token space in this challenge, this absolutely matters. Whether or not it is intended behaviour is up to @SebLague of course, but the current behaviour seems unintuitive, it’s certainly not documented.

Move generators don’t concern themselves with the 50 move rule or repetitions, that’s not what they’re made for.

The Board class includes a check for whether the current state is a draw, because it knows whether or not it is (or at least it should). So it should already know that the moves it’s generating are bogus. It’s not just a move generator, it already tracks this information, just a matter of including that in its knowledge of move legality.

[WorstWizard]

That’s a perfectly valid point! Wasn’t aware that it was optional per actual rules. Within this version of the game, it is an instant draw, so I’ll leave the issue open for now as it could still be a convenience feature.