Moving
Sequencing and movement: give an order, take the long way, then stop counting steps and let the code find the path.
Code Quest
Code Quest
The hero only moves when the code is right. Students write real JavaScript across 32 lessons and roughly 190 puzzles, and every mistake is visible on screen the moment they run it.
What students learn
Children this age lose interest when code is abstract. Here the feedback loop is instant and visual, so loops, conditionals and functions stop being vocabulary and become tools they reach for.
Write and debug real JavaScript.
Use loops and conditionals with intent.
Break a big problem into functions.
Read an error and fix it alone.
Code Quest teaches real JavaScript to ages 10–12 — no blocks, no drag-and-drop. Students type code into an editor to move a hero through a dungeon, and the hero only moves when the code is correct. Across 32 lessons and roughly 190 auto-graded puzzles they build from a single movement command to loops, conditionals, functions and decomposition, finishing with three boss lessons where everything has to work at once. The dungeon supplies the motivation; the JavaScript is the same language professional developers write.
Pathway rhythm
Thinking
Variables, arithmetic, booleans and conditionals — the hero starts making decisions instead of following a script.
Building
Loops, then functions and decomposition, then three boss lessons where everything has to work at once.
Module by module
Module 1 · Giving Orders (sequencing)
The first lessons: one command moves the hero one step. Students learn that a program is an ordered list of instructions and that order is not negotiable.
Writing a first statementSequencingReading the gridPrecision over guessing
- In class
- 'Give an Order' and 'The Long Way' — routing around pits, one instruction at a time.
- Outcome
- Student writes a working program and understands why a wrong order fails.
Module 2 · Stop Counting (abstraction and combat)
Counting every step gets tedious, so the hero learns to move to a destination. Then combat arrives and actions get consequences.
Abstraction over repetitionWorking with a richer APIPlanning a routeHandling failure states
- In class
- 'Stop Counting' and 'Clear the Hall', followed by the first debugging lesson, 'Fix the Map'.
- Outcome
- Student stops brute-forcing and starts choosing the right instruction for the job.
Module 3 · Naming Things (variables)
Values get names. Students store, reuse and update them, and discover why a well-named variable makes a program readable.
Declaring variablesReuse instead of repetitionUpdating a valueNaming clearly
- In class
- 'Name It Once' and 'The Loot Row' — tracking loot without retyping numbers.
- Outcome
- Student uses variables deliberately rather than hardcoding values.
Module 4 · Doing the Math (arithmetic and strings)
Arithmetic, then text. Students calculate, combine and count — and hit their second debugging lesson when the vault total comes out wrong.
Arithmetic operatorsWorking with stringsCombining valuesTracing a wrong result
- In class
- 'Do the Math', 'Mirror Math', 'Counting Coins', then 'The Miscounted Vault'.
- Outcome
- Student can find the line where a calculation went wrong instead of rewriting everything.
Module 5 · True or False (booleans and conditionals)
The biggest leap in the course: the hero starts making decisions. Booleans, comparisons, if, else, and choosing between several paths.
Boolean values and comparisonif / elseMultiple conditionsDeciding rather than scripting
- In class
- Six lessons from 'True or False' through 'Smart Choices', ending at 'The Broken Defender' debugging challenge.
- Outcome
- Student writes a program whose behaviour changes with the situation.
Module 6 · Again and Again (loops)
While loops, then for loops, then loops combined with conditionals — the point where students can express ideas that would take hundreds of lines otherwise.
while loopsfor loopsLoop plus conditionAvoiding infinite loops
- In class
- 'Endless Corridor' through 'Marching Orders', closing with 'The Tangled Path'.
- Outcome
- Student uses repetition as a tool and can reason about when a loop stops.
Module 7 · Build Your Own (functions and decomposition)
Students write their own moves, pass inputs to them, and break a large problem into named pieces — assembling a personal toolkit of functions.
Defining functionsParameters and inputsDecompositionReusing your own code
- In class
- 'Make Your Own Move' through 'Your Toolkit', then 'The Faulty Machine'.
- Outcome
- Student solves a big problem by splitting it, and reuses their own functions to do it.
Module 8 · The Bosses
Three final lessons where everything has to hold together at once — waves, escorts and the deepest room in the dungeon.
Combining every conceptWorking under pressureDebugging a long programFinishing what you started
- In class
- 'The First Deep One', 'The Gauntlet Returns' and 'Heart of the Dungeon'.
- Outcome
- Student completes a substantial program that uses loops, conditionals and their own functions together.
Skills gained
Writing real JavaScript by handSequencing and precisionVariables and namingArithmetic and stringsBooleans and conditionalswhile and for loopsWriting and calling functionsDecomposing a large problemReading an error and debuggingPersisting through a hard problem
Tools used
JavaScript in a real code editorThe Code Quest dungeon engineInstant automatic gradingXP and stars for completed puzzles
Final project
Heart of the Dungeon
The last boss lesson. Students face waves and escorts in the deepest room, solving it with the loops, conditionals and functions they wrote themselves across the previous 31 lessons.
Why parents choose it
Real code, not a toy
Many courses for this age use coloured blocks. Code Quest uses JavaScript typed into an editor — the same language that runs the web — so nothing has to be unlearned later.
Mistakes are visible, not shameful
When the code is wrong the hero simply does not move. Debugging becomes a normal part of the work rather than a failure, and three lessons are dedicated to it explicitly.
It cannot be faked
Every puzzle is graded automatically and the order is locked, so a student cannot skip ahead. Progress on the map is progress that actually happened.
A genuine on-ramp
Code Quest ends where Python Max begins. Your child arrives at the next program already knowing what a loop, a function and a variable are for.
Project examples
Clear the Hall
The Miscounted Vault
Your own reusable toolkit of functions
Heart of the Dungeon boss run
Format
32 lessons, about 6 puzzles each
Every puzzle auto-graded on the spot
Locked order — no skipping ahead
FAQ
Isn't JavaScript too hard at 10?
Not when the result is visible. Lesson one is a single line of code that makes the hero take one step; the difficulty climbs one idea at a time across 32 lessons.
Is this just a game?
The dungeon is the motivation; the code is real JavaScript typed into an editor. Nothing is dragged, and nothing is pretend.
Request information
Ready to choose the right pathway?
Book a focused consultation and map your child's age, interests, and goals to the right Numeris program.