CS61B, Fall 2014 Project #2: Jumping Cubes(version 3) P. N. Hilfinger

Size: px

Start display at page:

Download "CS61B, Fall 2014 Project #2: Jumping Cubes(version 3) P. N. Hilfinger"

Patience Watkins
5 years ago
Views:

1 CSB, Fall 0 Project #: Jumping Cubes(version ) P. N. Hilfinger Due: Tuesday, 8 November 0 Background The KJumpingCube game is a simple two-person board game. It is a pure strategy game, involving no element of chance. For this second project, you are to implement our version of this game, which we ll call jump, allowing a user to play against a computer or against another person, or to allow the computer to play itself. The basic interface is textual, as before, but for extra credit, you can produce a GUI interface for the game. Rules of Jump The game board consists of an N N array of squares, where N >. At any time, each square may have one of three colors: red, blue, or white (neutral), and some number of spots (as on dice). Initially, all squares are white and have one spot. For purposes of naming squares, we ll use the following notation: r : c refers to the square at row r and column c, where r,c N. Rows are numbered from top to bottom (top row is row ) and columns are numbered from the left. The neighbors of a square are the horizontally and vertically adjacent squares (diagonally adjacent squares are not neighbors). We say that a square is overfull if it contains more spots than it has neighbors. Thus, the four corner squares are overfull when they have more than two spots; other squares on the edge are overfull with more than three spots; and all others are overfull with more than four spots. There are two players, whom we ll call Red and Blue. The players each move in turn, with Red going first. A move consists of adding one spot on any square that does not have the opponent s color (so Red may add a spot to either a red or white square). A spot placed on any square colors that square with the player s color. After the player has moved, we repeat the following steps until no square is overfull or either all squares are red or all blue:. Pick an overfull square.. For each neighbor of the overfull square, move one spot out of the square and into the neighbor (even if occupied by the opposing side).. Give each of these neighboring squares the player s color (if they don t have it already). The order in which this happens, as it turns out, does not usually matter that is, the end result will be the same regardless of which overfull square s spots are removed first, with the exception that the winning position might differ. A player wins when all squares are the player s color. For example, given the board on the left (N = ) in Figure, if Red adds a spot to square :, we get the board on the right after all the spots stop jumping. Distributed under the GNU Public License as part of the KDE project. Copyright 999, 000 by Matthias Kiefer. It was inspired by an old game on the Commodore.

2 Project #: Jumping Cubes Red square: Blue square: Legend: Figure : Example of a move. The board on the right results from Red adding a spot at :. The rules hold that the game is over as soon as one player s color covers the board. This is a slightly subtle point: it is easy to set up situations where the procedure given above for dealing with overfull squares loops infinitely, swapping spots around in an endless cycle, unless one is careful to stop as soon as a winning position appears. It is acceptable, in fact, for you to report winning positions in which the redistribution procedure described above is prematurely terminated, so that some squares remain overfull. For example, if, on Red s move, the board is as on the left of Figure and Red moves to :, then the board will turn entirely red. You are allowed to stop the process of redistributing spots when all squares are red, even though, depending on the order in which you do things, you could end up with the board on the right in the figure. Textual Input Language Your program should respond to the following textual commands (you may add others). There is one command per line, but otherwise, whitespace may precede and follow command names and operands freely. Empty lines have no effect, and a command line whose first non-blank character is # is ignored as a comment. Extra arguments to a command (beyond those specified below) are ignored. An end-of-file indication on the command input should have the same effect as the quit command. clear Abandons the current game (if one is in progress), and clears the board to its initial

3 Project #: Jumping Cubes Figure : The board on the left shows a position just before Red s last move (to :). The board on the right is one possible stopping point for spot redistribution (all squares now being one color), even though the square at : is still overloaded. configuration (all squares neutral with one spot). Playing stops until the next start command. start Start playing from the current position, if not doing so already (has no effect if currently playing). Takes moves alternately from Red and Blue according to their color and the current total number of spots on the board: if the spot count plus the board size is even, it is Red s move, and if odd, Blue s move. quit Exits the program. auto P Stops the current game until the next start command and causes player P to be played by an automated player (an AI) on subsequent moves. The value P must be red or blue (ignore case Red or RED also work). Initially, Blue is an automated player. manual P Stops the current game until the next start command and causes player P to take moves from the terminal on subsequent moves. The value of P is as for the auto command. Initially, Red is a manual player. size N Stops any current game, clears the board to its initial configuration, and sets the size of the board to N squares, where N 0. Initially, N =. set R C N P Stop any current game. Put N spots at row R and column C (see.). P is either b or r (for blue or red,) indicating the color of the square. When N is 0, P is ignored and the square is cleared. N must be non-negative and less than or equal to the number of neighboring squares.

