Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Game Server #60

Open
2 of 10 tasks
ForNeVeR opened this issue Jan 6, 2024 · 0 comments
Open
2 of 10 tasks

Game Server #60

ForNeVeR opened this issue Jan 6, 2024 · 0 comments

Comments

@ForNeVeR
Copy link
Member

ForNeVeR commented Jan 6, 2024

(Excerpt from #29.)

Server should provide HTTP API capable of:

  • register a new game

  • query game list

  • join a game

    • When joining the game, server sends to the client a game key that should be used to schedule turns and query the game state.
  • schedule the game turn

    • When scheduling a turn, each client sends to the server their shot power and direction parameters.
    • When all the players in a game have been scheduled their turns, server simultaneously performs the turns.
  • query the state of the game

    • When the client queries the game state, server sends the game map and the shot/direction history for each player. Shot information also contains a coordinates where the shot has been exploded and information whether any of players was hit by the collision.
  • Each game should have a round timeout. If any of the clients haven't scheduled their turn in time, their shooting phase should be skipped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant