web app in the index.html file: that meets the following requirements

This game is based on a game played by two players, where one calls even or odd, then both players on the count of three extend from 1 to 4 fingers of one hand. The win loss conditions are explained in 5 - 8 below.

This gameplay is modified slightly from this format to be suitable for computer play. In the computer played version the human player is the one calling even or odd by entering it into a prompt. The computer generates both numbers, calculates their sum, determines if the sum is even or odd, displays the game results, keeps a record of the human player's wins and losses, and displays the tally with the game results.

1. The player will enter their name first and the computer will use the player name in all messages.
   • (This should be exactly the same as we have been doing with BNH.)
2. Before each play, the human player will call whether the total number count will be an even number or an odd number.
   • For this computerized version the human player will enter even or odd in a prompt.
   • User input should be case insensitive.
3. On the count of three the computer will randomize two numbers from 1 to 4 inclusive.
4. The computer adds the two numbers together.
5. If the sum of the numbers is even and the human player called it called even, that player wins.
6. If the sum of the numbers is odd and the human player called it called even, that player looses.
7. If the sum of the numbers is odd and the human player called it called odd, that player wins.
8. If the sum of the numbers is odd and the human player called it called even, that player looses.
9. The computer displays the game results in a sentence as given below.
   • playerName, you chose playerChoice, the sum was number which is an even/oddnumber, you win/lose!
10. The computer keeps track of the human player's wins and losses.
11. The computer displays to the human player their total number of wins and losses.
    • Use a prompt to display game results, win/loss totals, and query to play again.
12. Allow the player to play as many times as they want.
    • Since the player name is already stored in a variable, there is no need to ask for it after the first play.
13. For invalid or empty input from player, continue prompting player for valid input, provide example of expected input.
14. No need for the total number of wins and losses to persist after a game session.

Example game results and win/loss record:

"Phil, you chose even, the sum was 7, which is an odd number, you Lose! That's 3 wins and 5 losses! Would you like to play again? y/n"

Submission Details

Upload index.html containing your code

For full credit index.html must run and look as specified

For Bonus Credit, follow the instructions in the Late Work announcement to submit planning and design artifacts. Examples of artifacts: the truth table for this game. (Refer to the truth table in BNH to see what to apply here.) App process flows, activity diagrams, lists of steps, maps like the ones in the comparison and looping classrooms, any and all of this is eligible. If you sketched or scribbled with pen and paper then make a phone pic of it. Use case scenarios and user stories are welcome too. Zip it all up and submit as an attachment to the comments.

{Gradebook > Click that specific assignment > Find the comments field > below that is the attachment tool.}

Upload