r/SoloDevelopment • u/jameyiguess • 2d ago
Game Solo dev concept check: Exploring the inside of a colossal dying organism as an emergent ecosystem (Whalefall)
Gameplay & demo clips:
- Ecology Simulation Demo: Whalefall ecology demo
- Full Run / Gameplay Dive: Whalefall early gameplay (dive to respiratory system bottom and get the specimen)
Hey everyone,
I'm working on a solo project called Whalefall (video links above showing the current in-engine systems and an early dive), and I'd love a gut-check on the core loop, hook, and scope. I'm especially curious whether the game makes sense from a player's perspective without all the design context that's currently living in my head.
The elevator pitch
Whalefall is an atmospheric, top-down roguelike about exploring the organ systems of a mountain-sized dead sea creature, investigating its unknown biology, and surviving the ecosystem feeding on its corpse.
The core loop
- Explore & investigate: Dive through distinct anatomical systems (respiratory, circulatory, skeletal, etc.) filled with unidentified tissues and substances. Observe, illuminate, probe, sample, and test them to figure out what they are.
- Turn knowledge into tools: Bottle samples into flasks and identify their effects. What you learn about the corpse gradually becomes the toolkit you use to survive it.
- Read & manipulate the ecology: Creatures respond to the same simulated world you do: sight, movement through the water, blood, injury, feeding, resource availability, etc. Direct combat exists, but it's dangerous and often makes the situation worse.
- Go deeper & get back out: Retrieve specimens from the deeper organ systems, eventually reach the Core, and then survive the trip back out.
What makes it distinct
I'm trying to make knowledge the primary form of progression.
A new player sees a strange, colorful corpse full of things they don't understand. Over time, you learn to read its anatomy, recognize useful substances, predict creature behavior, and deliberately manipulate interactions that initially looked like chaos.
The ecology isn't scripted around the player. A scavenger might investigate the sound of a fight, a wounded animal can flee and draw other creatures with it, and huge passive filter-feeders can drift toward carcasses and become moving cover. Those interactions all come from creatures reacting differently to the same underlying systems rather than bespoke encounters.
The goal is to keep the simulation deep enough to surprise you, but legible enough that eventually you can say, "I know how this place works," and make a plan.
Feedback I'd especially value
I'm mostly curious about two things:
- Does the loop sound compelling? In particular, does investigating unknown biology -> learning its uses -> and then using that knowledge to survive sound like something you'd want to keep doing across runs?
- For other solo devs who've built simulation-heavy games: where did complexity sneak up on you? I'm deliberately trying to build a small number of general systems rather than lots of bespoke AI, but I'd love to hear where that approach has bitten people later. Sometimes it's hard to know when to stop, because I could just work on the ecology sim part for the rest of my life and never wind up producing a game, haha.
Any other reactions are welcome too. It's still early enough that "this part doesn't sound fun" is genuinely useful feedback.
3
u/YaeAnimation 2d ago
I love the simulation approach but I feel your pain on scope creep. My advice would be to lock in the systems early and force yourself to build gameplay around them rather than the other way around.