Game development log · The Last Shelter

The Last Shelter

A top-down pixel-art survival game built in Godot. The player wakes alone in a failing shelter, rebuilds its systems with an overconfident robot named BB, and eventually discovers the shelter is a damaged spaceship stranded near Earth.

Role
Solo Developer
Engine
Godot
Platform
PC, Console, Mobile
Timeframe
In development · Since May 2026
View development logs
Hero runtime capture from The Last Shelter
Hero runtime capture from The Last Shelter.

The player journey

Wake. Repair. Remember.

The emotional arc moves from isolation to companionship, then from one dark room to outer space. Each beat is a playable system, not a detached story screen.

01 / WAKE

Learn the shelter through need.

Movement, clothing, hunger, and the first repair make the unfamiliar room readable.

The player standing in the Living Quarter of The Last Shelter
Living Quarter runtime capture from the opening survival loop.
02 / REPAIR

Make systems depend on one another.

Power, machines, food, and BB’s trust turn survival into a connected route.

BB sprite sheet from The Last Shelter
Source sprite art; runtime Workshop capture pending.
03 / REMEMBER

Reinterpret the place you know.

The Bridge opens to Earth and the shelter becomes part of a damaged ark ship.

Earth seen from orbit in The Last Shelter
Bridge view source art used for the controlled world reveal.

Design pillars

A world made of systems.

The portfolio story is about the relationship between rules, writing, interface, and feeling—not only the pixel art on top.

Survival as discovery

Needs and repairs lead the player through the world, so onboarding happens inside a meaningful goal.

One connected system

Finite resources, room power, crafting, and farming reinforce one another rather than becoming isolated minigames.

Character inside the interface

BB teaches, obstructs, rewards, and eventually upgrades the player’s diegetic HUD.

Four development chapters

Questions first. Evidence next.

Each chapter isolates one design question and shows how it changes what the player can understand, do, or feel.

LOG 01Opening loop

Exploration — Letting the Game Unfold Through Play

How can the first survival loop teach the world without a detached tutorial?

Urgent needs turn movement, power, repair, and progression into one readable first-day route.

  • Onboarding
  • Narrative UX
  • Level Design
Use the same camera framing before and after the first room receives power.
Open log
LOG 02Chapter 2 · BB

Companion — Building an NPC With Real Personality

How can one NPC be character, progression gate, teacher, and interface designer?

BB makes the game’s systems feel personal: repairing the companion also changes what the player can understand and do.

  • Character Design
  • Writing
  • Interaction Design
Use the approved one-shot reveal with expression changes and confetti.
Open log
LOG 03Matter circulation

Nothing Is Waste — Building a Robust Resource System

How can repair, farming, crafting, and waste feel like one connected economy?

A finite material model makes the shelter feel alive while exposing the accounting questions that still need validation.

  • Systems Design
  • Economy
  • Balancing
Show Metallo, Carbo, Hydro, Oxo, and Silico moving through one potato loop.
Open log
LOG 04Chapter 2 · The Bridge

Expanding the Game — Giving Every Challenge a Worthwhile Payoff

How can each completed system earn a payoff that expands the story, mechanics, and space?

The repair loop grows into an EVA, turning familiar routing rules into a physical journey with a permanent power reward.

  • Systems Design
  • Spatial Design
  • Payoff
Sixth anchor, junction unlock, solar deployment, then Facility energy +1.
Open log

Controlled spoiler

The room is larger than it looks.

Let the overview earn its final reveal. The full Bridge context stays behind an intentional action.

Earth seen from the Bridge of the damaged ark ship