# Debris Anything loose in the shaft that can hit you. Spawned by `game.hazards.buildRig()`; not authored into the scene. Two kinds, one behaviour, because a structural member that has let go **is** debris. | `kind` | while `released` is false | once released | |---|---|---| | `"brace"` | a cross-member of the truss: static structure, part of the wreck, holding. Visible from the first second of the run at instability 0. | sweeps the shaft on the drift it was built with, at `hazards.CFG.braceSpeed`, tumbling. Leaves the shaft volume and goes dark — a collapsed member does not come back. | | `"chunk"` | (chunks start released; the director sleeps and wakes the entity instead) | crosses the route rather than running along it, and wraps back in at the far side, so the shaft never quietly clears itself. | `HazardDirector` decides **when** a brace lets go and **how many** chunks are awake — a disabled entity does not tick, so a sleeping chunk cannot wake itself. ## Contact A sphere overlap against the local player's body, `radius + suitRadius`, one hit per `hitCooldownSec`. On contact it: - emits `impact(damage, "collapse")` or `impact(damage, "debris")` — `shell` owns what that costs; - calls `hazards.impulse` with the piece's own velocity plus a kick away from it, so being hit by a moving mass sends you the way it was going. It never writes the player's transform and never writes `state.integrity`. ## Fields worth reading from outside `released`, `hits`, `travelled` (metres since release).

# rules <!-- zero:scaffolded-readme --> <!-- Replace the line below with what this module provides and who consumes it, then delete both comment lines. --> TODO: describe this module.

# PressureVent A relief port on the Kestrel Wake that no longer holds. Spawned by `game.hazards.buildRig()`; not authored into the scene. A vent is a **rhythm, not an ambush**. It rests, then the lip lights up and a stub of plume shows for a beat and a quarter, then it blows for a beat and a third. The glow is the contract with the player: you can see it coming — and if you are still hauling a tonne and a half of plate down the middle of the shaft when it goes, seeing it coming was not enough. ## Escalation Armed from `instability` 1 (`RULES.CFG.ventAtInstability`). The rest between bursts shortens with every plate taken off the wreck; the charge and the burst stay the same length, because those are the two windows a player has learned to read. At instability 0 it never cycles and the plume is not drawn at all. ## What it does to you Inside the jet cone it calls `hazards.impulse` every frame — the shove has to be sustained to take you off your line, not a single knock. Two things keep it a hazard rather than an ejector seat: - **Radial falloff.** Strongest down the axis, nothing at the rim, so clipping the edge of a plume costs a correction and not the level. - **A per-burst budget** (`hazards.CFG.ventMaxDeltaV`, 6.5 m/s). In a game with no drag an uncapped jet is a catapult: sit in one for its whole burst and you leave the wreck. With the cap a vent costs a known amount of speed to correct — about two seconds on the RCS brake. The first frame the player is caught it emits `impact(impactAmount, "vent")` once. It never writes the player's transform and never writes `state.integrity`. ## Fields worth reading from outside `firing`, `charge` (0..1 warning ramp), `fires`, `hits`. `look` can hang the lip's emissive off `charge`; `shell` can warn off `firing`.

# Scrapper The suit. Everything that moves the player in HULLBREAKER happens in this component and nowhere else. Vacuum has no drag, so `Scrapper` integrates a velocity that nothing ever takes away. Thrust adds to it, the RCS brake subtracts from it and charges propellant for the privilege, and letting go of the controls changes nothing at all. Clamp a plate and its mass folds into every one of those numbers: you start slower, you stop far slower, and the shaft is narrower than you remember. Put it on the player's body. The scene's PlayerPrototype clones one per joining scrapper, and each instance answers only to the client that owns its body. ## Controls | Control | Keyboard | Gamepad | Touch | |---|---|---|---| | Move (thrust in the helmet's plane) | `WASD` | left stick | left stick | | Look | mouse | right stick | drag, right of screen | | Thrust up | `Space` | right shoulder | **Thrust Up** | | Thrust down | `Ctrl` / `C` | left shoulder | **Thrust Down** | | Burn (hard acceleration) | `Shift` | right trigger | **Burn** | | RCS brake | `Q` | left trigger | **RCS Brake** | | Magclamp (grab / release) | `F` | west face button | **Magclamp** | Move and look come from `@builtin::inputMaps.default`; the other five are `game.scrapper`, which composes beside it. ## What other systems call ```lua local suit = entity(bodyId).component.get("Scrapper") suit:applyImpulse(dx, dy, dz) -- world-space delta-v, m/s suit:applyForce(dx, dy, dz, dt) -- the same, held for dt seconds suit:velocityAt() -> vx, vy, vz suit:isCarrying() -> carrying, tonnes, pieceId suit:halt() -- bring the suit to rest, spending no propellant ``` `applyImpulse` is the only sanctioned way to move the scrapper from outside this slice — a pressure vent, a collapsing beam, a piece of debris all push the player through it. The shove is scaled by whatever is on the clamp, so a loaded scrapper is harder to knock off line, and the plate is carried through the shove with them. ## What it reports `speed`, `carrying`, `carriedPiece` and `clampReady` are live public fields a HUD can read every frame. `carrying` is also mirrored onto `game.rules`' run state, and the clamp announces itself on the event bus as `clamped`, `released` and `deposited`.