P.A.T.H.: Vietnam

P.A.T.H.: Vietnam — Developer's Dispatch

Game Updates, Reflections, and Dev Notes

Developer's Dispatches on design, history, systems, and other stories behind the P.A.T.H. Games title; P.A.T.H.: VIETNAM.

· developer return note

Coming Back With a Clearer Tour in Mind

A soldier says goodbye before deployment while transport waits nearby
I am returning to the project through one soldier's tour, beginning with the life and choices carried into deployment.

I'm returning to P.A.T.H.: Vietnam prototyping with more focus.

The break helped me separate the project I wanted to make now from the larger universe of things P.A.T.H. might eventually become. I cared about tabletop play, campaign management, cooperative possibilities, other eras and reusable systems. I just don't need to build all of them before proving the centre.

The centre of the experience is one player living one soldier’s tour of duty.

A text adventure with more life around the text

The simplest way to describe the direction is a choose-your-own-adventure or text adventure. The player reads a situation, makes a decision and moves into what follows.

This description is useful, but incomplete.

I want the choices to exist inside a lived year. The soldier has a background before Vietnam, a role in the unit, people at home, men around him, equipment in specific places, money, mail, fatigue, stress, injuries, duties and a date he is counting toward. The player should be able to open a record and see what the tour has done. A small decision should be allowed to return weeks later because the game remembers it.

The text provides the immediate moment. The surrounding systems give that moment weight.

This means creating depth without turning the screen into a spreadsheet. The mechanics could be substantial underneath, while the player-facing experience needs to remain readable: a scene, a choice, a consequence, a shift in the day and a record that stays coherent.

Bringing the 1960s onto the screen

Historical atmosphere can not depend on a few filters and a period font.

The 1960s need to arrive through objects, media and routine: the radio dial, the mail, the service record, the PX, the catalogue, the calendar, the photographs, the language people used and the material things a soldier carried or sent home.

This creates a useful design rule. An artifact should not exist only because it looks interesting. It should give the player another way to understand or affect the tour.

A Pocket Guide can be a readable object. A catalogue can create delayed delivery, financial decisions and a connection to someone at home. A calendar can show the historical date and the shortening road to DEROS. A radio can bring music, news, announcements and the strange normality of a broadcast reaching a base far from home.

The richer the presentation became, the more important restraint became. Historical availability is not the same as commercial permission. A recreated artifact needs provenance and context. A fictional broadcast should be clearly fictional even when it is designed to feel period-aware. The game can bring an era closer without pretending its simulation is an archive.

Health had to remain part of the plan

Coming back does not mean returning to the same pace that had forced the break.

With ADHD and ASD, I know I can enter deep, productive periods of focus. I also know that transitions, overload and the accumulation of unfinished threads can become costly. The solution is not to reject intensity completely. It is to put edges around it.

Smaller batches help. A written target helps. Tests help. A list of what is explicitly not part of the current pass helps. Stopping after a failed approach instead of immediately generating five replacements helps. So does leaving enough time to discover whether yesterday’s brilliant solution still makes sense in daylight.

The project deserves sustained attention and resources.

The next version starts here

The years of tabletop work and the earlier digital prototypes gave me a foundation. They do not give me the focused single-player game I'm describing today.

I'm using this final week of June to define that promise clearly. Starting in early July, I want to build the new prototype around one person’s complete tour rather than keep expanding several ideas at once. I do not yet have every interface, record, persistence rule, artifact or accessibility control in its final form. Those are design and implementation problems ahead of me, not features I can claim today.

What has become clear is the game promise:

That is enough to start again.

Is this the final prototype?

Most likely not.

But, the answer no longer frightens me as much as it did during the prototype period. A version does not need to be final to be the closest and most honest expression of the idea so far. It needs a clear purpose, a testable shape and enough discipline to reveal what should come next.

This direction feels closer to the experience I've wanted to inspire from the beginning. Not command from above. Not a parade of historical facts. Not a power fantasy dressed in period equipment, and certainly not another first person shooter.

A person enters a year he cannot control. History establishes the mission. The player chooses what follows, then lives with what the tour remembers.

Next tasks is to turn this clarity into a working build. I do not know how quickly it will progress or how much work will be required beneath the visible scenes.

I only know this next prototype feels like the natural progression of my idea.