Inspiration
The idea started from a simple, slightly absurd question: what happens if you take the genuine tension of a survival-management game and put it in the hands of creatures who have absolutely no business handling a crisis? Space station survival sims tend to lean grim, and management games tend to lean clinical. Hamster Space Station came from wanting the stress to be real but the register to stay warm - to build something where a 9% oxygen near-miss makes your hands sweat for a second, and then you laugh, because the hamster who just saved everyone is covered in carrot seeds and immediately ready to do it again. The hamsters themselves became the inspiration engine: once Patches, Cheddar, and Nugget had distinct personalities, the whole design followed from asking what each of them would actually do under pressure.
What it does
Hamster Space Station is a real-time crew-management survival game where players assign three hamsters across three work modules - Engineering, Farming, and the EVA Airlock - to keep a crumbling station alive while building an emergency jump drive home. Crisis Tickets fire on a tunable escalation curve, resource meters for Oxygen, Food, and Hull Integrity all depend on each other through an explicit economy, and every hamster has a personal Energy bar that depletes with work and must be managed through the Cafeteria or Sleeping Quarters - meaning the player isn't just fighting the station's problems, they're managing their crew's wellbeing at the same time. Each hamster has a specialty (Patches in Farming, Cheddar in Engineering, Nugget on EVA) and a personality that shows up mechanically, not just cosmetically, so the tradeoffs always feel personal rather than abstract.
How I built it
The submission was built as four interlocking design artifacts: a Game Design Document covering the core loop, resource economy, and escalation curve; a Player Journey Map breaking the first fifteen minutes into phases with emotional beats, teaching moments, and design rationale; a Visual Concept Package defining the color language, UI layout, and character designs; and a Production Plan sequencing the build across four phases with explicit technical dependencies for the Meta Horizon mobile platform. Each artifact was built to inform and check the others - the escalation curve's numbers had to match the Journey Map's near-miss timing, the Visual Package's character traits had to match the GDD's specialties, and the Production Plan's milestones had to describe the exact experience the Journey Map promised. Iteration ran in both directions: design decisions made in the GDD reshaped the Journey Map, and friction discovered while writing the Journey Map fed back into simplifying the core loop.
Challenges I ran into
The hardest problem wasn't any single mechanic - it was keeping four documents in sync as the design evolved. Early drafts had four work modules instead of three, a fourth hamster that came and went, and character specialties that got reassigned more than once as the personalities sharpened. Every change had a way of rippling sideways: swap which hamster handles Engineering, and suddenly a callout in the GDD, a beat in the Journey Map, and a trait card in the Visual Package all need to agree with each other and with the new story.
Accomplishments that I'm proud of
The resource economy is the piece I'm most satisfied with - every resource has an explicit source, sink, and reinvestment path, and the three-way tradeoff between gathering seeds, covering oxygen, and feeding an exhausted hamster never has a clean answer by design. I'm also proud of how specific the Player Journey Map ended up: a second-by-second breakdown of the first 30 seconds, a minute-by-minute escalation table, and a near-miss window that's explicitly tuned rather than left to chance. Most of all, I'm proud that the hamsters' personalities are mechanical, not decorative - Cheddar refusing to leave the Cafeteria until her Energy bar is green, Nugget volunteering for EVA before she's even asked - because that's the detail that turns a spreadsheet of systems into a cast of characters players actually root for.
What I learned
Building four artifacts that have to agree with each other taught me that consistency is a design skill in its own right, separate from coming up with the ideas in the first place. A great mechanic that contradicts something three pages back isn't a great mechanic yet - it's a draft. The biggest personal takeaway was about restraint - the instinct to add a fourth hamster, a fourth module, another retention system, is strong, and the game got better every time I cut back toward three hamsters, three modules, and one very tight core loop.
What's next for Hamster Space Station
Can't wait to make this game! I imagined myself playing it and I feel that it would be genuinely fun to do so. I hope that that Horizon's tools will make it possible.
Log in or sign up for Devpost to join the conversation.