johnathonnow / alephzero-chess Goto Github PK

Right now check is checked but not chessmate.

The board is not inverted and math is hard.

Right now the WasmBoard is not de-serialized correctly, causing buggy behavior. This should be fixed.

Right now the client duplicates a lot of information about the board. This should be avoided.

it appears you can en passant anytime the pawn you are enpassanting was last to move.

#10, #5, and #6 would all benefit from moves being handled differently.
Instead of asking "is a move here legal?", a Move ticket should be returned if the move is valid dictating what the move does, and if the move is invalid then None should be returned.
This will let us return a Castle stub, an En Passant stub, or whatever other stub as necessary. This will prevent Board from needing to know the details of how pieces move, and will also give us move history for free.

PawnRanks should be generalized into some kind of piece generator, which can take a formula for which pieces should go where. Then the board can contain four piece generators:

1. White pawns, something like (y==1) {"type": "pawn", "color": "white"}
2. Black pawns, something like (y==7) {"type": "pawn", "color": "black"}
3. White pieces, something like (y==0 && (x==0 || x == 7)) {"type": "rook", "color": "white"}; (y==0 && (x==1 || x == 6)) {"type": "knight", "color": "white"}; (y==0 && (x==2 || x==5)) {"type": "bishop", "color": "white"}; (y==0 && (x==3)) {"type": "queen", "color": "white"}; (y==0 && (x==4)) {"type": "king", "color": "white"}
4. White pieces, something like (y==0 && (x==0 || x == 7)) {"type": "rook", "color": "black"}; (y==0 && (x==1 || x == 6)) {"type": "knight", "color": "black"}; (y==0 && (x==2 || x==5)) {"type": "bishop", "color": "black"}; (y==0 && (x==3)) {"type": "queen", "color": "black"}; (y==0 && (x==4)) {"type": "king", "color": "black"}