Supplementals

This page collects the extension paths that are most useful once the core session is working well. It is most useful when a group finishes early, wants another round of challenge, or leaves with enough momentum that one session does not feel like enough.

The aim is to extend the experience in ways that stay concrete, teachable, and connected to the original learning goals.

The core experience is designed to be delivered as a single, guided skillmap session. This path gives the clearest student on-ramp and keeps the experience cumulative across stages. Students move through the Garage, On the Road, and Finish Line stages in order, making choices, testing them, and reflecting on what changed at each step. They can choose to login with a Google, Microsoft, or Clever account to save their progress and remix the project after the session, but no login is required to experience the core learning.

Guided Skillmap Session

This format works for most classrooms, workshops, and activations. Learners follow the MakeCode Arcade pathway in order and build one concept at a time. This path gives the clearest student on-ramp and keeps the experience cumulative across stages.

Facilitation supports are built into the skillmap, and the Run of Show notes provide specific pause points, discussion prompts, and remix moments.

Stage-Based Remix Ideas

The strongest remix moments in this project come directly from the tutorials learners have already completed. Each one points to a small, visible mechanic students can change without losing the full thread of the experience.

The Garage

The Garage tutorials ask students to set the mission, build the car, tune driveSpeed, create efficiency variables, add a tradeoff rule, choose a role lens, and launch the Garage Shakedown test track.

Specific examples from the tutorials

  • change the driveSpeed value from Setup and Tradeoffs and compare how the car feels during Garage Shakedown
  • adjust the tradeoff rule that links speed to efficiency cost
  • improve the mission message or first feedback moment in Mission Briefing so new players understand the challenge faster
  • add or revise the retry button in Garage Shakedown so teams can rerun tests more easily

Facilitator prompts

  • What do you predict will happen if we make the car faster before the shakedown?
  • What improved after your change, and what became harder?
  • Does this remix make the game clearer, faster, fairer, or more strategic?
  • Which role would care most about this decision: performance engineer, strategist, or software engineer?

Three remix levels

  • Level 1: Quick Tune: Change one visible number such as driveSpeed or an efficiency value, then rerun the shakedown.
  • Level 2: Tradeoff Builder: Adjust the rule that increases efficiency cost when speed goes up, then explain whether the balance feels more fair or more risky.
  • Level 3: Test Engineer Challenge: Change the setup values and also improve the shakedown feedback, such as retry flow, unit display, or a clearer readout, so another team can compare results more easily.

On the Road

The On the Road tutorials ask students to load saved setup values, spawn obstacles, handle collisions, reward clean driving, create pit stop choices, switch to rain after a timer, reduce grip in wet conditions, add puddle hazards, and reward adaptation.

Specific examples from the tutorials

  • change the clean-driving reward logic in Hit the Track so careful driving matters more or less
  • adjust how often obstacles appear or how punishing collisions feel
  • revise the pit stop prompt text or pit reward so the choice feels more strategic
  • change the rain timer, puddle challenge, or adaptation reward in Changing Conditions

Facilitator prompts

  • Is this remix rewarding speed, control, or strategy the most right now?
  • What should a telemetry analyst measure after this change?
  • If the rain starts earlier or later, how does that change what counts as a smart choice?
  • Did your remix make the game easier to understand or just harder to survive?

Three remix levels

  • Level 1: Driver Challenge: Change one reward or penalty, such as clean-driving points or collision cost, and test one run.
  • Level 2: Strategy Challenge: Adjust a pit stop or weather mechanic, then explain how the best decision changes for the player.
  • Level 3: Systems Challenge: Combine two connected changes, such as obstacle frequency plus collision penalty or rain timing plus grip reduction, then compare whether the track still feels fair and readable.

The Finish Line

The Finish Line tutorials ask students to run a combined final challenge, track collisions and pit stops, save run data, show a one-screen review, choose a next-test focus, connect results to a role, and build a Winners Circle screen with a career lens and CS takeaway.

Specific examples from the tutorials

  • change the final challenge balance between obstacle risk and pit stop recovery
  • revise the one-screen summary in Reflect and Review so results are easier to read
  • improve the next-test focus or role-connection text so it sounds more specific and helpful
  • update the Winners Circle message, celebration scene, or CS takeaway so the ending feels more personal and motivating

Facilitator prompts

  • Does this remix help players understand their result more clearly?
  • What evidence from the run should show up in the summary?
  • If you changed the closing message, who is it helping most: a confident player, a frustrated player, or a first-time coder?
  • What should the player test next after reading this screen?

Three remix levels

  • Level 1: Reflection Refresh: Change one summary label, prompt, or closing sentence so the result is easier to interpret.
  • Level 2: Evidence Upgrade: Add or revise one tracked result, such as collisions or pit stops, and make sure it appears in the review.
  • Level 3: Experience Designer Challenge: Improve both the review screen and the Winners Circle message so the ending explains the result, names a career connection, and gives a useful next-test idea.

The best remix prompts are the ones that can be explained in a few sentences, pointed to in one small part of the project, and tested quickly in the simulator.

Follow-Up Ideas

The session can end at the skillmap, but it does not have to. When more time is available, or when learners leave wanting to keep exploring, these follow-up options extend the experience without losing the original learning thread.

Continue the Remix Loop

  • invite teams to revisit one stage and improve a mechanic they now understand better than they did on the first run
  • ask students to choose whether they want to remix for speed, clarity, fairness, strategy, or accessibility, then explain why
  • have pairs compare two versions of the same game element, such as a fast setup versus a balanced setup or a short pit reward versus a larger one
  • encourage students to keep the change small enough that they can still explain what changed and what effect it had

Extend the Career Conversation

  • ask learners which team role they want to learn more about and what part of the game made them choose it
  • invite students to connect one stage of the experience to one real job, such as software engineer, strategist, telemetry analyst, designer, or sustainability lead
  • use the reflection screens from the Finish Line as a starting point for a short career discussion rather than a separate presentation

Use the Session as a Launch Point for Further Learning

  • ask students what they would build next if they were turning this into a larger game
  • invite them to add a new challenge, a new weather condition, a new reward system, or a different ending message
  • use one of the remix levels above as a bridge into a second lesson, coding club meeting, or maker-style design session

Support Educator Reflection

  • note which pause points created the strongest student discussion
  • record which remix prompt produced the clearest cause-and-effect learning
  • identify where students needed the most support with controls, vocabulary, or prediction
  • use those notes to shorten or sharpen the next run of the experience

Share the Project Beyond the Session

  • share the repository link with educators who want to inspect the project structure more deeply
  • use the project wiki for contributor-facing workflow notes, planning context, and implementation details
  • point interested learners or collaborators toward the full repository if they want to explore how the tutorials connect to the underlying project systems

Simple Closing Moves if Time Is Short

Even a few extra minutes after the main experience can support a useful follow-up.

  • ask each team to name one thing they changed and one thing they would test next
  • ask for one role connection from the room
  • have students vote on which remix idea would be most interesting for a second round