Skip to content

US Basic pong #2

@codastream

Description

@codastream

Description

user story : As a user, I want to so that [benefit]

Acceptance criteria

  • user can start a game with another on same machine
  • paddles can be controlled with WASD and arrow keys
  • collisions with playground make the ball bounce
  • scores are displayed
  • match end when (score reaches ?)

Error handling

  • when a player leaves the game
  • when a player attemps modifying game parameters (ball position, ...) through the browser
  • when latency is low (3G connection on Chrome devtools)

Additional context (screenshots, links, ...)


Priority and estimates

priority :

  • low (not planned)
  • medium (add in next sprint)
  • high (add in current sprint)
  • critical (add in current sprint top priority)

estimate : ? story points


Definition of done

  • Manual tests are written in doc
  • Manual tests are passing
  • Documentation is updated (in code and / or wiki)

Subtasks (if applicable)

  • Define a "protocol" and json structure for each event : game start, game end, ball move, paddle move, point scored, ... + message frequency
  • Make WS API
  • Handle in frontend through Canvas API or external lib (p5.js ?)

{
  "type": "paddle_move",
  "data": {
    "player_id": "player1",
    "y_position": 250
  }
}

Sub-issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    featureNew feature or request

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions