vel1khan / pixel-chess Goto Github PK

When castling, the position of the rook piece is not updated on client-side.
Potential fix: Check move flags from chess.js to determine if it is a king/queen-side castle and adapt accordingly on client-side

After pressing the 'Play now!' button this is happening:

So I'm pushing 'Okay' just wondering what will be next. Without any move in the game and the program makes me dumb!

Chess.js requires extra parameters to be fed into .move() for promotion to work. As of now, you can't even move the pawn as it sees the move as illegal due to the missing parameter.

Screenshot taken at a resolution of 1279x647, which corresponds to the browser window not in fullscreen on a 1600x900 resolution screen.
Potential fix: Mess with the positioning CSS and perhaps of the elements around the button.

The timer is desynchronizing after a time.
Potential fix: Update the timer on server side not on client side

When a client receives a turn message, the received array containing the cells that have pieces that can be moved contains some of the same cell numbers repeated more than once as the same piece can have multiple moves.

Not a massive problem but leads to a small increase in bandwidth overhead and client-side processing.