Multiplayer Radio Design

Overview

Students analyze how radio signals can create multiplayer interaction in micro:bit games, then design an original concept using a game design document. This lesson connects creativity with logical reasoning and planning for building in MakeCode.

Learning intentions

Students will be able to:

• describe how rational numbers and signed values relate to distances and opposite quantities in a simple game scenario
• write clear game rules, roles, and win conditions for a radio-based multiplayer game
• plan which radio-related MakeCode blocks they will need based on their game concept
• explain how player actions produce outcomes through radio communication

Success criteria

• I can explain that opposite quantities can combine to make 0 and connect this to “send vs. receive” or “score up vs. score down.”
• I can interpret signed “direction” ideas (positive/negative) as moving toward or away from a target.
• I can write a complete game design document: rules, roles, win condition, and a step-by-step flow of play.
• I can identify at least 3 MakeCode blocks needed for my radio game and justify why.

Curriculum links

• The Number System — apply and extend addition/subtraction of rational numbers using a number line idea (7.NS.A.1)
• The Number System — interpret sums of rational numbers in context and describe opposite quantities combining to make 0 (7.NS.A.1a)
• The Number System — understand integer division leading to rational quotients and interpret quotients in context (7.NS.A.2b)
• The Number System — understand multiplication rules for signed numbers and interpret products in context (7.NS.A.2a)

Lesson structure ({total minutes})

1. 0–5 min · Hook with scenario. Teacher shows an example prompt: “Player A sends a signal; Player B responds and changes the score.” Students quick-write: What changes, and how might the game “undo” or “balance” that change?
2. 5–12 min · Mini demo: multiplayer logic. Teacher briefly reviews an existing makecode.microbit radio game concept (no building yet): show how each device broadcasts, receives, and updates state (score/position/status). Students discuss in pairs: What are the roles, rules, and win condition?
3. 12–18 min · Bridge to math thinking (signed quantities). Teacher explains a game-friendly math frame: scores can increase/decrease (positive/negative), and “opposite” actions can cancel to 0. Students model with a simple number-line statement: “If +3 and -3 happen, what is the result?” Then students connect it to rules like “bonus and penalty.”
4. 18–25 min · Design doc walkthrough. Teacher distributes the game design document template and models filling in one section: player roles (e.g., Sender/Receiver), win condition (e.g., reach +10 score), and a short play loop (start → send → receive → update → repeat). Students follow along with their own draft.
5. 25–35 min · Brainstorm & sketch. Students brainstorm their own radio multiplayer concept, sketch a quick layout, and write:

• rules in 4–6 bullet steps
• what is sent over radio
• how devices interpret received signals
• win condition and tie-breaker Teacher circulates using a checklist: Are roles clear? Is there a measurable win condition? Is there a “balanced” action (opposites cancel to 0) or a signed score update?

6. 35–42 min · Plan the MakeCode blocks. Teacher asks for block identification: “From your rules, which actions require radio transmit/receive, storing score, and updating display?” Students list at least 3 blocks and write one sentence each explaining the purpose (e.g., “radio send broadcasts player move,” “radio receive triggers score change”).
7. 42–45 min · Exit ticket (fast). Students answer two prompts on a sticky note or form:

• “What is your win condition, and what triggers it?”
• “Give one example of an opposite quantity in your game that could combine to make 0.”

Resources

• Game design document template (print or digital)
• Example radio game screenshots or short teacher demo notes
• Student notebook or design journal
• Pencil/markers and optional sticky notes
• Teacher checklist for rules/roles/win condition clarity
• Timer for transitions
• Optional: simple number line worksheet (only 1–2 problems for modeling)

Assessment

• Teacher observation during drafting: check for clear rules, roles, and win condition
• Block planning check: students can justify radio-related blocks tied to their game flow
• Exit ticket to verify conceptual alignment to opposites canceling and win-condition triggers

Differentiation

• Support:
• Provide sentence starters for the design doc: “Players will send…”, “When a device receives…, it will…”, “The win condition is…”
• Offer a partially completed template for students who need structure (roles and win condition already labeled)
• Extension:
• Challenge advanced students to include a tie-breaker and a clear method to prevent “double scoring” (e.g., using a state variable)
• Ask them to include a signed “direction” mechanic (positive/negative points) and explain how opposite events affect the final score
• EAL/SEN considerations:
• Keep language simple and visual: use icons for roles (e.g., A/B), arrows for game loop steps
• Allow oral rehearsal before writing rules; then students copy key phrases into the template