Building a sandbox in the dark
Every GM should have shares in Post-it notes to stop themselves from drowning in loose pages, overlapping drafts, and redacted secrets buried in old books, napkins and hard to find PDFs.
Whole timelines disappear into folders named Final_v3.
In Search of Typhon began that way too, a beautiful mess of character sketches, conspiracies, and half-written mission outlines scattered across a Trello board, Scrivener folders, Google Docs and Word. It was a mess.
But something changed when I moved the story into the Tartarus Sector.
I realised I wasn’t writing a story anymore. I was engineering a world, and that meant the tools had to develop.
From Story to Structure
When I first wrote the outline for In Search of Typhon five years ago, it was a narrative in the traditional sense: acts, scenes, dialogue, beats. I designed it like a film script — cinematic and tightly controlled, a story that knew exactly where it was going.
But Alien: Evolved Edition opened up the opportunity for something completely different. The Tartarus campaign setting wasn’t a single corridor of dread; it was an entire sector — a sprawl of corporate intrigue, military decay, and colonies left to rot on the edge of nowhere.
I realised that if Typhon was going to exist inside that, it couldn’t just be a single narrative thread. It had to be a system — one that would continue to move whether the players were watching or off pursuing something else.
I didn’t want to just run my story inside the Alien universe; I wanted to plug it into the machine and see what survived.
The Integration Layer: Tartarus Meets Typhon
The process began with overlaid maps, faction charts, and cross-references between my original lore and the Evolved Edition core rulebook.
Tartarus already offered everything a good sandbox needs — politics, power struggles, and a sense of creeping inevitability.
I didn’t want to replace that; I wanted to infect it with my narrative.
Every key figure from my notes found a home:
An antagonist, a former executive who breaks away from the company, fits right in with the secret dealings of and .
An ICC field agent who becomes a moving piece in the sector’s delicate power balance.
A missing NPC that becomes the link between the players and the conspiracy and now haunts the back channels of Tartarus’ outer systems.
By rooting these characters in Free League’s existing architecture, the story immediately gained weight. The universe didn’t need to adapt to my writing; the story was already there, just waiting to be told.
The Digital Backbone
To make that complexity sustainable, I built what I now call the campaign’s digital spine — a Notion database structured like a living organism.
It isn’t a wiki or a set of notes; it’s a simulation of the campaign’s internal logic.
Every table is a layer of the ecosystem.
NPCs track motives, factions, and current whereabouts.
Factions record assets, territories, and levels of corporate or ideological influence.
Planets and Systems pulls directly from Tartarus, with overlays for active conflicts and secret installations.
Clues and leads connect to multiple entities — an NPC, a location, a faction — to form a self-referencing web of cause and effect.
The real magic isn’t in the data itself, but in the relationships between it all.
Clicking through one record creates a chain of consequences — an entire network of who knows what, who wants what, and who’s willing to kill for it.
Designing from the NPC’s Perspective
This is where the biggest creative shift happened.
I stopped writing from the players’ point of view and started building the campaign from the outside in, through the eyes of the NPCs.
Each major figure in In Search of Typhon now operates like a self-contained narrative engine. They have motivations, secrets, and trajectories that move regardless of the players’ actions. Their decisions ripple through the database: when an event triggers, the status of related NPCs and factions changes automatically.
If the crew ignores a lead, the world doesn’t pause. It advances unseen.
This approach changes how I think as a Game Mother. Instead of plotting outcomes, I work probabilities. The players aren’t uncovering my story — they’re colliding with it.
A Living Web
The deeper I built the database, the more it resembled a conspiracy itself. Every clue is cross-linked. Each secret has an owner. The entire system hums with tension.
And because all of it is relational, I can follow a single thread — a location, a name, a shipment number — and watch it spiral into an entire narrative arc.
That means I no longer prep plots. I prep pressure points. The rest emerges naturally once players start making decisions.
This structure also makes the campaign modular. So, if the players jump across the map, the story doesn’t collapse — it just loads a different node.
Every planet, every outpost, every corporate pawn in Tartarus is ready to react.
The Alien universe works because it feels indifferent. It doesn’t care about the characters’ plans or intentions. The same should be true of the campaign.
By giving the world autonomy, both narratively and mechanically, I’ve built a framework where the story doesn’t need to be forced. It just happens.
The Notion database isn’t there to keep the story tidy. It’s there to make sure the universe can carry on even when the players can’t.
And somewhere deep in the dark between systems, the machine hums on — waiting for the first dice to fall.