Description (five sentences max.)
I need to describe the life of a game lobby. This should be described by actions available on the backend. These actions should be functions so that it will be easy to later implement them with websockets. This Issue can be implemented over multiple PRs
All possible user actions are defined by the backend.
The game state only exists on the server
The frontend has access to the least amount of information
Acceptance Criteria
The following actions are implemented:
Lobby
[x] Create Game Lobby
[x] Join Game Lobby
[x] Leave Game Lobby
Game
[x] Get a Hand of Cards
[x] Play a Card
[x] Determine whose turn it is
~- [ ] Check Table~
[x] Check playable cards
[x] Check number of cards remaining in opponents hand
[x] Determine the winner of a round
[x] Determine the winner of a game
[x] Get the results of a game
[x] Check which player belongs to what party
[x] Get information on the last "stich"
Out of Scope
Websocket implementation
No special game orders
No callouts
Document optional improvements
Optional. Could lead to a better feature.
Description (five sentences max.) I need to describe the life of a game lobby. This should be described by actions available on the backend. These actions should be functions so that it will be easy to later implement them with websockets. This Issue can be implemented over multiple PRs
Acceptance Criteria The following actions are implemented:
Lobby
Game
Out of Scope
Document optional improvements Optional. Could lead to a better feature.