cygni/snakebot

snakebot's Issues

Enable Cors for login service

Implement support for cors in login service.

Send event for tail-nibble

Gameplay: Fixed starting positions

Currently starting positions for snakes are random. One snake can get an advantage by getting a favourable starting position. For instance if no other snakes are near by.

Suggested solution:
Create a fix set of starting positions on the map. Randomly assign bots to these positions.

On game start send link to web gui

Send a link to the web gui to all clients when a game starts (only training mode) so that the game can be started and viewed there.

Both snakes dies when eating each other's tail

If two snakes eat each other's tails it seems the both die. Reported by David Schlyter.

Implement ping/pong to keep clients alive

Let all clients send a ping over the websocket every 30 secs. The server replies with a pong and thus keeping the socket alive.

Statistics

of:

• number of served players
• spread of client types (computer language)
• spread of operating systems
• wins per player name

Clojurescript heartbeat

Clojurescript ClientInfo

Webclient: Send starttournament to server

Authentication system

• Invalidate the login token after xx minutes of inactivity
• ability to add users via docker environment variables
• ability to add users via configuration file

Game area in webclient only visible if the game area is square

If a game area is rectangular (e.g. 50x25 as currently is checked in in the JS-client), a game can be started but the game area won't be drawn.

Webclient: Create a loginpage

Create a loginpage to access tournament settings

Analyze GC settings

It seems that sometimes the whole server stops. This might be because of some stop-the-world GC happening. Also, clients are being defaulted to last direction move because responses are not being accepted in time. Could be GC-related as well.

Webclient: Make server websocket adress configurable

Now the adress to the websocket is hard coded in TournamentStore.js and GameStore.js. For deployment we need this adress to either be specified as an environment variable or a configuration file.

Color coding in Highscore list javafxclient

It would be great if the snakes presented in the highscore list was color coded in the same color as the snakes are drawn!

Webclient: Listen to response from server onServerCreated

Hack and resilience testing

There may be issues regarding misbehaving clients.
We need to test what happens when clients behave in a bad manner.

Example of things to test:

• A client sends a RegisterMove before the game has started
• A client sends a stream of constant RegisterMoves
• A client tries to register twice under different names
• A client changes the parameter receivingPlayerId in the message
• Is it possible to DDOS the server and cause all other clients to default moves?
• A client sends RegisterPlayer in the middle of the game
• A client sends garbage
• ... and whatever crazy stuff that might happen

Please create issues for whatever crashes you see. If possible attach server logs and client logs.

MapUtil - positions should be private

Webclient: receive tournament bracket from server

Webclient: connect createTournament to backend via WS

GameHistorySearchItem

Add number of gameticks in game.
Add list of interesting events during the game (tail-nibble, head-to-head-crash, head-to-body-crash, head-to-wall, head-to-obstacle etc).

Measure time for movement to after confirmation that MapUpdateEvent has been sent to all

The implementation now puts the MapUpdateEvent on the outgoing eventbus to each client and then directly starts the countdown.

Better to start the countdown till after we have confirmation that the messages has at least been sent. But to wait for a real ACK from all clients might be too much (and also difficult, and could be misused)

Implement tournament mode

• Add request/response classes for webclient to administer tournaments.
• Implement TournamentManager

Logging

Enable some suitable logging that doesn't disappear when the docker container restarts.

Logic for sending gameSettings to server (as Json?)

New scheme for winner

• Let the last snake alive win, regardless of points accumulated
• The other positions are calculated by points
• If two or more snakes have the same amount of points let the one with the most of:
  PointReason.GROWTH,
  PointReason.NIBBLE,
  PointReason.CAUSED_SNAKE_DEATH,
  PointReason.FOOD,
  win in the order described above.

Implement suicide penalty

When a snake kills itself by hitting a wall or itself a configurable penalty is rewarded.

Implement snake protected for N ticks after tail nibble

• Add snake protection scheme
• Add attributes to snake head (and perhaps SnakeInfo) that indicates how many ticks are left under protection

C# - ClientInfo Call

