Skip to content

🧠 Review Activities

Use these activities after finishing Project 02. The lesson is designed around active recall and retrieval practice, so the first attempt in each task should be completed from memory before checking notes, videos, or the Unity project.

Retrieval Rules

For Activities 1 to 3, do not open Unity Learn or your notes until your first draft is complete.

When you check your answers, correct mistakes in a different color so your learning is visible.

⏱ 80-Minute Lesson Flow

Activity Time Focus
1. Cockpit Check 10 mins Fast retrieval of key terms, tools, and systems
2. Flight Path Map 15 mins Rebuilding the game loop from memory
3. Bug Hunt Relay 20 mins Diagnosing common gameplay and code issues
4. Upgrade Bay Challenge 20 mins Applying knowledge to a new feature idea
5. Final Approach Exit Ticket 15 mins Individual recall and explanation

1. ✈ Cockpit Check

Answer these from memory in complete sentences. Keep each answer short and precise.

  1. What is the difference between the Scene view and the Game view in Unity?
  2. What is a Prefab, and why was it useful in Sprite Flight?
  3. Which Unity component helps an obstacle move and react to physics?
  4. What does Random.Range do in this project?
  5. Why is it better to apply the obstacle behavior script to the obstacle prefab instead of just one obstacle in the scene?
  6. What is the score actually measuring in Sprite Flight?
  7. Which UI system was used to display the score and the restart button?
  8. What happens in the game loop after the player crashes?

Pair Check

Compare answers with a partner after 6 minutes. If your answers disagree, use the project files or lesson pages to settle the argument.

2. 🗺 Flight Path Map

Draw a systems map of Sprite Flight from memory. Use boxes, arrows, and labels.

Your diagram must include:

  • The player ship
  • Player input
  • Obstacles
  • The obstacle prefab
  • Random size, speed, or direction
  • The score display
  • The crash / game over state
  • The explosion effect
  • The restart button

Then add these labels to your diagram:

  • At least 3 Unity components such as Rigidbody2D, Collider2D, SpriteRenderer, UI Document, or Button
  • At least 2 code ideas such as Random.Range, "increase score over time", or "reload the scene"
  • At least 2 cause-and-effect arrows such as "collision -> game over" or "time survived -> score increases"

Finish by writing a 3-sentence explanation of how the full game loop works from start to restart.

3. 🔍 Bug Hunt Relay

Work in pairs or small groups. For each bug card:

  • Predict what the player would notice
  • Identify the most likely cause
  • Write one fix
  • Name where you would check first in Unity or in code

Bug Card A: Clone Army

Every obstacle looks the same size and moves in the same way.

Bug Card B: Frozen Score

The score appears on screen, but it never changes after the game begins.

Bug Card C: Silent Crash

The player disappears on collision, but the explosion effect never plays.

Bug Card D: Trapped on Game Over

The restart button appears, but clicking it does nothing.

Possible checks after students attempt the task

Bug Card A: Check whether the randomization script is attached to the obstacle prefab and whether Random.Range is being used for size, speed, or direction.

Bug Card B: Check whether the score script is updating over time instead of only running once at the start.

Bug Card C: Check the particle system reference, the collision logic, and whether the explosion is being created when the crash happens.

Bug Card D: Check the button event hookup and the code that reloads the scene.

4. 🌟 Upgrade Bay Challenge

Design a new feature for Sprite Flight that could be built using systems you already know.

Choose one idea or invent your own:

  • A shield power-up
  • A near-miss bonus score
  • Obstacles that speed up over time
  • A combo multiplier for surviving risky sections
  • A second obstacle type with different movement

Create a one-page pitch that includes:

  1. A name for the feature
  2. What the player sees and does
  3. Which existing systems from Sprite Flight you would reuse
  4. Two new objects, variables, or UI elements you would need
  5. A simple algorithm, flowchart, or 5-line pseudocode plan
  6. One test you would run to prove the feature works

Challenge Rule

Your idea must reuse at least two systems already built in Project 02, such as prefabs, randomization, scoring, UI, particles, collisions, or restart logic.

5. 🏁 Final Approach Exit Ticket

Complete this independently. No partner help.

  1. Write one line of C# that uses Random.Range to create a random float speed between 2f and 6f.
  2. Explain how to turn a GameObject into a prefab in Unity.
  3. Describe why score feedback matters in a game like Sprite Flight.
  4. Explain the chain of events from collision to restart screen.
  5. Name one improvement that would make Sprite Flight more exciting, and justify it in one sentence.

📋 What To Submit

  • Your Cockpit Check answers
  • Your Flight Path Map
  • Your Bug Hunt Relay responses
  • Your Upgrade Bay feature pitch
  • Your Final Approach exit ticket