candyandfrank ▸ MAKER
Engineer · no class code yet Credits: — ○ No game yet

You're the chief engineer.
The AI just types.

▪ 240×135 screen · joystick + 2 buttons · real Python · one USB cable

Think it through, write the design card, inspect the build, hunt the bugs. The AI types the code — but tuning the numbers is a job it can never take from you.

BUGS FIXED 0
♥♥♥
BUG HUNT · 240×135 · made here
click = zap · space = jump
candyandfrank MAKER — think, design, build, play
Bench check before you start
  • Chrome or Edge, on this https address
  • Your class code from your teacher
  • A USB-C data cable for your handheld
  • First time on a handheld? Do the one-time system install first

STEP 1 Game Design Card

Fill in the card. Read each example out loud, then write your own.

What is it like to play? Say it like you're telling a friend.
When I push the joystick or press A, my game does…
When … happens, I win. When … happens, I lose.
The most special thing about your game. (Your pixel-art hero is added here automatically.)
Write your answers to the build crew's questions here.
🎨 Pixel Painter — draw your hero (16×16)

Tap a square to paint or erase; hold and drag to keep drawing. When you're done, press the button below and your hero is written into Special rules for you.

🗄 Version Cabinet — my ladder of progress

Once you build your first version, cartridges start collecting here.

🔒 Privacy & this computer

Only your design card (and, for a rework, your code + bug report) is sent to the AI. Your name is used only to file your versions under the class code. We don't collect anything else on this page. Your drafts are saved in this browser only — on a shared computer, press the button below when you're done so the next person doesn't get your work.

🔑 Teacher Panel

When a student passes their inspection question, grant a build credit here.