Why level design works in class
A level is a small problem to solve for someone else. Students have to imagine how another person will play, build, test, fail and improve. They practice creativity, spatial reasoning and persistence, and they get a concrete result they can share with the class.
And there is no programming to learn first: students start building in the first minutes. If you want to explain the approach to parents or colleagues, our article on making a game without coding is a good introduction.
What you need
Computers with a recent browser are ideal; tablets and phones work too, held in landscape. There is nothing to install. Students can build and test levels without an account; saving and publishing require a Google account, so follow your school’s rules on student accounts. A simple option is to play the levels together in class, directly in the editor, without publishing anything.
A one-hour session
Here is a format that fits in one class period:
- 10 minutes: demo on the projector: build a tiny level with a gap, a spike and three diamonds, then play it.
- 25 minutes: each student or pair builds a short level around one idea (a spring tower, a key to find, a lava run).
- 15 minutes: swap seats: everyone plays a classmate’s level while the designer watches without helping.
- 10 minutes: fixes and debrief: what was too hard, what was fun, what surprised the designers.
Playtesting: the heart of the workshop
The most valuable moment is watching someone else play your level. Ask designers to stay silent and note where players die, hesitate or get lost. Almost every student discovers that their level is harder than they thought: it is a powerful lesson about empathy and clear communication.
Our level design tips can serve as a checklist for the debrief: teach before you test, make dangers readable, keep it short.
Skills students practice
- Problem solving: placing a key, a door and a switch so that the puzzle works and cannot block the player.
- Spatial reasoning: judging distances: a jump covers about 5 tiles, a spring throws the hero about 8 tiles up.
- Iteration: build, test, fix, test again: the same loop as in engineering or writing.
- Feedback: giving and receiving precise, kind comments about someone else’s work.
- Vocabulary: the words of game design: difficulty curve, playtest, speedrun… our platformer glossary explains them.
Ideas for follow-up sessions
Give each session a constraint: a level with no enemies, a level that teaches the switch blocks, a level that must be finished in under 20 seconds. Students can also design a series of three levels with rising difficulty, or work on puzzles with keys and doors.
If levels are published, each one has its own leaderboard: a friendly race against the clock on the class levels is a great way to end a project.
A note on safety
Published levels are public. Players can report a level, and moderators can hide it. Before publishing with a class, agree on simple rules: level names that everyone can read, and no personal information in names or usernames.