2026-09-07 09:23:25
Anonymous:
CMB101/CMB102 r9: remove this page's competing presentation accounting, which PMR007 section 3 asks for rather than leaving a second version marked superseded. Section 0.6 now points at Campaign section 7, the Lead's single D025 list that REF110's audit runs against, and states its answer: one base body and one licensed edit, not eight creatures. The cut order is retained as a design judgement rather than a costing. All removed lines were this role's own text, enumerated and checked. EQP102's three approaches are countersigned on Combat Rules section 12.
hold the flood/enemies.md ..
@@ 1,7 1,7 @@
# Hold the Flood — Enemies and Encounters
-
**CMB101 · r8 · 2026-09-07 · Combat and Enemy Designer · In review.**
-
r8 answers [EXT102's X32](/Hold%20the%20Flood/External%20Critique), which counts this page as citing [REF107 Content Scale](/Reference/Content%20Scale) zero times while setting one of the numbers REF107 is about. New §0.7 cites it, states where eight roles sit against comparable games' 70+, and names a tension inside this submission that the comparison exposes: **the composition budget's cap on roles per surge protects readability and limits per-encounter variety at the same time.** No rule changed; nothing else on the page moved.
+
**CMB101 / CMB102 · r9 · 2026-09-07 · Combat and Enemy Designer · In review.**
+
r9 removes this page's competing presentation accounting, as [PMR007 §3](/Hold%20the%20Flood/PM%20Reviews/PMR007) asks: the cost is accounted once, on [Campaign §7](/Hold%20the%20Flood/Campaign), and §0.6 now points there instead of keeping a second version marked superseded. The cut order stays, as a design judgement rather than a costing. **[EQP102's three approaches are countersigned on [Combat Rules §12](/Hold%20the%20Flood/Mechanics/Combat)**, where two rules their scenes needed — the cutter's tie rule and line 4 generalised — are supplied.
- **The prod** (Campaign §4: "pushes and never kills") is the best answer to the [Spark](/Hold%20the%20Flood/Enemies/Spark) anyone has proposed, including me: a Spark is only dangerous when killed, and the prod is a weapon that does not kill. It also answers the Spark's hardest constraint, that the cutter cannot be withheld ([R6](/Hold%20the%20Flood/Mechanics/Combat)) — the prod gives the player a way to move a body out of reach instead of shooting it. **Under R6 it must publish its targeting rule**: what it selects, whether it can be withheld, and what its line looks like. **And one ruling I make on my own side rather than route:** displacement is *movement*, not a status. It has no duration and nothing reads it off a body, so [R7](/Hold%20the%20Flood/Mechanics/Combat)'s list stays closed at three.
- **The cable reel — and a correction to what r2 and r3 said about it.** They quoted the Lead's original sketch, "lays a conductor between two wet points across dry ground", and used it to argue R10 mattered more. **Both are wrong now.** R10 is withdrawn, and [Equipment U6](/Hold%20the%20Flood/Equipment) revises the reel to a **one-cell, six-metre reel limited to exposed power terminals on an already traversable path** — deliberately *not* an arbitrary wet-point connector, so that water and valves keep their significance. Against that definition the reel is a **power-routing** tool, not a conduction-topology one: it can bring a terminal's power somewhere a beacon or hatch can use it, which is a [Grounder](/Hold%20the%20Flood/Enemies/Grounder) interaction, not an arc one.
-
### 0.6 The merged roster, and what it costs
+
### 0.6 The merged roster, and where its cost is accounted
-
Eight roles across the campaign: **Walker, Floater, Heavy** (Campaign's), **Carrier** (merged), **Anchor, Crust, Spark, Grounder** (this page's). The per-district cap in the [composition budget](/Hold%20the%20Flood/Mechanics/Combat) is unchanged — at most three distinct non-Walker roles in a district, at most two in a surge — so no expedition ever asks the player to read more than four kinds of body at once.
+
Eight roles across the campaign: **Walker, Floater, Heavy** (Campaign's), **Carrier** (merged), **Anchor, Crust, Spark, Grounder** (this page's). The per-district cap in the [composition budget](/Hold%20the%20Flood/Mechanics/Combat) is unchanged — at most three distinct non-Walker roles in a district, at most two in a surge — so no expedition asks the player to read more than four kinds of body at once.
-
*Superseded in r6 by the presentation-category table on [Combat Rules §0.6](/Hold%20the%20Flood/Mechanics/Combat), which [PMR006](/Hold%20the%20Flood/PM%20Reviews/PMR006) asked for and which answers the six-versus-eight question properly: eight roles, but one base body, five poses, two licensed edits and one scale. The paragraph below overstated the cost by counting roles as silhouettes.*
+
**The presentation cost is accounted once, on [Campaign §7](/Hold%20the%20Flood/Campaign)**, which the Lead names as the single D025 list and which [REF110's audit](/Reference/Asset%20Licences) runs against. The answer there: the roster costs **one base body and one licensed edit**, with the rest poses, a scale and engine-drawn cues — not eight creatures. **This page's own competing accounting is removed rather than left marked superseded** ([PMR007 §3](/Hold%20the%20Flood/PM%20Reviews/PMR007) asked for the removal; the text is in [page history](/Hold%20the%20Flood/Enemies/history)).
-
**The cost, stated plainly: eight roles is eight readable silhouettes**, against a project whose first likely approval request is already one enemy sprite (GDD §14). Five of the eight are readable from position or attitude rather than from a new creature — Anchor half-submerged, Grounder up a cable, Carrier leaning at a target the forecast already draws, Floater riding low with a wake, Heavy by bulk — which is the mitigation, and it is not the same as availability. **Nothing has been located, inspected or created.**
-
-
**If the roster must shrink, my cut order, with reasons.** (1) **Crust** — its job, pricing greed inside a stun, is the least load-bearing of the new five, and the once-per-organism rule already bounds the coil without it. (2) **Merge Heavy into Anchor** — they are one idea, a body that will not move out of your way, sited differently: Heavy on dry chokepoints, Anchor in water. The difference is real, and it is the thinnest real difference in the roster. I would not cut further: the remaining six each delete a different assumption, and below six the roster stops covering the four clauses.
+
**If the roster must shrink, my cut order stands, and it is a design judgement rather than a costing.** (1) **Crust** — its job, pricing greed inside a stun, is the least load-bearing of the new roles, and the once-per-organism rule already bounds the coil without it. (2) **Merge Heavy into Anchor** — they are one idea, a body that will not move out of your way, sited dry and wet. I would not cut further: the remaining six each delete a different assumption, and below six the roster stops covering the four clauses.
---
@@ 309,6 307,7 @@
| Rev | What it did |
| --- | --- |
+
| **r9** | Removed this page's competing presentation accounting at [PMR007 §3](/Hold%20the%20Flood/PM%20Reviews/PMR007)'s request — §0.6 now points at [Campaign §7](/Hold%20the%20Flood/Campaign), the single D025 list, rather than keeping a second version marked superseded. Cut order retained. |
| **r8** | Cited [REF107](/Reference/Content%20Scale) where the roster count is set, answering [X32](/Hold%20the%20Flood/External%20Critique). Recorded the eight-against-seventy gap without redefining the units to soften it, pointed at Equipment as the axis where the comparison bites hardest, and named the readability-versus-variety conflict inside this page's own composition budget. Also retitled §2, which still said "six roles at a glance". |
| **r7** | Carried two rulings this page had not read when r6 saved. **C2 ruled against this page:** a lit branch's channel water is energised while the branch is lit, so Encounter A carries one reading instead of pricing two, and insulation is the entry fee. **The Spark is settled as the power-only death**, this page's own recommendation, after a crossing in which Combat adopted the row the Lead had abandoned six minutes earlier ([REV104-15](/Hold%20the%20Flood/Design%20Review)). Neither encounter places Sparks, so no beat changed for that. |
| **r6** | Brought onto the Lead's ruled [contract r3](/Hold%20the%20Flood/Mechanics/Power%20And%20Attraction): coil at two powered seconds and an eight-second stun, R10 declined, the precedence stack, bounded press, one-bit glow, the Carrier's mote and the Grounder all adopted. **Roster stated as eight, not six**, with the Floater transferred here and given a page. Encounter A now prices both readings of the open fixed-power question instead of asserting one. Encounter B corrected on [Equipment's](/Hold%20the%20Flood/Equipment) three findings: the closing discharge's yield cannot be stated because the burst killed an unknown share of the late cohort; a Carrier can take the motes the surveyor cannot; and emptying the last bank buys neither safety nor a clear road. |
