Skip to content

Latest commit

 

History

History
50 lines (39 loc) · 3.71 KB

W18_proj00.md

File metadata and controls

50 lines (39 loc) · 3.71 KB
Raw

Annie Bai, Hyewon Seong

CS56 Winter 2018 P. Conrad

Description:

The project allows you to simulate a Texas Hold'em poker game, either against a computer in single-player.

User Stories:

  • As a user, I can choose to play a single-player poker game against a computer
  • As a user, I can bet, call, check, or fold during a hand, or check the rules at any time.

Assessment of Project:

  • The single player mode runs to completion.
  • The option for creating a poker chat causes the screen to freeze.
  • The option of joining a poker chat brings up a chat screen, but does not send any messages.

User Stories: Prospective Options

  • As a user, I can play against multiple players in a game, instead of just one.
  • As a user, I can customize the name that is displayed on the screen.

Assessment of the README

The README is mostly comprehensive. A better explanation of how to win the game might be necessary for people who don't know the game.

Assessment of build.xml file

The file is currently based on ant, but has relatively few descriptions about what the flie itself is doing.

Assessment of Issues

There are enough issues to gain more than 1000 points, and they are clear in what is expected to gain those points.

Additional Issues

*Something we may try to implement is a more visually pleasing interface, for both choosing the game and displaying the win conditions, as well as an easier to read Rules explanation.

Assessment of code

The code is currently organized explicity for a two-player game, and therefore relies on such. The way each individual file is organized, but together the code gets a little messier.

  • The Deck code describes how the cards are moved from the active deck to the discarded one.
  • The Hand code seems to describe how to return values in the hand.
  • The Player class gives it a hand of cards, keeps track of its wins, and the amount of chips it holds
  • The PokerSinglePlayer class holds code for restarting a timer, but a timer isn't implemented within the game; it also depends heavily on there only being one opponent to determine many of its decisions.
  • The CompareHands code compares the values of two different cards in order to determine the winner - it is currently highly dependent on the fact that there are only two players
  • The Card class holds its value and suit with methods to return its value, its suit, and print out both in a string
  • The TableCards class represents the cards that are currently on the table, with the flop cards, turn card, and river card all being chosen randomly from the deck
  • The User class signifies a human player and includes a hand and chips, from the Player class, and a function to take a turn
  • The OpponentAI class inherits from the Player class and holds both a hand and a number of chips, and a method to determine whether or not it should bet or call and a string that tells the player what move the AI made.
  • The PokerMain class holds the staring menu to choose what type of game you want to play through buttons.
  • The PokerGame class holds the possible win conditions, the different steps of the game, whose turn it is, and all the other general assets that are present within the game
  • Most of the issues or additonal features we can add to this code will require a lot of refactoring of the original code, because of the way this is originally structured. We anticipate a large scale refactoring of this code, which might be challenging.

Assessment of Test Code

There are several test codes for win conditions for different match-ups. It doesn't cover every case, however, and could be improved in including cases for empty hands. It also does not have any test cases for the bet implementation or other features, which could be added to make it more thorough.