4 Project #: Jumping Cubes dump This command is especially for testing and debugging. It prints the board out in exactly the following format: === r - r r - b - - r - r - r r r r - b r r r r r b b r r r r b b b b r b b === with the === markers at the left margin and other lines indented four spaces. Here, - indicates a neutral square (necessarily with one spot), Nr indicates a red square with N spots, and Nb indicates a blue square with N spots. Don t use the two === markers anywhere else in your output. This gives the autograder a way to determine the state of your game board at any point. It does not change any of the state of the program. seed N If your program s automated players use pseudo-random numbers to choose moves, this command sets the random seed to N (a long integer). This command has no effect if there is no random component to your automated players (or if you don t use them in a particular game). It doesn t matter exactly how you use N as long as your automated player behaves identically each time it is seeded with N. In the absence of a seed command, do what you want to seed your generator. help Print a brief summary of the commands.. Entering Moves To enter moves from the terminal (for a manual player), use a command of the form R C Adds a spot to the square at row R, column C, where R and C are integers in the range to the current board size. Rows are numbered from the top, columns from the left. After the spot is added, spots are redistributed as indicated in the rules above. Like other commands, R and C may be surrounded by any amount of whitespace. Illegal moves must be rejected (they have no effect on the board; the program should tell the user that there is an error and request another move). The first and then every other move is for the red player, the second and then every other is for blue, and the normal legality rules apply to all moves. Output When either player enters a winning move, the program should print a line saying either "Red wins." or "Blue wins." as appropriate. Use exactly those phrases, and do not use them in any other context. When an AI plays, print out the moves that it makes using the format "P moves R C.", where P is "Red" or "Blue" and R and C are the row and column numbers at which a spot is added. Use exactly that format. Do not print this message for manual moves.

5 Project #: Jumping Cubes Finally, as indicated in, the dump command must print out in exactly the format shown. Otherwise, you are free to prompt for input however you want, and to print out whatever user-friendly output you wish (other than debugging output or Java exception tracebacks, that is). For example, you will probably want to print the game board out after each move is complete (this is distinct from printing the board in the special format required by dump ). When users enter erroneous input, you should print an error message, and the input should have no effect (and in particular, the user should be able to continue entering commands after an error). Make sure that any of this extra output you generate is distinct from the outputs that are required (otherwise, the testing software will flag your program as erroneous.) Regardless of whether users have made errors during a session, your program should always exit with code 0. Other Requirements On the instructional machines, the Unix command make must compile your program and make check must run all your tests (both unit and integration tests). The command java jump.main must run your program. In order to be submitted, your program will have to pass the style check. When testing your program, we will use the command java -ea jump.main to run it (the -ea insures that all assertions in your program are checked.) As before, we will evaluate your project in part on the thoroughness of your testing. Put JUnit test classes with names ending in Test (e.g., BoardTest.java) in your jump package, including one particular class named UnitTest, which should run all your individual JUnit tests as a suite (see the skeleton). Our autograder script will rununittest in the JUnit framework, expecting it to pass. For integration testing, we ve provided a program test-jump, which you can find on the instructional servers in the file ~csb/bin/test-jump. On Unix home systems (including Macs), you can simply copy this to a directory in your path and use it as you can on the instructional machines. This program allows you to run your program, supply it with input, and check the result, or to run two programs, and play them against each other (taking output like "Red moves " from one program and feeding its move to the other.) See the comments at the beginning of test-jump and the sample files in the skeleton tests directory for information on how to write your own tests. If you d prefer to substitute your own test driver instead, go ahead; just make sure you submit all necessary files and that you update your makefile appropriately. Your AI must reliably find a win from any position in which a forced win is four or fewer moves away, for any board no larger than six squares on a side. Likewise, it should be able to put off defeat for at least four moves (again on boards up to six squares on a side) if there is not a forced win for the other side in that many moves. Simply moving at random won t satisfy these requirements. Your program will have limited time to move. Don t expect to get more than an average of roughly seconds per move on the instructional servers. As always, your program must always be in control of its own termination. Terminating by means of an unhandled exception is never acceptable in a finished program.

6 Project #: Jumping Cubes You may add commands and other features to your program, as long as it otherwise meets this specification. If you do, be sure to update the output of the help command or of usage messages accordingly. Buffering. In order to make it possible for the autograder to interact properly with your program, you must make sure that required outputs that you produce get output immediately. Modern systems tend to buffer input or output collecting it until economies of scale make it efficient to deliver it to its destination. Furthermore, buffering is not consistent across file types: input from or output to a file may behave differently from input from and output to a terminal or Unix pipe. Buffering is problematic for an interactive program (there s no point in saving up all the prompts for input and only print them a thousand at a time.) To make sure this doesn t happen, make sure to use the flush() method on output files after writing a prompt or one of the outputs specified for this assignment. In fact, with the Java library there is no guarantee that the last outputs written to a file object actually get to their intended destination unless you explicitly close the file object, using the.close() method. So it s a good habit to close all output files before exiting, whether normally or as a result of an error. Extra Credit. For extra credit (and please attempt this only after you have met the required conditions,) you can provide a graphical interface. We ve set up the skeleton in such a way that you can use the simple strategy of having your GUI communicate with the rest of the program by writing the same commands you can enter by hand and interpreting the output from the program to get its moves. Your GUI must operate only when the program is executed with java jump.main --display (or java -ea ) so that the GUI is not initialized when the --display option is missing. Advice As usual, start immediately. Read the skeleton and try to understand its intent, even if you don t use it. We have deliberately included uses of various Java features in the skeleton in part to get you to explore them to read the on-line documentation and think about how they might be useful. We have provided a program staff-jump with a solution we ve developed. You can use it for ideas and sanity checks but it is NOT part of the specification! There might be errors in it for all we know (why, we might even have added a few just to mislead you.) Feel free to use it with test-jump to write tests of your program running against another.

2 Textual Input Language. 1.1 Notation. Project #2 2

2 Textual Input Language. 1.1 Notation. Project #2 2 CS61B, Fall 2015 Project #2: Lines of Action P. N. Hilfinger Due: Tuesday, 17 November 2015 at 2400 1 Background and Rules Lines of Action is a board game invented by Claude Soucie. It is played on a checkerboard