Hold The Horde — Horde Encounters

Status. A provisional proposal for review, not owner-approved. It shows two ordinary encounters in one proposed area and argues which kind should be common. Example fiction is labelled. Rules for controls, perception, reinforcement and interruption belong to Combat Rules; this article uses them and does not restate them. No enemy roster, campaign map or balance figure is proposed, and nothing here establishes that any of it is enjoyable.

The area

(Proposed fiction.) A segment of the long service route: a junction opening onto a straight run of working light, and at its far end a pressure door jammed on its manual bolts. The run is in vacuum. Both encounters below happen here, in one trip.

Encounter one — the run

Objective. Get to the door at the far end.

What the player sees before committing. From the junction mouth the whole run is visible and lit. The crowd's spread is readable: thick across the middle, thinner along the left wall. One alcove halfway down has nothing in it, and nothing goes near it.

Decisions. Push the middle, where the crowd is densest and a cascade has the most to work with. Move along the thin wall, trading damage for exposure and timing. Or back out and take a branch route, which costs oxygen and time and is a legitimate answer, not a failure.

With the Relay Cascade Array. Density is the Array's best case: aimed into the packed middle, the chain branches through the crowd and the run empties. Per the combat contract, that is simply a win — the area stays clear for this expedition, and the player has bought the direct route, quiet working time at the door and the oxygen margin they would otherwise have spent going around. No replacement wave arrives and no compensating elite appears. A build that trivialises an ordinary crowd is the point of having built it.

With the Cargo-Cycler Rig. The Cycler does not clear the run and does not need to. A shove compresses the middle group off the left wall, and a fragment burst opens a lane long enough to cross. It costs colony-bound salvage rather than a permanent module, and it leaves the run occupied behind the player — which matters on the way back.

Why fight rather than pass. Two reasons that are not a toll. First, this is where an expressive rig becomes visible: the crowd is the canvas, and clearing it is the payoff for the parts committed to that build. Second, the empty alcove is information. Something about it keeps ordinary enemies out, and that is a fact the player can record and use without enemy behaviour becoming the subject of experimentation.

Withdrawal. Backing out to the junction is always available. Enemies search the last place they perceived and settle, and the player has spent time and oxygen, not progress.

On return. A later expedition finds a different population and density here. What the player deliberately changed persists; the crowd does not.

Encounter two — the jammed door

Objective. Cut the door's jammed bolts and hand-cycle it open — the established act on this route, using the suit's baseline cutter.

What the player sees before committing. The door's state and its remaining bolts are readable at a glance, as are the two approaches to the panel and which one has cover. So is the reason this will be harder than it looks: cutting and cycling are loud, and the run's occupants investigate loud things.

The pressure is caused, not scheduled. Nothing here escalates because the player is doing something interesting. The door grinds, and grinding is a physical event ordinary enemies come to look at. Quiet looking, moving, framing a record and reading the journal draw nothing. This example also contains one visible caller — an ordinary enemy that, allowed to finish its warning, brings a group from the adjacent area. Killing it first is a real targeting decision with a readable consequence; the run in encounter one has no such source and does not escalate.

Decisions. Clear the approach first and then work in peace, spending the build's resources up front. Work in bursts between arrivals, using a Cycler shove to block the narrow approach and buy stages. Or accept what has been done and leave.

Interruption, stated exactly. The work has named visible stages — each bolt, then each cycle of the door. Leaving before the current stage completes loses that stage and the time and oxygen already spent on it. Completed stages persist. Damage alone does not cancel the work; an enemy stops it only by a readable physical result, such as forcing the astronaut off the control. So withdrawal has a real opportunity cost without permanent loss: nothing resets, the bolts already cut stay cut, and the trip that ends here is one that bought fewer stages than it hoped.

With the Array. Clearing the approach outright means the door is finished without interruption. That success is not clawed back.

With the Cycler. Blocking the approach is cheaper than clearing it and leaves the player working with something moving nearby — a different texture, not a worse outcome.

Room to think. Between arrivals there is quiet, and the journal pauses everything, so the painted mark on this door frame can be read and recorded without the encounter punishing the reading. Pressure applies to doing, never to looking or thinking.

On return. The door's cut bolts and completed cycles are exactly as they were left. The population around it is not.

Comparison

Which should be common

The route crowd should be the ordinary case; the contested mechanism should be occasional.

This is a change from my first position, which favoured pressure-while-acting as the common rhythm, and the reason is that I had not separated which matters more from which should happen more often. Contested-action encounters are the stronger of the two — they put the price on the thing the player actually came to do — but their weakness scales directly with frequency. If every world-time action is harassed, the causal pressure starts reading as a trigger attached to interesting objects, which is the failure I named as this structure's own risk. Rare, it lands. Constant, it becomes suspicious.

Route crowds carry the ordinary rhythm better because they ask a question the player can answer in several legitimate ways — fight, slip past, go round — and because being pushed onto an unplanned route is one of the cheapest ways this design produces discovery.

Strongest alternative. Make contested actions the default. It gives a tighter and more consistent rhythm, keeps combat permanently tied to what the player is trying to achieve, and never lets fighting drift into scenery. If the trigger-feel worry turns out to be unfounded, this is the better arrangement, and it is what my own first position argued for.

Accepted costs. Two encounter kinds at different frequencies risk reading as two disconnected modes, and a player may meet contested work rarely enough not to get good at it. The alcove-style oddity depends on authored placement, so it is not free. And the claim that a powerful build needs no compensating penalty because oxygen and capacity already constrain the player is a proposal, not a demonstrated balance: those limits may or may not prove sufficient, and only later authorised observation could say.

Unresolved

How often "occasional" is; whether readable anomalies like the alcove stay interesting once their cause is known; whether route crowds without escalation sources remain tense; and the enemy roster, none of which is proposed here.