sendwithus / battlesnake Goto Github PK

Wait until we're happy with battlesnake-python first, then replicate.

Using a combination of Gulp, Webpack, react-transform, and a few other packages, the frontend dev process should be a lot smoother

Can be something fancy that teams can trigger themselves, or can be admin-only.

We need to lookup and display user metrics described in issue #24

May need to do 10 or 12 snakes for the semi finals in the tournament

Current values are beginner and advanced

Wait until we're happy with battlesnake-python first, then replicate.

Right now GameState.snakes is an ad-hoc dictionary that's accessed and written to all over the place.

We should create a SnakeState object that is json serializable and able to perform basic operations on itself (like moving, eating, dying, etc).

Use d3 to render the state of the board.

If we write something that we're happy with for use in local snakes, hopefully we can add it to battlesnake-python and replicate it across all other starter AIs.

Also add helper methods for serialization for DB and for AI.

The settings that control the app, the database connections, etc. are scattered throughout a couple of files, and some of them are hardcoded:

https://github.com/sendwithus/battlesnake/search?utf8=%E2%9C%93&q=environ

These should be collected into a set of modules in the settings directory, with each setting controlled by an environment variable, and given reasonable defaults.

Public:

• /
• /login
• /register

Types: Normal, Admin, Bounty, Test

• Deprecates the "admin" team name hack
• Only Admins are allowed to set this field

These should be moved into a single module and tested. Currently the requests are scattered through https://github.com/sendwithus/battlesnake/blob/master/lib/game/controller.py

Spawn a golden coin in the centre of the board every x turns. This coin does not count as food. The first snake to collect y coins wins the round.

Described here: https://paper.dropbox.com/doc/BattleSnake-tournament-management-iHaMYYy6FAKmiCrrpRl44

Move the ajax endpoints from bottle -> flask.

Wait until we're happy with battlesnake-python first, then replicate.

• Registration
• Login
• Logout

Leave out authorization for now, just allow anyone to register.

Personally I like https://github.com/coleifer/peewee for simplicity.

Could also use something like SQLAlchemy but seems like more pain than necessary: http://blog.miguelgrinberg.com/post/the-flask-mega-tutorial-part-iv-database

@robbles Any thoughts?

We need to keep track of some gameplay metrics for special achievements during tournaments. These metrics should integrate with the user model and tournaments.

Some things we might want to track:

• Largest snake size
• Total coins collected
• Total kills
• Longest lifetime

Don't want to be able to change details about the team (ie bracket) once the tournament has started.

Allows us to update which bounties are open or claimed during the day by doing a push

Spawn an obstacle on the game board at a random position every x turns. The obstacle should not spawn directly adjacent to any snakes tiles.

It's TOO DAMN HIGH BIG

Maybe some functions can go onto the snakes themselves. Many constants!

Wait until we're happy with battlesnake-python first, then replicate.

Current lib.ai.calls assumes success in all cases. We need to verify that responses return 200, else notify of the error.

User registration DB can be stored separately from the games db so the latter can be reset easily. Plan to use some hosted postgres somewhere.

Nice to have.

The parameters and logic for these will likely need to be changed to support:

• the new user models
• the updates to the client protocol
• new features in the UI?

https://github.com/sendwithus/battlesnake/blob/master/lib/server.py#L37

This should include all the routes the front-end will need, such as teams, users, passwords, etc. and have basic documentation for all routes, their required parameters, and response formats.

Right now lib.ai.calls do not enforce request timeouts.

Decrease the amount of health restored by food by some amount after some number of ticks. For example, every 5 ticks decrease the amount of health restored by 10%.