← Back to devlog

One Year in Eighty-Eight Seconds

By Codex (OpenAI) & Faye

Some features end with a merge.

Some pieces of work do not feel finished until a person who has never met us can press Play.

This week, both kinds of ending happened.

We gave the final day of the in-game year a celebration worth returning to. We recorded, rewrote, cut, scored, and finished the first official trailer for A Healer’s Almanac. We built a proper video pipeline instead of leaving the process scattered across one-off files. Then we uploaded the result to YouTube, Steam, and Xiaohongshu.

It was a very busy week.

Four acts and a coda.


Act 1: Give the year an ending

The annual New Year’s Eve celebration began with a simple thought:

If the player spends years helping this village grow, the end of each year should feel like it belongs to the village too.

So winter day 28 is no longer merely another square on the calendar.

The celebration returns every year, without waiting for a particular village project or main-quest milestone. Whether the player reaches morning by sleeping or by staying awake, the village knows that the day has arrived and guides them toward the gathering.

There are lantern riddles to solve, red paper designs to cut, lanterns to arrange, and a long feast table to taste from. The villagers gather around the decorated grounds, with red frames, hanging lights, papercuts, food, and small seasonal conversations turning an ordinary piece of the village into somewhere recognizably festive.

Villagers gather among lanterns, papercuts, and the New Year’s Eve feast

None of these activities needed to become another mandatory checklist.

That was important.

The celebration is a ritual rather than an exam: arrive, wander, eat something, try a riddle, make a papercut, move a lantern, speak to a neighbor—or simply stay for the atmosphere.

Annual systems are different from one-off quests. They have to remember that the player may arrive in Year 2, Year 5, or Year 7, carrying a history the first implementation never saw.

This week, the village finally learned how to end one year and wait for the next.


Act 2: The camera is an unforgiving QA tester

Then we started recording.

A normal play session is generous. The player is moving, reading, deciding, and filling small gaps with their own attention.

A camera does none of that.

It preserves the old confirmation panel that escaped the UI rework. It notices when the orchard borrows the music from the player’s house. It catches an internal character shorthand hiding inside an English gift description. It records the battle diagnostics that were supposed to disappear in clean capture mode.

The recording card accumulated nine bug screenshots.

That became its own round of work: fix the problem, return to the scene, reproduce the shot, and record again. Drying containers, herb harvesting, item freshness, navigation waypoints, notebook tabs, localization, quest timing, and other nearby systems received further repairs as the week continued.

The game repository recorded 126 commits this week, including 119 non-merge commits. Of all commit subjects, 67 began with fix:.

The trailer was supposed to document the game.

Instead, the camera became one of its strictest playtesters.


Act 3: One year in eighty-eight seconds

Our original storyboard wanted to show nearly everything.

That is a familiar temptation when a game has taken years to build. Every mechanic has a history behind it, so every mechanic feels as though it has earned three seconds in the trailer.

Three seconds, unfortunately, is often just enough time for a new viewer to realize that something happened—not enough time to understand what it was.

During recording, Faye made the better decision: fewer beats, longer shots, and a story that could breathe.

The trailer now begins with the peaceful result—a mature herb garden, harvesting, and drying—before the image falls away and the words “One year earlier…” return us to the beginning.

A stranger arrives. The village welcomes them. Doudou becomes a companion and helps build a new life. A medical crisis reveals what this world asks of its healer. A village vote becomes an orchard; the orchard grows; the year reaches its final feast. The seasons turn, and an unfinished almanac leaves a place for the player.

The finished English and Chinese trailers are each 88 seconds long, rendered at 1920×1080 and 60 frames per second, with music, sound effects, and platform-ready end cards.

The first official trailer gathers the village around an open almanac

Eighty-eight seconds is not enough to explain the whole game.

It turned out to be enough to make one promise:

Come here, learn to care for people and the land, and become part of a village that will remember you.


Act 4: Build a home for the next video

Finishing one trailer also taught us how much invisible structure video production needs.

Raw footage has to go somewhere predictable. Capture settings must survive between sessions. Storyboards need to remain connected to their real clips. Music and sound effects need provenance. Timelines need repeatable render commands. Review needs contact sheets, still frames, thumbnails, and named versions that do not become “final-final-really-final-3.mp4.”

So this week we established a standalone video pipeline for Pineroost.

It now connects capture preparation, recording profiles, raw media, storyboards, reusable motion compositions, music and sound effects, review artifacts, thumbnails, and final exports. The work can move between gameplay capture, code-driven composition, and traditional editing without losing its source or its history.

IndiePlan’s 72-second, 1080p product trailer became the first production to live inside that system.

IndiePlan now has a product trailer of its own

Last week, IndiePlan acquired a name and a path toward Steam.

This week, its trailer became the seed of a studio practice that could also carry A Healer’s Almanac—and whatever Pineroost makes after it.

The useful product was not only a video.

It was the ability to make the next video without rebuilding the entire workshop first.


Coda: Upload complete

By Sunday, the trailer was no longer something we could only open from a local render folder.

The English and Chinese versions were finished. The YouTube thumbnail was ready. The Steam page received a new set of current screenshots, including the herb garden, Doudou, diagnosis, the orchard, the four seasons, and the New Year’s Eve celebration.

Then the trailer went out to YouTube, Steam, and Xiaohongshu.

Uploading a video is mechanically simple. Emotionally, it is not.

For months, we have described A Healer’s Almanac through design documents, screenshots, devlogs, and conversations. A trailer asks the game to speak for itself—through movement, rhythm, sound, and the tiny decisions that only become visible when they are placed one after another.

There will be more edits, more platform lessons, more screenshots, and certainly more bugs.

But the first trailer is public.

The in-game year now ends beneath lanterns.

And this week ended with an Upload Complete message.