This Code.org challenge has a fun mission: a Star Wars droid — BB-8 (the round, snowman-shaped one) — has broken into pieces, and Eon has to code it to collect its own scrap parts and fix itself, like repairing a car.
Teamwork first
Eon and his dad run it as a pair again: Eon drives (keyboard and mouse), dad navigates (spots bugs, keeps them on track). "The driver focuses on writing code; the navigator focuses on finding mistakes." A real two-person coding team, kid-sized.
The power move: loop instead of stack
To reach a part, BB-8 has to roll several squares in the same direction. Eon's first instinct is to add a "go east" block for each square — but his dad nudges him toward the smarter tool:
When a step happens multiple times, don't stack the same block over and over — use the machine (a loop): "repeat N times."
So Eon counts the squares (one, two, three…) and sets the loop to repeat that many times. One tidy loop does the work of many blocks — and BB-8 rolls right to its missing part.
Why it's a big deal
This is the same loop idea from the repeat-block lesson, now used to collect several objects with one short program. That's the whole point of loops: less code, more done.
Try it
BB-8 needs to roll 4 squares east to a part. Stack four blocks… or write "repeat 4: go east." Which is tidier? (The loop — and if the part moves to 6 squares, you just change 4 to 6.)