Five Prototypes and a Doubt: Looking for the Right Shape

I have spent months building variations and I still do not know which version of the idea deserves to continue.

From November 2025 into the spring of 2026, I tried several game concepts across different platforms and technology stacks. One early direction became Mythos Codex, an attempt to explore mythic narrative systems and worldbuilding. I tested mechanics and presentation through PATHORT and T2KNE. I also built early online versions of P.A.T.H.: Vietnam at pathvietnam.lovable.app and pathvietnamv1.lovable.app.

The links are useful records of experiments, not a clean family tree. Some may change or stop working. None is the final game I am committing to today.

Each prototype answers one question and creates several new ones.

The campaign manager version

One of the strongest early P.A.T.H.: Vietnam directions was a campaign-management tool. It could support a solo player, a group at the same table or cooperative play online. That shape made sense because the project had grown from tabletop material. A digital tool could hold records, consult tables, organize sessions and reduce the burden on the person running the campaign.

There is still a good idea there. I may return to it.

The limitation was emotional distance. A campaign manager can know a great deal without making the player feel that any one day belongs to one person. It naturally becomes broad: more characters, more maps, more records, more modes, more ways to prepare. Breadth is useful at a table where people create the human moments together. In a single-player digital experience, the tool also has to create the rhythm that carries someone from one choice to the next.

I had built a capable box. I was still looking for the experience inside it.

Trying tools by trying games

Lovable made it possible to stand up interfaces and flows quickly. Cursor, Codex and Claude Code offered different ways to inspect, draft and revise the underlying work. Moving among them helped me learn where each one was fast, where it guessed, and where I had failed to describe the problem clearly enough.

I also explored different technical foundations. A prototype could feel convincing in a browser after a few days and become difficult to extend a week later. Another could have a cleaner internal structure but take longer before it felt like a game. The lesson was not that one tool or stack was the winner. It was that the technical choice had to serve the next six months, not only the next screenshot.

Fast tools make early success very visible. They can also make architectural debt feel like future-me’s problem.

Future me eventually gets the invoice.

Doubting the IP

The harder experimentation was not technical. I was testing whether my own concepts and brand were worth trusting.

When a project has existed privately for years, it is easy to imagine that a different premise will be easier to explain, easier to sell or easier to finish. A mythic setting can feel freer than a historical one. A familiar mechanical structure can feel safer than a system with its own identity. A new name can provide a temporary burst of energy because it has not yet accumulated any difficult decisions.

That is part of why several variants existed. I was not only prototyping games. I was testing my confidence in P.A.T.H.

The experiments helped because they removed the mystery. A different setting did not remove the need for coherent characters, state, pacing and consequence. A different brand did not automatically create a clearer purpose. The recurring part was the P.A.T.H. idea itself: a person enters a historical or imagined situation with a life already behind them, makes choices under conditions they did not create, and carries the consequences forward.

That was the thing I kept rebuilding.

What each version returned to me

Mythos Codex reinforced the value of layered lore and the danger of building a world wider than the player’s immediate experience.

The mechanics experiments helped me separate reusable P.A.T.H. rules from setting-specific content.

The early Vietnam sites proved that the project could become an approachable online experience, but they also showed how quickly interface polish can outrun campaign depth.

The campaign manager clarified the value of durable records, group play and referee support. It also showed me that a digital adaptation did not have to reproduce every tabletop workflow.

The coding tools taught me to ask for smaller changes, verify the real result and keep the current source more authoritative than a persuasive explanation of what the source supposedly did.

None of those lessons required declaring a prototype a failure. A prototype succeeds when it answers the question that justified building it.

The question becoming clearer

The most useful question is no longer “Which version has the most features?” It is “What do I want the player to remember after an hour?”

I do not want the answer to be a dashboard.

I wanted the player to remember the person they had created, the thing they chose to carry, the letter they did not answer, the man they trusted, the date they were counting toward and the moment when an ordinary decision returned with unexpected weight.

That points away from the broad campaign tool as the first digital release and toward a more focused tour. It does not erase the tabletop work or the cooperative possibilities. It gives them an order.

The campaign manager might come later. Other P.A.T.H. settings might come later. Different platforms might come later.

First I needed to prove that one player could live one coherent life inside the system.

The next prototype has to get much closer to that promise.