BuildMe
3–4 hoursIntermediate

Make a Tiny Game That Actually Feels Good

Maps to: Game Developer · Gameplay Designer, Game Designer, Indie Game Developer, Level Designer

You're going to build one tiny game (a single mechanic, like a one-button jumper) and then do the actual job of a game designer: tune it until it feels good. The skill is game feel: noticing why one jump feels satisfying and another feels like mush, then changing gravity, timing, a little screen-shake, a sound until 'meh' becomes 'one more try.' That's the heart of game design, the judgment about what's fun, and doing one tells you fast whether chasing that feeling is your kind of work.

The plan

0/4 done

You're 20% in just for starting, the hardest part. Mark your first step done to keep the momentum.

  1. Don't design a whole game. Pick one tiny thing the player does (jump, dodge, collect, click) and get the most bare-bones version of it moving on screen. A square that jumps is a perfect start. The goal of this hour is the magic moment: a thing you made, responding to you.

    Objective: One mechanic chosen, and a bare-bones playable version of it running.

    1. 1

      Pick your one mechanic and write one line on why it could feel satisfying. Fastest path to playable: describe it to Rosebud and it builds a version in your browser. Want to actually code it? Godot's free 'Your First 2D Game' gets a square jumping in about two hours.

      Tool: Rosebud AI

    2. 2

      Get the bare version running: just the mechanic, no polish, no goal yet. It can look like nothing. It just has to move.

    Your call

    Pick your one mechanic yourself (one-button jumper, collect-and-avoid, tiny dodge, or one-mechanic clicker) and write one line on why it could feel satisfying.

    Which mechanic, and one line on why it could feel good.

    What good looks like: One mechanic is moving on screen, responding to you, even if it looks like nothing yet.

    • Smaller than you think. One mechanic. You can always add later; you can't finish a game that's too big.
    • If you're prompting Rosebud and it's not quite right, change one word and re-run; don't rewrite the whole thing.

The bar to look back against

A playable game loop built from one mechanic and deliberately tuned for feel, where you can name what you changed (gravity, jump, timing, feedback) and why it feels better, published to a link someone can play, and you watched at least one real person play it. The feel is the work: not 'it runs,' but 'I made it feel good on purpose.'

Finish the final step, then submit what you built. Your progress is saved.

Tools you'll use

Step 1 · Pick ONE mechanic and get it moving

Rosebud AI Free

Describe a game in plain English and it builds a playable version in your browser you can tweak and share by link.

Best for: The fastest route to a playable loop. (Free: ~20 prompts/week, plenty for one tiny game; games stay browser/link-based.)

Godot Free

A real, fully free game engine, no account, no fees ever. Its GDScript is close to Python.

Best for: If you'd rather actually code your game, the 'Your First 2D Game' tutorial gets a square jumping in ~2 hours.

GDevelop Free

A free, no-code game maker: build logic by snapping visual blocks together.

Best for: A middle path: more control than prompting, no code to write.

Step 2–3 · Make it FEEL good

Claude or ChatGPT Free

An AI that writes/fixes GDScript and maps a 'feel' to the setting that controls it.

Best for: Hour 3: turning 'this feels floaty' into the right change, after YOU decided it feels floaty.

Step 3–4 · Ship it, and watch someone play

itch.io Free

The friendly indie game marketplace: upload a game and it plays right in the browser, no fee, no approval.

Best for: Publishing your finished loop so anyone can play it from a link. (Steam, by contrast, is a $100 upgrade, not needed here.)

How this shows up on a resume or college app

I designed and tuned a small game from a single mechanic, iterating on 'game feel,' adjusting gravity, timing, and feedback until it was satisfying to play, and published it for others to play. I learned that the hard part of game design isn't making it work, it's making it fun, and that 'fun' is a judgment you build by testing, not a formula you follow.