Why P.A.T.H. Is Building Lucky 8 Instead of Borrowing a Rules Engine

Earlier this year, after sitting on the idea for a very long time, I decided to give my own RPG settings a serious year of work. P.A.T.H.: Vietnam (Pivotal Actions Through History) was the project I kept coming back to. I had the historical interest, the research and more notes than any sensible person needs. What I needed was to turn them into something people could play.

I did not begin by deciding the world needed another rules engine. There are hundreds already. Plenty of them are good. In January, I chose Free League’s Year Zero Engine under the Free Tabletop License as the foundation for my Vietnam setting. It seemed a practical way to spend my time on the campaign instead of inventing every mechanism underneath it.

For much of the winter, that meant writing, editing, testing, rewriting and discovering that the apparently finished paragraph still needed another pass. Familiar work, if you have ever tried to make a rule survive somebody else reading it.

The prototypes kept changing the question

Alongside the manuals, I started building digital prototypes. One early experiment was a campaign engine for Twilight: 2000, a game I have enjoyed since its original release in the eighties. With related mechanics behind my Vietnam setting, it seemed a reasonable place to explore campaign management.

It was fun to build and try. It also reminded me how easily I could spend all my available time improving a tool for somebody else’s setting while my own game waited nearby.

The following months produced several P.A.T.H. variations: solo and cooperative campaign systems, character and inventory tracking, narrative tools and a prototype with an AI backend running the campaign. Each version helped me see something. Each also offered about a dozen new things to build before I had decided which game I was actually making.

The direction gradually became clearer. I wanted one person’s experience inside a historical campaign, with a life before service and consequences that stayed around afterward. A campaign manager could support that. It was not the whole experience.

July brought a fairly unpleasant discovery

While polishing the manuals, preparing a proposal for Free League and spending serious time on the digital game, I looked more closely at the licence. The digital direction I had been building toward did not fit the foundation I had chosen.

I had a very definite “You’ve got to be shitting me” moment.

By then, months of rules, examples, prototype code and documentation were connected to that decision. This was not a matter of changing a logo and carrying on. I could not treat the game I wanted to release as something that would sort itself out once I had finished enough screens.

That was my mistake to resolve. Free League had its terms. I needed a foundation that suited the future I was building, including the digital game. Being annoyed about discovering the mismatch late did not make the mismatch disappear.

Removing a name did not remove the dependency

I spent days trying to untangle references, rewrite material and work out how much of the stack needed attention. That was uncomfortable in a more practical way. Some reassuring checks were checking the assumptions I was trying to leave behind.

A passing result is not much comfort when you have asked it the wrong question.

The useful lesson was that I had to separate the setting from the mechanism properly. The historical research, character ideas, campaign material, artwork and lessons from the prototypes were not suddenly worthless. But the rules could not become mine through a search-and-replace pass.

I was close enough to the outreach stage to feel the setback sharply. I had put hundreds of hours into building, reviewing and correcting this thing. Going back into the foundation was not how I expected to spend the next stretch of the year.

Still, that was the work in front of me. So I went back to work.

Lucky 8 gives that work a name

I already had an idea for a narrative engine that I wanted to explore. August being the eighth month made Lucky 8 a name I could have a little fun with. After all the frustrating parts, I was happy to keep a small joke.

The important part is what the system needs to do. It has to support social situations as well as combat. It has to make room for wounds, strain, relationships and ordinary competence. It has to work in a historical setting without letting a spectacular roll erase everything we know about the situation.

I also want it usable around a table. If an explanation needs me standing over somebody’s shoulder for twenty minutes, I have not finished explaining it. If a digital version hides all the confusion, the confusion is still there.

Building my own engine means I get to make those choices directly. It also means I have to do the work of making them hold together. There is no magic advantage in adding one more system to the pile.

The person still comes before the uniform

LifeP.A.T.H.—Previous Activities, Training, History—is one of the ideas I want to carry through all of this.

What did the character actually do before service? What did that teach him? What training followed? What does the campaign add that he could not have planned for?

I want those questions visible in the record. A childhood, a job or a responsibility can create real capability without handing out military qualifications for free. A school can teach specific work. A year of duties and decisions can change the person in ways the first character sheet could not predict.

That remains the centre whether I am writing a manual or building a screen. I do not want a perfect military tool with a sentimental biography attached. I want a person who has to live with what he chooses.

History gives the choices somewhere to happen

Pivotal Actions Through History does not mean the player gets to win the Vietnam War. It means actions matter inside a situation larger than the character.

Date, place, training, equipment, information and authority can limit what is possible. That does not remove agency. It gives the player a real problem. Find another method. Get the right person. Wait, prepare, accept a cost or decide the attempt is not worth it.

Sometimes there should be no roll at all. Qualified, routine work can simply happen. I would rather save the dice for an uncertain result that changes what comes next than make a capable Soldier repeatedly audition for his own job.

That is the game I am trying to bring out of this restart. The setting and the years of thinking still matter. The difficult lesson matters too, even if I would have preferred to learn it several months earlier.

I want to be more open about this part of the work: what I tried, what failed and why the next version is taking a different shape. There is plenty left to find out. At least I now know which foundation I need to build.