Free coding game for kids ages 10–13: snap blocks that turn into JavaScript-style code, then type your own loops and if statements to guide a robot.
How to play Code Quest
A small robot needs to collect every gem and park on the checkered flag. Your child writes the program that drives it. In the first half of the game, each block they tap appears on the same row as a line of JavaScript-style code, so “move” sits right next to moveForward(); and the orange repeat block sits next to for (let i = 0; i < 3; i++) {. When they press Run, the line that is running lights up while the robot moves.
In the second half the blocks disappear and your child types the code. A row of shortcut buttons inserts commands and loop templates at the cursor, which makes typing on a phone or tablet manageable.
| Levels | Concept |
|---|---|
| 1–4 | Sequences: move, turn, collect in the right order |
| 5–8 | for loops, including a loop inside a loop |
| 9–10 | if (onGem()): one program for two or three worlds with different gems |
| 11–12 | while (!atGoal()): loop until the job is done |
| 13–15 | Typing the same ideas as text |
| 16–20 | Sensors pathAhead(), pathLeft(), pathRight() and if / else if / else to solve mazes the program has never seen |
Every world is generated at random, so a solution cannot simply be memorized.
What your child learns
The bridge from blocks to text. Many kids get stuck between visual coding and “real” code because the two look unrelated. Seeing them side by side, line by line, makes the translation obvious: a block is just a line, and a block with a mouth is a line that ends in { with a matching } further down. By the time typing starts, the syntax already looks familiar.
Loops and patterns. A staircase of gems is the same four moves again and again. Spotting that pattern and wrapping it in a for loop is pattern recognition put to work, and the par counter rewards it.
Conditions and general solutions. When the same program must work in three worlds with gems in different places, a fixed list of moves fails. The only way through is if (onGem()) { collect(); }. That is the step from “a list of instructions” to an algorithm that adapts.
Reading error messages. Missing a bracket or misspelling a command produces a short, friendly message with a line number. Kids learn that errors are hints, not failures.
Algorithmic thinking with sensors. The final missions are mazes solved by a rule: if the path ahead is open, go; otherwise check left; otherwise turn right. Writing one small rule that solves any maze of that kind is a genuine computer science idea.
Tips for parents
- Ask “which line will run next?” before pressing Run. Tracing code in your head is the most valuable habit in programming.
- Read the code out loud together. “For i from 0 while i is less than 3” sounds strange at first and natural after a week.
- Praise shorter programs. When the counter turns green, ask your child to explain how the loop replaced the repeated lines.
- Let typos happen. Resist fixing them. Point at the message and ask what it says.
- Pause between the two halves. Level 12 to 13 is a big jump. A short break before typing helps.
Offline activities and variations
- Paper robot. Draw a grid, place coins as gems, and write the program in pencil using the same commands. A sibling or parent plays the robot and follows it literally.
- Loop hunt. Look for repeated patterns in songs, knitting, dance steps or stairs, and write them as a
forloop. - Rule mazes. Draw a simple maze and test the “keep your hand on the right wall” rule. Does it always work? When does it fail?
Common mistakes
- Turning the wrong way because the robot faces down the screen. Imagine sitting in the robot.
- Putting the
collect();block outside the loop, so only the last gem is collected. - Forgetting the closing
}in text mode. Counting brackets in pairs fixes it.