Building a custom view to play the game Arimaa
In this assignment you will be tasked with building a custom view that will
model and play the game of Arimaa. Arimaa is a game that is played on an 8x8
chess-like board. There are two players (gold and silver) that have 6 different
animal types: one elephant, one camel, two horses, two dogs, two cats, and eight
a
its. The objective of the game is to get one of your ra
its completely ove
to the other side of the board or to completely eliminate your opponents ra
its.
It is possible to capture and remove opponent pieces from the board using
the four designated trap squares on the board. However for this to work a
larger piece must push a smaller piece into one of the trap squares to eliminate
it. Should a smaller piece be adjacent to an opponents larger piece it is rendered
immobile until the larger piece is no longer adjacent.
A more detailed version of the rules of Arimaa can be found here https:
en.wikipedia.org/wiki/Arimaa. It is suggested that you take a read through
this first and if possible play a few games of Arimaa to get a feel for it before
implementation.
While a player can choose the placement of their pieces at the start of the
game we will have a fixed starting a
angement to simplify the implementation.
Be aware that for this assignment you are required to use a single
instance of a custom view class to render the game. If more than one
instance is used you will fail the assignment.
Coding Brackets (80%)
1. Bracket 1 (10%)
• Create a single page layout containing a single instance of your custom view for Arimaa. Bracket failure if more than one instance
is used.
• Create the shell of a custom view that is forced to be square in size.
• Allow a player to make one to four moves during their turn.
2. Bracket 2 (20%)
• Render an 8x8 board with the four trap squares in place.
• Render the initial state of the game which is the following:
-> 8 ra
its on the back row.
-> In the row in front of the ra
its: cat, dog, horse, camel, elephant, horse, dog, cat.
• Maintain a history of the board after every move. If a board has
een seen before do not accept the move.
3. Bracket 3 (30%)
• Add in a UI element to allow a player to _nish their turn and switch
to the other player. If the state of the board has not changed during
the move refuse to change to the other player.
• Enable touch input to accept two touches to make a move. One
touch to select the piece (highlight the selected piece), and one touch
to make the move (highlight the squares that the piece can move to).
All pieces may move one step forward, backward, left, or right as a
move. Ra
its cannot move backward.
4. Bracket 4 (40%)
• Have a UI element to indicate who the cu
ent player is
• Have a UI element to show a message explaining why a turn is not
accepted.
• Have a UI element to reset the game.
5. Bracket 5 (50%)
• If a smaller piece lands next to a larger piece render it immobile.
Should the larger piece move away allow this piece to move again.
• Enable a larger piece to push a smaller piece. This should count as
two moves.
6. Bracket 6 (60%)
• If a piece lands in a trap square remove it unless there is a friendly
piece adjacent to it.
• End the game if a ra
it gets to the other side.
7. Bracket 7 (70%)
• Enable a larger piece to pull a smaller piece this should count as two
moves. A dialog will be useful here to ask if the user wants to move
their own piece only (single move) or pull the opposing piece with it
(two moves).
• Add in an undo feature for the cu
ent turn to undo moves made
during the cu
ent turn before committing.
8. Bracket 8 (80%)
• UI design: well thought out UI and custom view that is easy and
intuitive to use