CSCI 1226 A06

A06

Due Date: Friday, October 27
File(s) to be submitted: RockPaperScissors.java
Sample Output: SampleOutput.html

Rock-Paper-Scissors Game (Value-Returning Methods)

Synopsis

Implement a Rock, Paper, Scissors game using static methods in Java. The game should continuously run, allowing the player to play multiple times without restarting the program. Players can exit the game by entering a specific command.

Game Rules

Rock beats Scissors.
Scissors beats Paper.
Paper beats Rock

Task Description

The program should prompt the user to select Rock, Paper, or Scissors.
The computer should randomly select Rock, Paper, or Scissors.
Display the player's choice, the computer's choice, and the result of the match.
Repeat the game until the player decides to exit by typing Exit as a choice.
NOTE: Every 5th game (i.e., 5, 10, 15, 20, etc.), the computer reports the player's current record (wins, losses and ties).
Before exiting, the program should print a message on the console with the player’s totals wins, losses, and ties

Method Requirements

public static void printIntroduction(): This method prints out the program introduction (with title, description and author information) as demonstrated in the sample output.
public static String getChoiceFromUser(): This method should prompt the user to enter their choice (Rock, Paper, Scissors, or Exit to quit the game) using techniques covered in the lectures (e.g., Scanner class for the user input). Return the choice as a String.
public static String getRandomChoice(): This method should randomly generate a choice (Rock, Paper, or Scissors) and return it as a String.
public static String determineWinner(String playerChoice, String computerChoice): This method should take in the player's and computer's choices, determine the winner, and return a String stating the result (e.g., "You Win", "You Lose", or "There is a Tie").
public static void printStats(int wins, int losses, int ties): This method should take in the total numbers of player’s wins, losses, and ties and print a message on the console as provided in the sample output.

Additional Requirements

Use a while loop as covered in the lectures to continuously run the game.
The game should only exit if the player chooses the "Exit" option.
Handle invalid inputs properly. For example, if the user enters something other than "Rock", "Paper", "Scissors", or "Exit", prompt them to enter a valid choice until they enter a valid choice.
Document your code properly using Javadoc comments.
Display meaningful output messages guiding the user as shown in the sample program run.
The game must count how many wins, losses and ties a user has and print the totals after the user chooses the "Exit" option

Submission Requirements

Submit a RockPaperScissors.java file with your solution.

Grading Outline

5 points: The method printIntroduction() implemented correctly: it prints the introduction on the console and does not return anything
15 points: The method getRandomChoice implemented correctly - does not print anything, but returns a correct value as required.
10 points: The method getChoiceFromUser implemented correctly - prompts a user to provide a choice and returns it as a String
10 points: The method getChoiceFromUser handles invalid inputs (not "Rock", "Paper", "Scissors", or "Exit") and reprompts the user.
20 points: The method determineWinner implemented correctly - does not print anything, but returns a correct value as required, the logic of the method is implemented correctly.
10 points: The game continuously runs until the "Exit" command is issued using a while loop as described in the lecture.
5 points: The game correctly handles the "Exit" command to end the game.
10 points: Every 5th game (e.g., 5, 10, 15, etc.), the program should print a message on the console with the player’s current wins, losses, and ties using the printStats method (int wins, int losses, int ties) as shown in the sample run.
5 points: Before terminating, the program prints the stats of the game - total wins, losses, ties using the printStats method as shown in the sample run.
5 points: Proper formatting and naming conventions.
5 points: Proper Javadoc documentation.

Note: There will be penalties for submissions that do not compile (that Netbeans shows with those red squiggly underlines) or that "crash" on sample input (do input in an unexpected way). The grader may assign a grade of zero if they deem the code too hard to fix.

SUBMIT / Check