WAITING_FOR_PLAYERS
PLAYER_TURN
TURN_IN_PROGRESS
FINISHED

Maybe a <group> for specifically for tiles and another for decorative information. The entire map settings should have an height/width or aspect

Happens during state WAITING_FOR_PLAYERS

• Allows player to change name and set a color
• Route should be get@/game/{id}
• View partial will be games/confirm.haml
• Fork the games/index.haml to show different partials depending on the game state
• After submit, verify if each player is confirmed

Once all players have confirmed:

1. Run the map build to allocate player starting positions
2. Game state changes to PLAYER_TURN

For instance, post@/game/new should pass through a series of validation checks before creating a new Game instance. How do we use validation to cover our bases for situations like, users[] must be >= 2 in length, all users must have account, no duplicate ID's etc.

Air drop: move units from one tile to any other tile (connected or not)