Commit Graph

11 Commits

Author SHA1 Message Date
387125e828 Introduce check if the game has ended (checkmate/stalemate) 2024-01-17 17:38:06 +01:00
ae3e73f711 Another step towards allowing reconnections
1. Implement thread-safe ringbuffer for websocket messages

This implements a ringbuffer that is used to decouple the raw websocket
connection from the messages that the game handler handles.

2. Change websocket handling

With this commit, we stop waiting for the websocket connection to be
established before the game starts.
Now, the Connection type is responsible for waiting for the websocket
connection before writing.

Some bugs are still happening:
	1. The rejoining client is not told the state of the board
	2. Invalid moves are not handled by the client (not sure why though)
	3. The still-connected client should be told, that the opponent
	   disconnected. Then the client should show the passphrase again

3. Introduce method to send status of board and player

4. Reconnect works (kind of)

With the right changes in the client, the reconnect works (but only for
the first time).

WARNING:
At the moment, we will create a new player whenever connection wants to
join a private game. This will also clear all the disconnect callbacks
that we set in the player.
2023-12-09 21:00:52 +01:00
51d959b01f code upkeep 2023-10-12 21:03:12 +02:00
a550ad9cdc Remove server.go and move type. 2023-09-24 01:18:06 +02:00
9fbffc61f9 Add position to websocket message. 2023-08-14 00:05:47 +02:00
9c7bdf357d Make en passant and castling work. 2023-07-05 21:15:01 +02:00
9793c37582 Many many changes 2023-06-25 16:11:29 +02:00
7f206b15fe Pieces are now an interface and starting to enforce rules. 2023-06-20 23:53:54 +02:00
060ac8ad9e Add groundwork for checking rules. 2023-06-12 22:32:31 +02:00
7544bf0563 Refactor some of the game handler code 2023-06-08 20:20:37 +02:00
e90fb7a0dc Transform communication of moves to api types. 2023-06-02 23:41:43 +02:00