Puzzle Game Logic

Explore & Discover

Play five puzzle games this week — try Portal 2, Monument Valley, or The Room (all free or cheap). As you play, don't just solve puzzles: watch how they're built. Notice when a puzzle feels fair versus frustrating, and ask yourself why. What clues did the designer give you? What rule did you figure out on your own? Jot down three puzzles that surprised you — a sentence or two each about what made them click. You're not building anything yet, just training your brain to see design decisions. Check out the YouTube channel "Game Maker's Toolkit" (free) — his puzzle design videos are genuinely mind-blowing. You're ready for the next step when you can describe three specific puzzle mechanics and explain what makes each one satisfying or tricky.

Learn the Basics

Puzzle games run on hidden rules — called logic systems. Learn the big ones: constraint satisfaction (Sudoku, Nonograms), state machines (doors that open only when X and Y are both true), and graph puzzles (mazes, network routing). Head to Brilliant.org (free tier) and try their logic puzzles section. Then watch "The Puzzle Instinct" playlist on the GDC Vault (free). Write a one-page "logic cheat sheet" with a real game example for each type. Utah's own game jams at Salt Lake Gaming Con have produced tons of clever constraint puzzles — look some up on itch.io for free. You're ready for the next step when you can name at least three logic system types and give a real game example for each.

Build Your First Project

Time to build your first puzzle in GDX or Scratch (both free). Pick ONE mechanic — a sliding block, a light beam that reflects, a switch that opens a door. Build it so it actually works, even if it looks rough. Don't design ten puzzles yet — just one mechanic that a player can interact with. Use the Scratch wiki or GDevelop's built-in tutorials if you get stuck. The goal is a single puzzle that has a start state, a goal state, and at least one rule the player has to figure out. Test it on a family member or friend and watch their face — you'll instantly know if it's too easy or too confusing. You're ready for the next step when you have a working puzzle that someone else can play start to finish.

Experiment & Iterate

Take that one mechanic and build three different puzzle levels around it. Each level should teach something new: level 1 introduces the rule, level 2 adds a twist, level 3 combines it with a second element. Playtest each level with a real human — not just in your head. When they get stuck, resist the urge to explain. Watch and take notes. Then redesign based on what you saw. Game designers call this "iteration" and it's the actual job. Keep a simple design doc (a Google Doc or notebook works great) tracking what changed and why. You're ready for the next step when you've playtested each level at least twice and made at least one meaningful change based on feedback.

Advanced Techniques

Now study advanced puzzle design techniques: difficulty curves, "aha moment" engineering, and how to layer mechanics without overwhelming players. Read "The Art of Puzzle Game Design" by Scott Kim (searchable free excerpts online) and watch Mark Brown's "Boss Keys" series on YouTube (free). Try adding a second mechanic to your game and design two levels that combine both — this is called mechanic layering and it's what separates good puzzle games from great ones. Study how Stephen's Sausage Roll or Baba Is You introduce new rules through environmental storytelling, not text. You're ready for the next step when you have a two-mechanic puzzle game with at least five levels that increase in difficulty.

Final Project Showcase

Polish your puzzle game into something you're proud to share. Add a title screen, clear visual feedback for success and failure, and at least six levels with a real difficulty curve. Write a one-page "designer's commentary" explaining every major design decision you made — what you tried, what failed, and what you'd do differently. Post your game to itch.io (free) with a short description. Share it in a game dev community like r/gamedev or the GDevelop Discord. Getting real feedback from strangers is different from family — prepare yourself for honest opinions and use them to level up. You're ready for the next step when your game is publicly posted and you've collected at least five pieces of outside feedback.