The obvious things shouldn't need orders.
A fireteam now helps its own. Covering fire, casualty drags and a little more initiative—plus the feature we decided to remove after trying it.
OPEN FIELD NOTE →
Building a living frontier where a small crew can find a home, make a name, and venture into the inexplicable.
FALLOW is a grounded, expedition-first survival and tactical simulation in development. These are the records of how it is taking shape—from the systems that work to the ideas that don't survive playtesting.
Meaningful workstreams, real playtest decisions, and the evidence behind each change.
A fireteam now helps its own. Covering fire, casualty drags and a little more initiative—plus the feature we decided to remove after trying it.
OPEN FIELD NOTE →
A fight can be complicated without being impossible to understand.
Formations, realistic stops and the small decisions that make a squad feel alive.
Moving the interface into the world, and giving players room to think.
Decades after the Collapse, people have rebuilt lives at its edge. But the place where it began hasn't finished becoming something else.
ENTER THE WORLD ARCHIVE →The difference between someone who ventures into the Fallow and an expeditionary who's made a life of it.
Rebuilt settlements, persistent uncertainty, and a catastrophe that may not have finished.
From temporary refuge to the beginnings of a working expeditionary town.
We wanted a fireteam that could look after itself. Playtesting revealed which parts actually helped—and which new interface we'd rather leave behind.
There's a particular kind of frustration in a tactical game: watching someone stand beside a wounded teammate while you pause the world and tell them to help. FALLOW's latest workstream explored how much of that responsibility should belong to the survivors themselves.
The ambition was bounded initiative—not a squad that decides your strategy for you, but people capable of handling immediate, sensible actions within their orders.

We also built a system where a fireteam could propose requests—retreating, flanking, dragging a casualty—and wait for you to accept them. The benchmarks exposed problems: a lone flanker entered crossfire; an untimely pursuit left other enemies still shooting.

“I didn't use it at all and didn't feel like I wanted to.”
That was the playtest verdict on the request interface. So we retired those badges and benched the INITIATIVE setting for now, keeping both tested for a possible revisit. The immediate helpful behaviours stayed. This is exactly why a workstream doesn't end when the code runs: it ends when the interaction earns its place.
The same branch brought a significant identity change: Fallow became the game's working title. The start screen was redesigned around a redacted order, a stark FALLOW readout, and a brief expedition designation. The field interface also settled on Oxanium for ordinary text, with Saira Stencil One retained for titles and names.

Quick checks passed 16/16 after each step. On the final game code, 27 of 28 Full suites passed; the native walkthrough initially failed, partly because improved covering fire prevented the scripted casualty. After adjusting that script, its own validator passed 14/14, but the other 27 suites were not rerun in that same pass.
The next substantial stretch of development turns toward enemies and detection, the home base, and eventually a convincing complete demo on Westbank.
Workstream by workstream, the decisions and experiments that are making FALLOW into a playable world. No daily noise. No manufactured milestones.
Squad initiative, playtest decisions and the FALLOW working title.
Target lines, a clearer fight summary, state icons and credible engagement decisions.
Formation marching, multi-step plans, contact drills and building occupation.
Teal world-space tags, right-click actions, context and a more legible interface.
Somewhere between recovery and emergence, people have made a life in the shadow of the place where everything began.
The Fallow is a named region, not a generic class of zones. It was ground zero of the Collapse, the disaster that spread outward and changed the world. Roughly thirty to sixty years later, its consequences are still unfolding.
Beyond it, communities have rebuilt. Inside it, industrial ruins, farms, towns, wilderness and reclaimed infrastructure form a continuous frontier. The cause of the Collapse remains unresolved; so does the nature of the artifacts.
Many people enter the Fallow. Fewer learn how to live and work there. Expeditionaries survey, recover, escort, hunt artifacts, take contracts, and cull the nonhuman threats that endanger settlements. Their work is varied, their reputations complicated, and no single organisation gets to decide who counts.
The player's refuge can grow into a functioning expeditionary headquarters and, potentially, a town. It needs food, production, repair, trade and people with reasons to stay. Home matters because it gives every journey into the Fallow a human consequence.
The frontier can be frightening, but it can also be beautiful, strange, funny and quietly domestic. Altered wildlife, unfamiliar species, ordinary life and inexplicable things coexist. The mystery is not a checklist waiting for a final answer.
An honest development journal for FALLOW: a grounded, expedition-first survival and tactical simulation built in Godot.
FALLOW's development is iterative and openly examined. Each completed workstream leaves behind a technical record, screenshots, playtest results and decisions. The Field Notes turn that evidence into a readable story about the emerging game.
These notes distinguish confirmed features from experiments, record what testing did and didn't prove, and leave mysteries in the world genuinely unresolved.
After a workstream has been completed and merged, the project owner asks for a new Field Note. The editor reviews the private development diary and verified game evidence, writes the public-facing report, checks the screenshots and publishing status, then updates this site and its RSS feed.
Publication is deliberately owner-triggered rather than automatic on every code change. The game repository and detailed development diary remain private. No Claude calls are used to write or publish this journal.