melvic-ybanez / nostalgia Goto Github PK

Undo button should still work even if both players ran out of valid moves.

We also need to implement a draw system, but that should be in a separate issue.

Implement the three-fold repetition

Implement Piece Square Tables to improve the engine's board evaluation.

This happens when you create a Human vs Computer or Human vs Human game while a Computer vs Computer game is still playing. After the creation of the new game, the human player (White) can’t move and a black square is selected.

One possible reason for this is that the move updates are too fast (since both are level 2) that the computer can still complete the computation before the cancelation of the current move and whole game happens. So when the new game is started, the onSucceeded code still gets executed, leading to changes in the state.

One with a loading bar is even more preferable

We are now using new piece assets from Phobos. We can remove the old assets, except for the white knight since we are using it as the app's icon for now.

Implement the fifty-move rule.

The system should declare stalemate in the absence of a legal move.

Example:
A white pawn going from e2 to e4 should have its back facing the player. A knight moving from g8 to g6 should be facing the player.

This is more difficult than expected because the info on the last move is not preserved in the histories.

One possible solution could be to add support to detect a made move given two boards.

To replicate:

1. Move a white piece.
2. Click on a black piece
3. Undo
4. Try clicking the white piece again.

Expected behavior: White piece should be clickable again
Actual behavior: White piece can't be clicked.

In some cases the it can even cause weird behaviors. For instance, if the black piece you clicked is a pawn, and the white piece happens to be at the end row. If you clicked the white piece again the system will think you are moving the black pawn to the last destination, causing the promotion dialog to appear.