CS161 Black Jack

Game Rules

Blackjack is a popular card game that is simple to play. The object of the game is to beat the dealer in one of the following ways:

• Get 21 points on the player's first two cards (called a "blackjack" or "natural") without a dealer blackjack;
• Reach a final score higher than the dealer without exceeding 21
• Let the dealer draw additional cards until their hand exceeds 21 ("busted").
• Initially the two Buttons "Hit" and Stand are disabled.

The player and the dealer receive two cards at the start and one at a time afterwards. The player decides whether to receive another card based on the value of his hand. Each face card has a value of 10, an ace may be counted as 1 or 11, and the other cards have values equal to their number. The player or dealer whose hand is closest to 21 wins the game. If a player goes over 21, he/she automatically loses (called a "bust"). If the player chooses to stand, the player is finished playing and waits for the dealer to play until standing or busting. If the player and dealer have equal points, then the game is called a push, and no one wins.

For example, consider the following hands: see image.

Player's hand has a value of 3 + 2 + 1 + 10 = 16. Note that the ace cannot be counted as 11 or the value would exceed 21. Dealers hand has the value 10 + 5 + 5 = 20. Dealer wins the game.

For this project, you must simulate a casino-style two-player game of Blackjack, pitting a player against a dealer. The player will draw cards first. If the player busts, the dealer automatically wins the game without receiving the cards. Otherwise, the dealer draws cards and the points of the player and dealer are compared.

Project Requirements

Operations

A. Initial View

Below is an initial view of the GUI displaying the game board: see image.

Initially the two Buttons "Hit" and Stand are disabled.

You can enable/disable Button object using the setDisable(Boolean) method.

The "Blackjack" table shows cards on both players' hands during gameplay.

B. Start Game (Figure 2)

When the player clicks "Start Game" Button, start a new game with the following initializations:

• Disable Start Button and enable Hit and Stand Buttons
• Reset the Deck
• Clear any existing game information such as hand values
• Put one card into the Dealer's hand
• Update the Label value of the Dealer's hand

The GUI will look like this (the first card may be different each time obviously): see image.

C. Player Plays the Game

When the player clicks the "Hit" button:

• A Card is added to the player hand
• The value of the player's hand is updated
• If the player has busted, end the game

If the hit did not bust the player, it will look something like this: see image.

Clicking Hit again: see image.

D. Dealer Plays the Game

If the player has not busted and clicks "Stand", the dealer begins playing the game.

• Using algorithms developed in the Player class, simulate the dealer's actions (hit or stand)
• Update the value of the dealer's hand on each hit
• Once the dealer has busted or decided to stand, end the game

E. Ending the Game

To end the game, the victor or a tie must be decided. The game result can be determined based on the following:

• If the player busted during their, the dealer automatically wins (the dealer does not even play in this scenario)
  • Display "Bust!" by the player's hand value
• If the dealer busted, the player automatically wins (implies the player did not bust)
  • Display "Bust!" by the dealer's hand value
• If neither player nor dealer busted, compare the value of each hand
  • The one with a higher hand value wins
  • In case of a tie, it is called a "push" and no one wins

After determining the winner, display the result and update the player or dealer score accordingly. Return the game buttons to their initial state Here are screenshots of each end game result:

Player Bust: see image.

Dealer Bust: see image.

Player Wins, no Bust: see image.

Dealer Wins, no Bust: see image.

Push (Tie): see image.

Implementation Requirements

The following class relationship diagram shows the required classes and how they interact. see image.

The BlackjackTableGUI class creates and manages the GUI and game using event-driven programming. The Card class represents a single playing card as defined by its face (All cards are spades for simplicity). It extends the ImageView class from JavaFX to store the card and its image in one convenient class. The Deck class represents a common deck of 52 playing cards (4 copies of each face Ace-2-...-Queen-King). Player is a class that encapsulates the common attributes of a player such as the player and dealer. Player and dealer are dealt cards from the same deck stored statically in Player class.

All methods must be public visibility. Use responsible access modifiers for all other fields.