$**$USE ICS$4$U COMPONENTS$**$Hangman Game

Objective: Create a Hangman game in Java $($console$)$ with varying levels of difficulty.

Mild

Requirements:

$1.$ Implement a basic version of the Hangman game where the user guesses letters to uncover a hidden word.

$2.$ Display ASCII art representing the Hangman's gallows and the current state of the word $($with blanks for unguessed letters and revealed letters$).$

$3.$ Allow the user a maximum of $6$ incorrect guesses before losing the game.

$4.$ Provide feedback to the user after each guess $($e$.$g$.,$ whether the guessed letter is correct or incorrect$).$

Medium

Additional Requirements:

$2.$ Include a predefined list of words for the game, with the word chosen randomly for each round.

$3.$ Add a feature to display a hangman ASCII art that updates with each incorrect guess, representing the progression towards losing the game.

$4.$ Along with the ASCII art, display the guessed letters that are incorrect and correct so the user can easily keep track of their progress.

$4.$ Include error handling for invalid inputs and ensure the program does not crash if the user enters non$-$alphabetic characters.

Spicy

Additional Requirements:

$1.$ Allow the user to choose the level of difficulty $($easy$,$ medium, hard$)$ before starting the game. Each difficulty level should correspond to a different word length range.

$2.$ Allow the user to play multiple rounds of the game without restarting the program.

$3.$ Implement a scoring system where the user earns points based on the difficulty level and the number of guesses remaining when the word is guessed correctly.

$4.$ If the user plays multiple rounds, allow them to accumulate points from previous rounds, or potentially lose points for losing games.

Success Criteria:

Functionality $(50\%)$: The program should meet all the requirements specified for the chosen difficulty level $($Mild $=30,$ Medium $=40,$ Spicy $=50).$

User Experience $(20\%)$: The game should be intuitive to play, with clear instructions and user$-$friendly input$/$output$.$

Code Quality $(20\%)$: Proper indentation, consistent naming conventions, and modular code structure.

Error Handling $(10\%)$: Appropriate handling of invalid inputs to prevent program crashes and provide informative error messages.