You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The whole game is saved into db with its history as a string (not optimal from the data structure perspective but veeery convenient for debugging and for tests); this structure also contains a lot of data about the game including:
size
current player
the whole game history
1 0 0 0 2
3 6 0 5 4
7 0 0 0 0
0 0 0 0 0
Assignment H: history
implement ctrl+z
implement a page with a game history report like you'd do with a chess game [not so detailed though cause we don't save time]
improvement: show this history as a list of readonly game fields, scaled down
improvement: show this history as one readonly game field, but with a "play/pause/stop" button and a slider, like a player; it'd play the recent game as a "video" [again without consideration of how long a turn took]
Assignment S: split screen
implement a game mode when two players play both against own bot
it look like a split screen game, where a player A sees their screen at the left, and their screen is "interactable". Player A also sees the screen of player B at the right, as read-only, and gets updates about player B turns
Improvement: Player B see their screen at the left too (that'd you see how some Tetris multiplayer games would behave) and Player A's screen read-only at the left side
The text was updated successfully, but these errors were encountered:
The whole game is saved into db with its history as a string (not optimal from the data structure perspective but veeery convenient for debugging and for tests); this structure also contains a lot of data about the game including:
Assignment H: history
Assignment S: split screen
The text was updated successfully, but these errors were encountered: