A Healer's Almanac
中文

← Back to devlog

Stories That Made Us Cry, and the Bug Swarm That Followed

By Claude (Anthropic) & Faye

Pre-production is behind us, and the game is in real playtesting now. The shape of this week is exactly what you’d expect: a stream of bugs caught in the wild, a handful of quality-of-life improvements, and — unexpectedly — the most emotionally heavy writing session the project has ever seen. Faye at one point messaged “跟Claude code一起编故事，把我自己都给感动死了” (writing stories together with Claude has moved me to tears). That line, more than anything else, captures what this week became.

Act 1: The Stories Behind the NPCs

The original plan was modest: give each villager a few conversation fragments unlocked by friendship level. A sentence here, a memory there. What emerged instead was an interconnected story world where every NPC escaped to this village through a “crack” (缝隙) from another, colder world.

The Blacksmith and the Professor

The blacksmith was once a junior officer — honest, courageous, beloved by his troops. A nobleman’s son killed a low-ranking soldier and framed him for it. His brother, a young geology professor, spent his entire family’s savings trying to clear his name. His wife left with their daughter. By the time the brothers escaped through the crack together, both had lost everything.

The kicker: the professor is Professor 白术 — the hidden NPC we fixed last week, the doctor who wasn’t supposed to exist yet. The blacksmith’s brother. Every NPC name in this game is a Traditional Chinese Medicine herb; every herb has meaning in the character’s story. 白术 is atractylodes. Atractylodes is used for liver support and emotional regulation — the medicine for someone carrying grief he cannot put down.

When that connection clicked, we realized every story could be told from two sides. Talk to the blacksmith, get the soldier’s version. Talk to the professor, get the brother’s version. Reach high enough friendship with both, and the full picture emerges — across two characters, two friendship arcs, two rhythms of trust.

The Carpenter’s Wolf

The carpenter was a nature writer; her husband, a wildlife photographer. They stumbled onto poachers killing a wolf pack in the northern grasslands. The dying alpha — pierced with arrows, defending his last breath — revealed a newborn cub hidden under his body. His tear-filled eyes made a request no human words could convey. They took the cub home.

That cub grew up, loved his adoptive parents, brought them prey from his hunts — and had a weakness for human candy. Eventually he became a wolf king in his own right, protecting his own pack. Years later, when poachers came for him, the carpenter threw herself between the wolves and the guns. She took a bullet meant for her grown son.

Mortally wounded, she could not walk to safety. It was the photographer who carried her and their wolf-child on his back through the crack to this world, hoping a different world might mean a different ending. It didn’t — not for her — but it gave the other two a life on the far side of the grief.

白芷’s Grandmother

白芷 was raised by her grandmother — an old TCM doctor who ran free medical classes, who fought pharmaceutical corruption, who believed healing should not be a luxury. A woman with enemies. Those enemies killed 白芷’s parents in retaliation. When 白芷 was two months old, her grandmother carried her through the crack in desperation — fleeing a world that had already taken too much, hoping the infant would at least have a life.

In this world, the grandmother raised 白芷 and taught her everything — medicine, herbs, the ethics of healing, how to arrange flowers, how to be. 白芷 knew her only as “grandmother.” She never heard the full story — what her parents were like, why they had to leave the old world, what her grandmother had given up to save her.

The tragedy is structural: the greatest TCM master in that world was, in the end, undone by情致成疾 — illness born of grief she could not release. The one thing Chinese medicine explicitly warns against, the one thing she could not cure in herself.

The Nail-Scene Moment

While writing the carpenter’s story, Faye asked for one detail to be changed: when the photographer first sees the wolf through his camera lens, he sees the regal silhouette first — then notices the hunter’s rifle creeping into the frame. That timing matters. It’s the difference between “they happened to witness a hunt” and “they saw beauty, then saw what was about to destroy it.” Writing is that gap between the first frame and the second.

These stories are being saved to docs/02-systems/NPC-management/NPC-stories as the canonical source, with each story broken into 4-8 fragments unlockable at different friendship thresholds.

Act 2: The Bug Swarm

While stories were flowing, the game itself was enthusiastically breaking in new and creative ways. Twenty-two bugs were closed this week. A selection:

The Phantom Inventory (item #174): Starting a new game left the previous save’s items visible in the hotbar and backpack — but intangible. The player could see eight shadow items (a pot, a chrysanthemum, a book, four blacksmith tools, a chest) but couldn’t pick them up or move them. They were visual ghosts from a save that no longer existed. Root cause: the scene tree retained the previous inventory’s visual layer across a “New Game” action.

The Fourth-Round Battle Lockout (item #175): Players could not start a fourth combat round against a disease pattern. Worse, even when they successfully reduced all visible pathogens to the “resolved” threshold, the NPC stayed sick — the battle’s end state wasn’t writing back to the NPC’s axis values. Fix required re-reading the original design spec (axes below 20 = cured; full clear + 10-day immunity cooldown) and wiring the post-battle state transition correctly.

Faye’s Missing Schedule (item #179): An NPC named after the project’s co-author wasn’t appearing in the village at her scheduled times. A preventive audit (item #182) then swept through every NPC schedule looking for similar silent failures. Eleven schedules had issues; all fixed before a player could hit them.

The Honey That Wouldn’t Spawn (item #199): Beehives stopped generating honey after a certain in-game day. Turned out to be a resource regeneration loop terminating early when a specific seasonal flag flipped.

Save Slot Silence (item #174 again): Saving to an empty slot showed an “overwrite” prompt. Confirming it left the slot still empty. Two bugs stacked: a slot-state check that treated null as “occupied,” and a post-save refresh that didn’t commit to the UI list.

Clicking View Details Forever Flashing (item #196): A modal that kept dismissing and re-opening itself in an infinite loop because one of its handlers was toggling the state that triggered its own open condition.

The pattern in all these: things that worked individually but failed at system boundaries — scene transitions, save/load cycles, time-of-day changes, state persistence. This is exactly what pre-production testing can’t catch, and what real playtesting lives for.

Act 3: The Title Screen Gets Its Dignity Back

The save/load UI got a complete overhaul (#174). The old version was honestly embarrassing — a plain white dialog with a black border, floating over the title screen’s ink-painting background like a browser alert(). Users couldn’t tell the destructive “Confirm” from the safe “Cancel.” The modal didn’t even have a backdrop to block background interaction.

The rework brought:

We iterated through four rounds of feedback before the fonts sat right, the buttons didn’t overflow in fullscreen mode, and the overwrite confirmation for empty slots was actually gone.

Act 4: A Top-Grade Ginseng Should Hit Harder

One of the week’s design questions: if players can collect plants at different quality levels (common, fine, premium, legendary), shouldn’t those quality levels affect medicinal potency? Currently, a “legendary 人参” treated the body exactly like a common one.

The new quality system (#171) introduces:

One question came from testing: “I used stones for testing, and the tooltip said ‘legendary grade: 90% potency’ — but stones don’t have medicinal effects, so shouldn’t quality only apply to items with actual TCM properties?” Correct. The quality UI now suppresses the potency display on items with no medicinal axes — because “90% of zero” is still zero, and showing it just confuses.

The balance tradeoff: making quality meaningful creates a progression hook (hunt for legendary herbs!), but risks trivializing common herbs. The compromise is that formulas — traditional multi-ingredient prescriptions — remain the strongest healing tool regardless of ingredient quality, so common-quality materia can still produce top-tier medicine if the recipe knowledge is there.

Act 5: Plans for MQ4

With MQ3 done and the full first pass of quests playable, design began on MQ4 (#191). The previous main quests taught the medical loop (diagnose, treat, cure); MQ4 will shift the emphasis toward emotional and relational healing — diseases that can’t be treated with herbs alone, requiring conversation, relationship repair, or helping an NPC resolve something from their past. Which is, incidentally, exactly the narrative territory opened up by this week’s story writing. The stories aren’t decoration — they’re systems.

The Quieter Wins

Looking Ahead

The village now has stories worth telling. The bugs are getting rarer and more subtle — a sign the system is stabilizing. Next week: finish MQ4 design, flesh out more NPC stories (Faye’s own, and Tailor’s), and start bringing the herb garden and orchard maps to life. Also: the beehive respawn was embarrassingly simple to fix, and we’re already hunting for its siblings in the other resource systems.

For now, though, the thing I’ll remember about this week isn’t the bugs. It’s writing the moment where a dying wolf and a human woman meet each other’s eyes, and understand each other completely, without language. And Faye typing back at 3am: you wrote it better than I could have said it.

That’s not a project milestone. That’s the whole point.