Lesson 18: Play Button + GameStats class (Matthes Ch 14 §1)
Learning Intentions
- Refactor the scattered ship_left counter into a proper GameStats class.
- Add a Play button so the game starts on click, not on launch.
Success Criteria
- My game_stats.py has a GameStats class with reset_stats() and game_active flag.
- Clicking 'Play' starts the game; losing shows the Play button again.
- I can explain why we hide the mouse during play.
📍 Do Now — Error of the Day
Right now your game ends and the window freezes. A real game shows a 'Play' button so the player can start again. Today we add one.
👁 I Do — Teacher Demo
Live-code GameStats class (extracts ships_left + adds game_active flag). Then the Button class — a Rect with rendered text. Hook MOUSEBUTTONDOWN → _check_play_button.
🤝 We Do — Build Together
Class wires up click-to-start together. Play button shows on launch + after losing. Click → game resets, mouse hides, play begins.
🚀 You Do — Your Turn
Customise button colour + text. Extension: show a second button like 'HIGH SCORE'. Arcade quests cover MOUSEBUTTONDOWN + collidepoint.
- Create game_stats.py with class GameStats — reset_stats() sets ships_left + game_active
- Create button.py with class Button — a Rect + rendered text
- Add self.play_button = Button(self, 'Play') to Game.__init__
- Add MOUSEBUTTONDOWN handler → _check_play_button
- On play click: reset stats, empty groups, create new fleet, hide mouse
🎮 Practice Quests — work through these
Loading practice quests for this lesson...
Three tiers — pick yours
Support
GameStats + Button skeletons pre-written
Core
build from scratch
Extension
animated button
Extensions
- Add a 'HIGH SCORE' title above the Play button.
- Show a flashing 'CLICK TO PLAY' hint.
📝 Exit Ticket — Coding Journal
Journal: explain the game_active flag — why do we need it separate from ships_left?
Evidence of Learning
Game starts with Play button visible. Clicking it starts play. Dying shows it again.