Version 0.0.10 of the server introduces a call to allow collection of usage stats ( #38 ).
The Java client has embedded this call in the BaseSnakeClient class. The call is made when a player successfully registers.
We need the C# client to do something similar.

Send notice to players that are late with RegisterMove

If a player's RegisterMove comes after the specified time limit respond with a RegisterMoveTooLate response.

Obstacles fixed at start of game

Place the obstacles randomly at the start of the game and don't remove or add new ones during game play.

This means:

• Remove options for likelihood of obstacle being removed in gameoptions
• Remove/disable logic for removing/adding new obstacles
• Update the GameAPI

Obstacles in clusters

Add obstacles in clusters of 1x1, 2x2 or 3x3 tiles (square formation).

Can't connect with browser WebSocket

When attempting to connect via a browser WebSocket, the connection fails with the following error:

WebSocket connection to 'ws://snake.cygni.se/training' failed: Error during WebSocket handshake: Unexpected response code: 403

This happens in all browsers (Safari, Chrome, Firefox), but not in Node. CORS issue perhaps?

Implement ClientInfo message

For statistics it is interesting to know what language, operating system etc a client is using. This is especially good to know the days before a student och client event so we can prepare guides and the correct responsiveness to questions.

I suggest we let clients, at any time, send a ClientInfo message over the WebSocket. This would only be needed once per session and could come at any time but perhaps a good time would be just before a "RegisterForPlay" message.

ClientInfo {
   programingLanguage: "JavaScript",
   OS: "Linux",
   IP: "xxx.xxx.xxx.xxx",
   baseClientVersion: "0.0.8"
}

Javadoc for API classes

It's important to be able to understand what messages from the server (and to the server) contain. A javadoc site for these classes should be a good start.

Webclient: Create a settings page that maps all gamesettings.

C# client heartbeat

Arenas where real players can meet and play

Bots in training quickly get tired of the server bots and want to meet other real players (or several incarnations of itself).

Add a new type of play, called Arena, FightClub or Freeplay, where any players can meet and battle.

• Any player in the same arena should have the possibility to start a game
• Arenas may be given names so that other players can find each other

Remove random obstacles, add a specified number at start of game instead

The random obstacles adds a measure of randomness that could kill a snake if unlucky. This happens for example if an obstacle is spawned so that a snake becomes locked in.

Better to add a random amount of obstacles at game start that stay there for the rest of the game.

Better versioning and build-date info

Increase available info at http://snake.cygni.se/info to include:
git hash
version
build number
build date

Add game type to play multiple rounds using the same players

You enter the number of rounds you want to play in the tournament and get a summary of the score after the last round. This is needed when there are not enough players for a full tournament.

Webclient: draw tournament bracket

Documentation: sequence diagrams for client <-> server communication

There are a lot of messages going back and forth during a game/tournament. It would be good to document this flow, especially for someone wanting to write a client in an new language.

Increase test coverage in world transformations

There are several transformation classes not under test right now. See module domain and in package se.cygni.game.transformation.

Save/search/fetch games

Save all game states (per gameID) in a mongoDB.
Ability to search by gameID, participating player(s) and date
Ability to stream a whole game by gameID

Preset boardsize

For simplicity we have decided to use only one size for the game world.

46x34

This means:

• remove world size from all API:s
• preferably we want the service to function even though a user uses the old API.

Game map dimensions should be enumerated or represent units of 25

Given the decision that a map dimension only can be a multiple of 25, this should be more obviously reflected in the client code. E.g. instead of integer-input, enumerate like for example:

small(25)
medium(50)
large(75)
x-large(100)

If we don't want to limit ourselves like this (e.g. it should be possible to have a 475x650 board) another option is to work with size units (integers). 1x1 would be like 25x25 works now, 4x4 would make it 100x100, 2x5 is 50x125 etc...

Send GameFeatures at GameStartingEvent

Now the GameFeatures are sent to the clients with the PlayerRegistered event. Better to send the GameFeatures on every start of a game. This is so that we have the opportunity to change settings between games.

Remove suicide negative points

This setting is not applicable when the last living snake wins.