Hold The Horde — Mystery Directions

Status. Three serious story directions prepared for an owner comparison. None is adopted, none is owner canon, and this is not a campaign or permission to build anything. Each states an actual proposed truth rather than a tease. No hour counts are claimed, and no room or cast catalogue is proposed.

One thing true of all three. In every direction, revival ends when the astronaut leaves. That is not a point of difference and none of them is uniquely a dilemma for it. They differ in what the player does once they could leave, and in what the deeper story asks of them.

1. The Registry

Pitch. The station is squatting inside an alien port authority that is still doing its job, and the job is keeping berthed ships' crews complete.

The truth. Infrastructure for registering and servicing visiting vessels. While a vessel sits berthed and flagged in distress, the authority maintains its declared complement, reinstating a crew member to the berth when the complement falls short. The human station is an unlicensed salvage yard cut into that port, selling berth services it never owned — which is what makes it unofficial.

The creatures are complements of vessels that berthed long ago and never left, reinstated far too many times. The warning is the yard crew's: they understood, and stopped answering so no further complement would be registered.

Revival lands aboard this ship because pattern and return point were both fixed at registration, when the ship docked. The authority does not re-survey, and a vessel cannot file again while flagged in distress, so the berth stays the return point however deep the astronaut goes. The pack is excluded because the remit is the complement — persons, declared at registration — and it never registered cargo.

Escape is repairing the ship and clearing the distress flag. Clearing it deregisters the complement, so revival ends at that visible, deliberate act.

Early interpretation. Infection. Bodies, hostility, a quarantine warning, a fled crew.

Two discoveries that change it. First, a berth cradle holding several bodies of one person at different degrees of completeness, in sequence, under the authority's marks — the same face repeatedly, incomplete. Second, and more consequential, the berth register itself: an addressable list of vessels still flagged in distress, most of them long gone, each with a complement the authority is still maintaining. The first suggests a process; the second says how many.

What the player then does. The horde stops being weather and becomes a consequence with an address. The player can go and clear other berths, which permanently reduces what walks the station, and each one is a place, a reading task and a decision about whether the complement in it is owed anything.

The two languages. The authority's operational script is procedural — berths, services, permissions, and the service and access marks already in use. It lets the player work fittings and move through the structure. The clients' language is a records language: declarations, manifests and complaints filed by visiting species. It is what makes the berth register legible, and therefore how the player learns where to go.

A survivor. Yeva worked the yard's berth interface for years and knows the operational script by rote; she can say what any fitting does. She has never read a client filing, and assumed the reinstatements were the yard's own salvaged tech being abused. Her expertise is real and her frame is wrong.

Apparent ending, and after. Clearing your own flag opens the door — complete and earned. Play can continue with the flag cleared and death now final: a changed phase chosen in the open, not hidden permadeath. The deeper action is releasing the other complements berth by berth, ending the horde at its source instead of fighting it.

2. The Ship's Own Unit

Pitch. Three unrelated problems in one place, and the strangest thing here came with the astronaut.

The truth. A refuge built by people hiding from a pursuit, on an old alien relay they barely use. The warning is human and moral: they were sheltering people who could not be found, and a docked ship means a manifest, a log and a witness. The creatures are a containment failure of biological cargo they were moving — unconnected to the relay, the warning or the revival.

Revival is the astronaut's own ship's medical unit: ordinary human equipment, legally required for long-haul solo flight, needing continuous power and a berth to run its cycle. The station supplies both. It lands aboard this ship because it is this ship, and excludes the pack because it reinstates a person from the medical bay and knows nothing of what they carried. Escape is undocking with power intact; the cycle stops.

Early interpretation. The station is doing it. Everything strange is here, so the strangeness must be local.

Two discoveries that change it. First, in the astronaut's own ship: a service record showing the unit was inspected and signed off before departure. Second, another wreck docked at the same station whose crew plainly did not come back — no unit, or no power. Revival is a property of the ship, not the place.

What the player then does. Escape stops being a matter of defeating the station and becomes an engineering problem: repair, keep power, undock. The horde is reframed too — not returns, not a mystery, a contaminated hold that can be dealt with by conventional means. And the human question stops being a clue and becomes a choice about people.

The two languages. The relay-builders' operational script is what the refuge was built on and lets the player use the structure — routing, passages, seals. The relay's traffic record explains nothing about revival: it holds what has passed through this region, including whether the pursuit the refugees fled ever came this way. Here the second language serves the human story rather than the mechanism, which is the point of it.

