**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](/Hold%20The%20Flood/Combat%20Rules); 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.
+
**Status.** A working encounter proposal after focused review; its frequency and quality remain unvalidated. 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](/Hold%20The%20Flood/Combat%20Rules); this article applies them to the player experience. No enemy roster, campaign map or balance figure is proposed, and nothing here establishes that any of it is enjoyable.
## The area
@@ 18,17 18,17 @@
**With the Relay Cascade Array.** Ordinary fire is mostly automatic and special abilities are triggered by hand (owner requirement), so the player's decisions here are where to stand, which way to press, and when to spend a special — not whether each shot connects. Density is the Array's best case: moving into the packed middle puts its automatic output where the chain has most to branch through, and the run empties. That is simply a win: the run's crowd is gone for this expedition, and the player has bought the direct route and the oxygen they would 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.
-
What it does not buy is a quiet door. The run up to the door vestibule is this encounter's boundary; clearing it does not defeat the caller beyond, or consume groups in connected spaces. Nor does "clear" mean sealed: something living outside can later walk in along a real route, always cued by sight, sound or door movement, never behind the player.
+
What it does not buy is a quiet door. The run up to the door vestibule is this encounter's boundary; clearing it does not defeat the caller beyond, or consume groups in connected spaces. Nor does "clear" mean sealed: something living outside can later walk in along a real route, cued by sight, sound or door movement along that connected route. It does not spawn as a penalty for clearing the crowd.
**With the Cargo-Cycler Rig.** The Cycler does not clear the run and does not need to. A shove displaces the middle group off the left wall — displacement, not a wall, since nothing here builds a lasting barrier — and a fragment burst opens a lane long enough to cross. The run stays occupied behind the player, which matters on the way back.
-
**The two rigs spend differently, and neither is simply cheaper.** The Array's modules occupy carrying space permanently but are not consumed per use, so its clearing costs capacity decided at the ship. The Cycler keeps capacity flexible but spends chosen salvage each time, so its lane costs colony-bound material during the trip. Which is dearer depends on what is scarce that expedition.
+
**The two rigs spend differently, and neither is simply cheaper.** The Array's modules occupy capacity while carried but are not consumed per use. Keeping or changing that loadout commits space; equipment can still be acquired, removed or left during an expedition under the build rules. The Cycler keeps capacity flexible but spends chosen salvage each time, so its lane costs colony-bound material during the trip. Which is dearer depends on what is scarce that expedition.
-
**Why fight rather than pass.** One honest reason, not two: this is where an expressive rig becomes visible and enjoyable, and clearing the run is the payoff for the parts committed to it. Fighting also buys the direct route. It does *not* buy the alcove — that anomaly is visible to anyone who looks, and a player who slips past sees it just as well. Enemy behaviour is legitimate information; it is not a reward for combat, and manipulating it is not the experiment.
+
**Why fight rather than pass.** The intended payoff is seeing an assembled rig clear the crowd and win direct access. The alcove is also visible to someone who slips past; noticing it does not require a fight. Enemy behaviour is legitimate information; it is not a reward for combat, and manipulating it is not the experiment.
-
**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.
+
**Withdrawal.** The player can attempt to reach the junction past occupants and pursuers. Enemies continue pursuing while they perceive the astronaut, then search and settle after losing the cue. Withdrawal spends time and oxygen and may defer the objective.
-
**On return.** A later expedition finds a different population and density here. What the player deliberately changed persists; the crowd does not.
+
**On return.** A later expedition may change population and density. Deliberate persistent changes and recorded evidence follow the exploration rules; the earlier clearance is not a guarantee for a new expedition.
## Encounter two — the jammed door
@@ 38,21 38,21 @@
**The pressure is caused, not scheduled.** Nothing escalates because the player is doing something interesting. The door grinds, and grinding is a physical event ordinary enemies come to look at. This example also holds one caller — an ordinary enemy that, allowed to finish its warning, brings a group from the adjacent space. Before committing to the first bolt the player can see or hear it, recognise its warning behaviour, and see the connected entrance it would summon from. Dealing with it first is a real priority decision with a readable consequence. Ordinary fire takes the nearest valid target, so reaching the caller with it means positioning until nothing else qualifies first — which may mean clearing what stands between. The alternative is spending a manual special to stop the warning in time. That is the choice: rearrange yourself, or spend something. The run in encounter one has no such source.
-
**Decisions, and what they cost.** Clear the approach and the caller first, then work undisturbed, spending build resources up front. Work in bursts between arrivals, using a Cycler shove to displace what arrives and buy stages — displacement, not a barrier. Or take what has been done and leave.
+
**Decisions, and what they cost.** Resolve the caller/source, present enemies and travelling groups before working, committing the relevant equipment or inputs up front. A separately cued later arrival can still change the situation. Work in bursts between arrivals, using a Cycler shove to displace what arrives and buy stages — displacement, not a barrier. Or take what has been done and leave.
-
The middle option has a price that lasts: taking hits spends condition, and lost condition does not come back in the field. It narrows the margin before a damage death for the rest of that expedition, including the walk home. So working under fire is not free just because damage cannot cancel a stage — it borrows against every later margin on the trip.
+
The middle option has a price that lasts: taking hits spends condition, with no passive field recovery in this proposal. Field healing is not specified here. It narrows the margin before a damage death for the rest of that expedition, including the walk home. So working under fire is not free just because damage cannot cancel a stage — it borrows against every later margin on the trip.
**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 are checkpoints and do not roll back. 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: the trip that ends here bought fewer stages than it hoped, and the bolts already cut stay cut.
Backing out is a route decision, not a guarantee. The way to the junction can be held by something, and choosing to leave is not the same as being able to.
-
**With the Array.** Clearing the approach outright means the door is finished without interruption. That success is not clawed back.
+
**With the Array.** Resolving the door area’s caller/source, present enemies and travelling groups buys quiet working time. A separately cued arrival can still interrupt it; clearing the run alone does not settle this area.
-
**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.
+
**With the Cycler.** A shove can temporarily displace the approach’s occupants, spending salvage to buy a work window. It creates no lasting barrier or established cost advantage; its value depends on the situation and available inputs.
**Room to think, stated precisely.** The journal pauses enemies, oxygen and action progress, so *reading* stored records and the already-visible frozen view is free. Capturing is not: framing and committing a record of the painted mark on this door frame is a world-time action, and physically studying it spends oxygen while the run's occupants keep moving. Looking raises no attention by itself, but it is not outside time. Thinking over what is already held is protected; getting new evidence into the journal is priced.
-
**On return.** Cut bolts and completed cycles are deliberate physical changes and persist across expeditions; the population around them does not. What can still block progress is a genuine new change — the door's feed losing power, a bolt re-jammed since. That prevents the *next* stage without rolling back a completed one, and must be an authored change the player can read, never a quiet reset of earned work.
+
**On return.** Cut bolts and completed cycles are deliberate physical changes and persist across expeditions; the population around them does not. What can still block progress is a genuine new change — a new visible obstruction or an engaged powered brake. That prevents the *next* stage without rolling back a completed one, and must be an authored change the player can read, never a quiet reset of earned work.
## Comparison
@@ 61,7 61,7 @@
| Objective | Cross the run | Finish a staged job |
| Information before commitment | Density, spread, one anomaly | Door state, approaches, a visible caller |
| Main decision | Where to go and what to spend | Whether to clear first, work between arrivals, or stop |
-
| Reason to fight | Build expression; a readable oddity | Uninterrupted stages |
+
| Reason to fight | Build expression; clear direct access | Quiet working time for stages |
| Cost of leaving | Time and oxygen | Time, oxygen and the unfinished stage |
| On return | Different population | Persistent work, different population |
@@ 69,15 69,15 @@
**The route crowd should be the ordinary case; the contested mechanism should be occasional.**
-
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 with frequency. If every world-time action is harassed, causal pressure starts reading as a trigger attached to interesting objects. Rare, it lands; constant, it becomes suspicious.
+
Contested actions can tie combat closely to the immediate objective. Making that pressure common may also produce a repetitive “activate, defend, inspect” pattern. The proposed lower frequency follows that risk judgment; it does not establish that occasional versions work better.
Route crowds carry the ordinary rhythm better because they ask a question with several legitimate answers — fight, slip past, go round — none of which is a failure state.
-
**How the preference is applied, since frequency is not a dial.** Pressure is caused, not scheduled, so "occasional" is not set directly — it is an outcome of placement, which is where the choice actually lives: how many of an area's world-time actions are loud ones like bolt-cutting rather than quiet ones; whether a mechanism sits in a connected area holding population or off a dead run where grinding reaches nobody; whether an area has a caller or alarm source at all; and how entrances connect, since a cued approach from a known direction reads differently from one the player cannot anticipate. Choosing this rhythm means authoring those causes deliberately. No frequency figures are proposed.
+
**How the preference is applied.** The intended frequency is expressed through placement: how many of an area's world-time actions are loud ones like bolt-cutting rather than quiet ones; whether a mechanism sits in a connected area holding population or off a dead run where grinding reaches nobody; whether an area has a caller or alarm source at all; and how entrances connect, since a cued approach from a known direction reads differently from one the player cannot anticipate. Choosing this rhythm means authoring those causes deliberately. No frequency figures are proposed.
-
**What the branch offers, since the comparison leans on it.** Here the branch that avoids the run loops behind the alcove and reaches it from the far side, so a player who declines the crossing meets the same anomaly from an angle the run never shows. That is one worked example, not evidence that detours generally pay: the claim that unplanned routes produce discovery is a prediction resting on placement doing that work.
+
**What the branch offers.** Here the branch that avoids the run loops behind the alcove and reaches it from the far side, so a player who declines the crossing meets the same anomaly from an angle the run never shows. That is one worked example, not evidence that detours generally pay: the claim that unplanned routes produce discovery is a prediction resting on placement doing that work.
-
**Strongest alternative.** Make contested actions the default. It gives a tighter, 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 proves unfounded, it is the better arrangement.
+
**Strongest alternative.** Make contested actions the default. Its strongest case is a more consistent link between combat and the immediate objective. It remains credible if that rhythm proves desirable and the repetition risk is smaller than expected.
**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.
