CIT 594 Assignment 12: Coin Grabber (Scala)
Spring 2015, David Matuszek
Because part of the goal is to teach minimaxing, I wanted a game to which this technique could be applied. Because this is a first Scala assignment, I wanted to find a very simple game to implement. I considered Mancala, but decided against it. In the end, I just designed a game for this purpose, which I call Coin Grabber. It probably isn't going to win any "best game" prizes, though.
The game is played on a 5x5 board, arranged like this:
Here are the rules:
The human player plays by entering one of the letters
R, or their lowercase equivalents, or any word beginning with one of those letters (such as
duck). The computer player indicates its move by printing one of the words
right. The board is printed at the beginning and end of the game, and after each computer move.
The goal is to write a program that uses a minimaxing strategy to beat, or at least challenge, the human player. Use an easily-modified constant to set the amount of lookahead. The use of alpha-beta cutoffs is optional. The program should not take more than 10 seconds to make a move (on your computer; it's okay if it takes a bit more time on our computers).
Most of the details are up to you. There is an obvious quantity on which to minimax--your money minus your opponent's money--but that isn't necessarily the best measure to use.
Finally: If you would prefer to implement a game of Mancala (using minimaxing), that's okay, too. Since Mancala has many variations, be sure to specify (by a
readme.txt file or a link to a website) exactly which variation you are implementing, and make sure we understand how to run the game and make moves.
Testing is always a good idea, but I don't want to try to squeeze any more into this assignment, so unit testing is not required. If you want to test parts of your program, JUnit tests (yes, written in Java!) can be used. Or if you are really ambitious, you could look into ScalaTest (but be prepared to be overwhelmed by the options).
Grading will probably be as follows, but is subject to change: