Designing Meatball's Big Walk: A Game Where You Play as a Dog Who Smells Through Dimensions

The first game I’m building for ephergent.com is Meatball’s Big Walk — a cozy point-and-click where you play as Meatball, the ship’s dog, exploring the lifeboat engine room.

Meatball can smell through dimensions. This is canon. It’s also the best game mechanic I’ve ever accidentally written into a story.

The Setup

This game is set during the “lifeboat era” of Season 1 — before the crew of The Ephergent knows they’re on a starship, before A1 reveals himself, before any of the dimensional travel really starts. It’s the quiet before the signal.

The engine room is small. A1’s blue glow fills the corners. Pixel’s espresso-stained workstation is in one corner. There’s a bone somewhere that turns out to be a frequency modulator (don’t worry about it). Meatball is just… being a good dog.

Why a Dog?

A few reasons, in order of how embarrassing they are to admit:

Meatball is the most immediately loveable character. Players who don’t yet know the Ephergent universe will not feel the weight of A1’s loneliness or the significance of Pixel’s role. But they will pat a dog. Meatball is the on-ramp.

“Smell” as a mechanic is interesting and undersused. Most point-and-click exploration games use vision — you click things you see. Sniffing inverts this. Meatball’s nose detects things that aren’t visually obvious: the faint dimensional resonance in a seemingly ordinary crate, the residual frequency signature on a bone that shouldn’t exist in the engine room. It gives me a way to surface lore naturally without exposition.

A no-fail-state game is easier to design well. Meatball can’t die. He can’t make wrong choices. He can investigate everything or nothing. This removes a whole layer of design complexity (balance, difficulty tuning, death states) and lets me focus on making each hotspot feel rewarding.

Scope — The Hard Cap

The game has:

• 1 scene — the engine room
• ~10 sniffable hotspots — each with a Meatball observation (internal monologue in his voice)
• ~20 one-liner reactions — some hotspots have multiple sniff results depending on order
• 0 fail states
• ~5 minutes of play if you investigate everything

That’s it. No inventory. No puzzles. No dialogue trees. Just a dog, a room, and the quiet hum of a ship that knows more than it’s saying.

Meatball’s Voice

Writing Meatball’s observations is the most enjoyable part of this project. His internal monologue is earnest and slightly oblique — he understands more than humans do about what’s happening, but he frames it in dog terms.

A few test lines (unpolished):

The corner smells like something that used to be a long way away. Like when you’ve been to a park and can still smell the park even after you’ve left. This corner has been to many parks.

The wrench smells like Om-Kai’s hands and also like a frequency I don’t have a word for. My nose has words for frequencies. The words are all feelings.

The bone smells like: home, far away, and Tuesday.

That last one is Meatball’s voice exactly. He doesn’t know what Tuesday is. He knows it smells like something.

The 15MB Budget

Meatball’s Big Walk targets 10MB compressed. The breakdown I’m planning:

• Godot HTML5 runtime baseline: ~5MB
• Background art (single environment): ~2MB
• Character sprites (Meatball + A1 glow): ~1MB
• Audio (ambient ship hum loop + reaction sounds): ~1MB
• Remaining: ~1MB buffer

Single scene, warm pixel art aesthetic, amber/brass color palette for the engine room. Different frequency, different look — this is the rule.

Next Step

Install Godot 4.x → build “hello cockpit” (empty scene, HTML5 export, measure compressed size) → report back with actual numbers.

The game dev posts will get more technical from here. This one was mostly me convincing myself the scope is right. I think it is.

Go sniff some things.