Hangman Game Project Overview

Hangman Project Requirements

• Project Due: December 2, 2024, 10:00 PM (Canvas)
• Game Objective: Player guesses letters in a secret word chosen by the computer. The player loses chances as they guess incorrectly as the Hangman figure is drawn. The game ends when the word is guessed correctly or the Hangman is fully drawn.
• Game Play:
  • Computer chooses a secret word from a list.
  • Hidden word is displayed as underscores.
  • Players guess single letters; correct guesses reveal letters in the secret word, incorrect guesses add to the Hangman figure.
  • Repeated guesses don't penalize the player.
  • "Guess Word" button allows the player to guess the entire word (only use ask block here).
• Secret Word Selection (Based on Difficulty):
  • Easy: 9 or more letters.
  • Medium: 6-8 letters.
  • Hard: 5 or fewer letters.
• Game End & Restart:
  • Player wins by guessing the word correctly (in whole or in part).
  • Player loses by running out of chances (Hangman complete).
  • Game restarts with a "z" key press.
• Word Display: Current guessed letters must be displayed on the screen, while unguessed letters appear as underscores.
• Hangman:
  • The Hangman figure reveals pieces with incorrect guesses (head, body, arms, legs).
  • The Hangman sprite's image is crucial for tracking game progress; its image must meet educational standards.
• Sprite Requirements:
  • Appropriately named sprites (avoid "Sprite1", "Sprite2").
  • "Guess Letter" sprite(s) to handle single letter guesses.
  • "Guess Word" button to prompt for the entire guess.
  • Appropriate use of (and avoidance of) ask/say blocks is crucial(only "ask" allowed when guessing the entire word).
• Word List: Use the provided "wordList" from the starter code to choose a random secret word based on difficulty settings.
• Statistics: The game must track and display the win/loss ratio and fewest guesses record for the user's subsequent games.
• Documentation:
  • Organize Snap! scripts for readability.
  • Remove unused blocks.
  • Name sprites, variables, and custom blocks clearly.
  • Add comments to explain complex code sections.
  • Provide details about which partner worked on which parts of the code.
• Custom Block Requirements:
  • Include a custom block with a parameter impacting game functionality (at least 1 parameter).
  • The block must utilize sequencing, selection, and iteration and produce different outputs based on the different input parameters.
  • Use a list (other than the word list) for efficient game mechanics.
• Screen Display: Information must be displayed without using the "say" block or variable display boxes.
• Important Note: Late submission will incur point deductions. Deductions will increase as time passes (see the rubric). Also, maintain school-appropriate content.