A survivor. Dorn knows the refuge's history and the breach in fine detail, and believes the station causes the revivals because the station is the only strange thing he knows of. He is wrong, honestly: nobody aboard had reason to read a visiting ship's service log.

Apparent ending, and after. Repair, undock, leave, with the refuge's people aboard or not. The deeper action is reading the relay's traffic record to learn whether the pursuit ever passed, then deciding what to do with the answer — carry these people away, or leave them where they cannot be found. A later playable choice, not backstory after credits.

3. The Clinic

The third direction is required to avoid another registry, stored person or reconstruction of identity. This is a fair attempt at one, and I think it stands.

Pitch. The station was an illegal clinic, and its triage system has never been told to stop.

The truth. An unlicensed clinic hulk doing experimental work that could not be done anywhere lawful — exactly why it is unofficial. Its automated triage still runs: it detects a casualty in its volume, retrieves the body, resuscitates it, and delivers the patient to their vessel of record. Nothing is stored and nothing is reconstructed — the body is recovered and restarted, which is why what comes back is the astronaut rather than a copy.

The creatures are former patients, the failures of that work, still in the wards. The warning was left by staff who fled when the wards breached. Revival lands aboard this ship because the vessel of record is set by the arrival manifest at the airlock, the only place the astronaut was ever admitted, and it never updates because they were admitted once. The pack is excluded because triage recovers a patient, not equipment.

Escape is discharge. Triage will not release a patient it holds as untreated, so departure means being discharged or shutting triage down, and revival ends at that point.

Early interpretation. A derelict overrun by something, with an inexplicable resurrection attached.

Two discoveries that change it. First, the retrieval itself becomes observable: drag marks, a cleared route, and a ward bay whose restraints and equipment are for people rather than storage. Second, a treatment record naming a patient the player has already met as a creature — with a date, a procedure and a consenting signature that was not theirs.

What the player then does. The horde becomes people who were done to, which changes what fighting them is without making them harmless. And the player has a reason to go deeper that is not power: the records say who authorised this.

The two languages. The clinic's operational script covers the hulk as a machine — doors, wards, service fittings. The second is clinical: procedures, dosages, patient notes. Reading it is what turns a creature into a name with a date, and it is the only route to who commissioned the work.

A survivor. Yeva was engineering staff, not clinical. She can get the player anywhere in the hulk and knows exactly which systems still run. She never saw a patient record, believed the wards were a quarantine, and has been carrying that belief for a long time.

Apparent ending, and after. Discharge and departure — complete on its own. The deeper action is recovering the clinical records and getting them off the station and out, which is a distinct thing to do rather than a fact to learn: evidence that someone commissioned this, carried out by a player who now knows what the wards were.

Where it is weakest. Its horde is the most narratively loaded of the three, and a design that wants ordinary combat throughout has to be careful that every fight does not become a moral event.

Preference, rival, and what I accept

I prefer the Registry. Its deeper action is the strongest of the three, because it is the only one where understanding the mystery changes the ordinary business of play: clearing other berths reduces the horde permanently, so the deeper story is expressed through the same activities the player has been doing all along rather than through a separate errand at the end. It also gives both languages real and different jobs, one to work the station and one to find the work worth doing.

Strongest rival: the Clinic. Its truth is the most human and its second language has the sharpest payoff — a creature becoming a named person with a date is a better single moment than anything in the Registry. I rank it second only because its deeper action ends in leaving with evidence, which is a weaker use of a station the player has spent the game learning to move through.

The cost I accept by preferring the Registry. It is the direction most likely to make the player feel that the setting is a machine rather than a place, and its complements-and-registers vocabulary can go cold. The Ship's Own Unit is the warmest of the three and I am not choosing it, which means accepting a colder frame in exchange for a deeper action that uses the whole game.

Questions that genuinely need the owner

1. Should the horde have an author? In the Registry and the Clinic the creatures are consequences of what this place did; in the Ship's Own Unit they are an accident with no meaning. This decides the tone of every fight and cannot be settled from the brief.
2. Should the deeper resolution be something you do here, or something you take away? Clearing berths keeps the player in the station; carrying out evidence or a decision about hidden people points them outward. Both are coherent endings to the same premise.
3. Should the mortal phase after the apparent ending exist at all? Every direction can either end at the door or let the player stay with death now final. That is a substantial change in what the last part of the game is, and it is a taste question rather than a design deduction.

Unresolved

Which direction, if any, to develop; what the second language actually says in each; and whether the mortal phase is a phase or a full alternative mode. Nothing here establishes that any of it is enjoyable.