Early Development - Status Update

This is the first proper development update for Lost in the Woods, and we wanted it to actually mean something not a two-line "still working on it" post, but a real look at where the project has been, where it stands right now, and what's actually changing under the hood. Grab a coffee. This one's long.

The biggest piece of news first: Lost in the Woods has changed engines. We're now building the game in Godot, and it's a decision that's been sitting with us for a while before we finally pulled the trigger.

When we started prototyping, the priority was speed get a playable slice together, prove the concept, see if the hoofprints-in-the-snow idea actually carried the dread we wanted it to. That prototype did its job. But as the scope of the game grew clearer, so did the friction. We needed tighter, more direct control over 2D lighting and rendering, over how the environment could shift in response to Agnes's state without every change becoming a fight against the tools. We needed a pipeline that didn't get in the way of iteration, because a game built on slow-burn atmosphere lives or dies on how quickly we can tune the feel of a scene, not just its logic.

Godot gave us that. Open, lightweight, built with 2D as a first-class citizen rather than an afterthought it fit the kind of game we're actually making far better than what we started with.

With the engine question settled, here's the honest state of things.

Lost in the Woods is early. Genuinely early. What exists right now is a playable slice covering the opening stretch of Act 1 — enough to establish Agnes, the isolated village buried in the winter of 1947, and the first hoofprints leading out past its edge into the treeline. It's small. It's also, we think, already doing the thing we set out to do: making a player uneasy before anything overtly frightening has actually happened.

The core pillars haven't moved. Slow pacing over jump scares. A world that reacts to Agnes's inner state rather than simply existing around her. A village that feels lived-in and recently emptied, not generically spooky. Everything we're building now is in service of those three ideas, and every system that doesn't serve them gets cut, no matter how interesting it seemed on paper.

Right now, active development is focused on the main menu — both its interface and, just as importantly, how it feels to sit in it before you've even pressed start.

This gets underestimated a lot. The main menu is the first place a player spends real, uninterrupted time inside the game's atmosphere. Before a single hoofprint appears on screen, before Agnes takes her first step into the snow, the menu has already told the player what kind of game this is. If it feels generic, the whole opening is fighting an uphill battle. If it feels right — quiet, cold, a little too still — it's already doing part of the horror's job for us.

We're iterating on layout, on how the menu transitions in and out, and on the small ambient details that live in the background while the player decides what to do. Below is a short clip of where it currently stands.

This is very much a work in progress — expect the polish pass, transitions, and audio layering to keep evolving from here. But it's the first time we've had something in this state worth actually showing.

Visually, we're leaning into a muted, desaturated palette that only breaks for specific, intentional moments a detail that matters, a color that shouldn't be there. It's a restraint-first approach: the fewer things fighting for the player's attention, the more weight the things that do stand out actually carry.

Sound is getting the same treatment. Rather than a constant ambient horror score, we're building toward long stretches of near-silence wind, distant creaks, Agnes's own footsteps in snow — with music reserved for moments that have earned it. Silence is doing a lot of the heavy lifting in this game, and we'd rather protect that than dilute it with wall-to-wall scoring

Once the main menu reaches a state we're happy with, focus moves back to expanding the playable Act 1 slice extending the trail further into the woods, deepening the environmental reactivity system now that it's rebuilt on solid Godot foundations, and starting early passes on the sound design layer described above.

We'll keep this devlog running as each piece lands, rather than saving everything for one big reveal. Progress in a game like this tends to be quiet and incremental which, fittingly, is exactly the kind of pacing we're trying to build into the game itself.

Thanks for following along.

— Dreammire Studios Team