2026-09-06 21:25:50
Anonymous:
CMB101 r2: reconcile with DES104 - rule citations move to the contract, base role renamed to Walker. No behaviour changed; Campaign's prod is noted in Enemies 0.5 as the best answer to this role anyone has proposed.
hold the flood/enemies/spark.md ..
@@ 1,6 1,6 @@
# Hold the Flood — Spark
-
**CMB101 · r1 · 2026-09-06 · Combat and Enemy Designer · In review — proposed role, new. Depends on [R3](/Hold%20the%20Flood/Mechanics/Combat) and, for its late payoff, [R10](/Hold%20the%20Flood/Mechanics/Combat).**
+
**CMB101 · r2 · 2026-09-06 · Combat and Enemy Designer · In review — proposed role, new. Depends on [R3](/Hold%20the%20Flood/Mechanics/Combat) and, for its late payoff, [R10](/Hold%20the%20Flood/Mechanics/Combat).**
Source rules it is built on: [Design Document r14 ec1b6c](/Hold%20the%20Flood/Design%20Document?revision=ec1b6c) §§3–6; shared grammar and the precedence stack: [Combat Rules](/Hold%20the%20Flood/Mechanics/Combat).
- **Zero Sparks in a surge entering dry ground.** A Spark that cannot reach water is a [Drifter](/Hold%20the%20Flood/Enemies/Drifter) with a worse silhouette, and placing one is a wasted role slot. This is a hard constraint in the composition budget, not a preference.
-
- Arrives in a surge; counts toward the limit of two non-Drifter roles per surge.
+
- **Zero Sparks in a surge entering dry ground.** A Spark that cannot reach water is a [Walker](/Hold%20the%20Flood/Enemies/Walker) with a worse silhouette, and placing one is a wasted role slot. This is a hard constraint in the composition budget, not a preference.
+
- Arrives in a surge; counts toward the limit of two non-Walker roles per surge.
- Proportion: around 7% in [Encounter B](/Hold%20the%20Flood/Enemies) (10 of 140). Enough that a channel crowd reliably contains some; few enough that a player wading a channel is not in continuous danger.
- **Not in the opening district's first expeditions.** A player still learning that water is a weapon should not simultaneously learn it is a trap. Middle campaign is the right entry point, and by then insulation is a module they have met.
@@ 66,3 66,7 @@
- **Does a Spark killed in water hurt other organisms?** My position: **yes** — energised water conducts to everything the water connects, and clause 1 does not care what a body is. Consequence: a dense crowd wading with Sparks in it is partly self-destroying, which is a nice thing for a player to *discover* rather than be told. It also means the discharge is a legitimate weapon when the player is on the bank.
- **Does a stunned Spark killed during a stun discharge?** My position: yes. Stun prevents acting, not physics; the body is still full of charge. Flagged because a designer implementing "stunned bodies do nothing" would get this wrong.
- **How long is the energised second, exactly?** Tied to [R3](/Hold%20the%20Flood/Mechanics/Combat) / open question C1, which the Lead owns. The Spark deliberately reuses whatever number the coil uses, so there is one quantity to learn rather than two.
+
+
## Reconciliation with DES104 (added in this revision)
+
+
The Lead published [Campaign 34dc09](/Hold%20the%20Flood/Campaign) and the shared-rule contract [Power and Attraction r2 69024c](/Hold%20the%20Flood/Mechanics/Power%20And%20Attraction?revision=69024c) while this page was being drafted. Two consequences for this page. **The rule source is now the contract, not GDD §4** — where this page cites the Design Document for a shared rule, cite the contract; the rules are the same and it is the one to cite. **The base role is called Walker there**, and this page's Drifter is the same role; Walker is the surviving name and [the role page is at Walker](/Hold%20the%20Flood/Enemies/Walker). The full reconciliation — what held, what conflicts, and the merged roster — is in [Enemies §0](/Hold%20the%20Flood/Enemies).
