konkit / tankgame Goto Github PK

Handling shooting on backend side - accepting event, creation of missle, broadcasting missle creation to all players.

Splitting the game to different rooms, where game is played independently.

Backend does not detect bullet-tank collisions properly. IMO tank has to be represented by a rectangle.

Change them to reflect game status in better way

Should be handle in similar way as #2

I would remove blank spaces from events name, e.g.
"move player" -> "player:moved"
and listener for this event onPlayerMoved

Player vs Map ( and world borders! ),
Player vs Bullet,
Player vs Player ?

We should have data structures that represent tasks positions and handles tanks behaviour.

Example usage

tank = new Tank({ login: "maciek", coordinates: [2, 3], life: 3, points: 5 });
tank.moveUp().then(function(tank) { // moveUp returns a promise that is resolved after server acknowledge move
    // tanks.coordinates == [2, 4]       
})

Should be handled in similar way as #2

We need to get an event when someone destroys player's tank. Event will be send only to destroyed player.

Keeping track of player positions, updating all players with players positions.

At the moment there are no possibility to play on 2 clients. Try to set '*' in HTTP config

Handle collision Tank-tank and tank-bullet

Keeping track of players' score

Sending current player position
Updating all players with other players positions

Players is not dead after fitrst bullet hit

Updating bullets positions
Updating state of static map elements.

Player connected, disconnected, etc.

At the moment when player disconnects his tank is left on the map - it should disappear.

We need an entity that abstract keyboard i.e. listens to keyboard keys press and emits appropriate events.

Usage example

k = new KeyboardListener();
k.on("up:arrow:pressed", function() {
  // handle up arrow pressed
});

The only responsibility of the canvas should be to take data structure and render it.
Canvas should not mutate its state itself! It might trigger some events if needed (e.g. if tank is about to collide with a wall)

eg. exit game and display some text - "game over"

Low priority task for user authentication, signing up, signing in etc.

Preferably using socket.io mechanisms or something similar.
Player movement, shooting, turning around time intervals should be constant and not depending on users' requests frequency.

We should deploy app to heroku to be able to present app easily, what do you think?

Issue was primairly fixed in #37 , but it still is not perfect.

It needs to be checked if there is any way to improve that.