shtwzrd / battlechat Goto Github PK

User story

As a Stakeholder,
I would like to be sure that the server can handle at least 16 simultaneous games,
so that at least 32 people can play Battleship simultaneously

• #21

Currently, the root directory of the application returns Not Found. The index page, used to queue into a game, should be served up when user HTTP GET to /

User story

As a Player,
I would like to be able to place my Battleships at the start of the match,
so that I have control over the arrangement of my fleet.

• #18
• #20
• #21
• #22

User story

As a Player,
I would like to have the ability to communicate with my opponent,
so that I can say rude things to him.

User story

As a client-side developer,
I would like for the server to return informative error messages when I issue requests that cannot be honored,
so that debugging front-end development is not opaque.

The client needs some understanding of what qualifies as a valid placement of battleships, so that it can provide the user with immediate feedback about invalid placements, or disallow them entirely, allowing for a better user experience.

This also prevents the server from having to validate individual ship placements all the time, reducing load.

User story

As a Player,
I would like to be able to ignore the other player’s chat messages,
so that they can’t hurt my feelings.

User story

As a Player,
I would like the possibility to give up(forfeit/surrender) a match,
so that I'm not forced to play through a one-sided match.

Figure out what the data looks like for the models sent over the wire

Needs:
Ship-placement models (sent Client to Server)
Firing models (sent Client to Server)
Valid firing locations (sent Server to Client)
Ship listings (sent Server to Client, at start of placement phase)
Game status messages (sent Server to Client, to inform Client of placement versus playerX firing turn, player Y firing turn, player X win, player Y win, etc)
Chat messages (sent Client to Server, then Server to Clients)

User story

As a Player,
I would like there to be a time limit on moves,
so that I don’t have to wait til the end of time for a slow opponent.

User story

As a Player,
I would like to be notified when I win or lose,
so that I know when the game is over.

User story

As a Player,
I would like the game to respond to my actions in less than 2 seconds most of the time,
so that the game feels responsive and not frustrating.

• #20

We need to represent the data within a game session. We diagramed the object model on a whiteboard and came up with the following classes:

Game State
    Board
    Player
        View
        Fleet
            Ship

@iensenfirippu is assigned.

User story

As a Player,
I would like to be able to rotate a ship I place,
so that I can hide my submarines even better.

User story

As a Player,
I would like to see a log over the moves made,
so that I can keep track of my enemy's actions.

Configure Spark to render mustache templates

@WarreQ is assigned.

User story

As a Player,
I would like assurance that only one player can fire at a time,
so that the rules of the game are enforced.

User story

As a Player,
I would like to be able to easily choose a target to fire at in the combat round,
so that I have control over where my fleet fires.

The server needs to maintain a collection of sessions.

When a player joins a game, there are two possibilities:

• there is a session with only one player connected to it. In this case, the player is connected to that session, which is then considered filled.
• there is no unfilled sessions, in which case a new session is created and the player is connected to that one.

The server should render the HTML client-side for the initial state of the game, including any databinding necessary for the client-side.

The chosen templating language is Mustache, so the template should be defined in that.

@ThorOfDoom is assigned.

• #24
• #25

User story

As a Player,
I would like to be able to access the game via my web browser,
so that I can easily play from anywhere, without needing to install any special software.

• #16
• #17
• #23

When on the root page, the player should be able to press a button or similar that allows them to queue into a game.

This should issue an HTTP POST to /, which returns the Battleship game page and redirects the user's browser there.

The server-side code needs to implement domain knowledge of what a valid ship configuration looks like.

The rules are as follows:

• A configuration consists of 4 ships
• Ships are 1-unit wide
• A fleet contains ships with exactly one ship with 2, 3, 4 and 5 units in length
• ships may be placed horizontally or vertically
• ships may not intersect one another
• all portions of a ship must be located within the game grid
• #26

When a session contains two people, the server should send a message to both players that the game is beginning and the server will then become receptive to ship placement commands.

User story

As a Player,
I would like to be able to see where my shots have hit the enemy,
so that I can keep track of the enemy ships my fleet has hit.

User story

As a Player,
I would like to be able to see where my fleet has already shot at,
so that I can keep track of where to shoot next and avoid wasting shots.

Make a plain html page to test the client-side code on, for quicker iteration in UI design and ease of client-side code testing.

@TheMightyMarm is assigned.

When the client has finished placing their ships onto the board, the configuration of ships should be POSTed to the server (via /session//placement or similar), and the server should return HTTP Status Code 200 if it's valid or 400 if invalid.

If the configuration is valid, the server's gamestate should be updated accordingly.

• #19