Our vision is to bring together the world's expertise to solve challenging security problems.
The ancient Roman game of ROTA is easy to learn, quick to play. It makes a great game for new recruits that teaches planning ahead and the points of the compass.
No one knows the Roman name for it, but scholars call it ROTA, Latin for "wheel." ROTA boards were painted, scratched or scribbled everywhere that Romans went. It probably kept a lot of bored Roman soldiers busy.
Scholars guess that ROTA is a three-in-a-row game like tic-tac-toe. They have reconstructed the rules based on medieval games that look a lot like it. There is one key difference between tic-tac-toe and ROTA.... ROTA can never end in a tie.
When you complete this challenge, please send a copy of your resume along with all hash values you collected and any code used in the challenges to: email@example.com
I'll explain how to play the game, then you'll get a chance to experience the real game.
Take some time and explore the game of ROTA. Use this time to get comfortable with the rules and develop a strategy for your final challenge. Oh, and that's not a graphic below... it's a playable instance of the game—have fun!
Pssst... By the Way: Really good players of Rota can keep the game going forever.
The object of the final challenge is to play 50 consecutive thirty-move games against our ROTA AI without losing.
To interact with the ROTA web service, GET requests are sent to:
Note: Successful requests (the correct use of placing a piece or moving a piece) must be made within a certain time limit or the session time restarts and a new game must be requested
Use request values to tell the computer what you want to do, for example:
Use the following parameters as reference when interacting with the web service:
Restart a game. In doing so you will create a new game and restart the timer for game length. This request can be made at any point. You must include your email in the initial request to obtain a valid session.
Place a new piece on the board. This request can only be made during the first three moves of each player's turns.
Use the location parameter in conjunction with place with a value between 1-9
Use the move parameter when moving a current piece from one location to another. This request can only be made after the player has placed all 3 pieces on the board. Include both the from and to parameters when moving a piece on the board. The value must be an integer between 1-9.
Returns the current status of the session which includes board status, computer wins, and player wins. This request can be made at any time, but does not reset the timer between successful requests.
Increases the games_won count and resets the moves count. This endpoint will kill a game if it is called prior to a 30 move game.
All web service responses are in a JSON format. Every server response will include the updated game board with the computer's next move if the prior request involved a player move.
Specifies whether the request was successfully executed. If the request did not go through it will fail and an explanation is given in the response data. A success is returned if the request does go through and is properly executed.
Contains the responses data which may include: board layout, computer_wins count, player_wins count, moves count, games_won, and hash (which is given after one hours of continuous play)
The board will be returned as a string, where each position corresponds to a position on the board. Board positioning is as below, where each position has a number 1-9.
- represents an empty space
c represents a space occupied by a computer piece
p represents a space occupied by a player piece
To help get you started, we've included basic Ruby code needed to interact with and solve this challenges.