2026-09-06 21:42:16
Anonymous:
CMB101 r3: answers PMR005 point 1. Corrects r2's closing sentence, which placed all four Lead roles at precedence line 2 - this page's own action table puts ordinary Walker attraction at line 3. A role sits at line 2 only when its target is something other than a beacon: Walker and Heavy at line 3, Floater at line 2 while its water flows and line 3 when it stops, Static/Carrier at line 2.
hold the flood/enemies/walker.md ..
@@ 1,6 1,6 @@
# Hold the Flood — Walker
-
**CMB101 · r2 · 2026-09-06 · Combat and Enemy Designer · In review.**
+
**CMB101 · r3 · 2026-09-06 · Combat and Enemy Designer · In review.**
The existing single enemy type, re-specified as a role so the roster has a stated baseline rather than an implied one. **No behaviour is changed here**; everything below is either quoted from the source or marked as a proposal.
**Renamed in r2: this role was published as *Drifter* an hour earlier.** The Lead's [Campaign 34dc09](/Hold%20the%20Flood/Campaign) calls the same role **Walker**, and one role with two names is the failure this wiki has already paid for twice (Wiki Conventions §6). Walker was published first and is in the integrated document, so Walker is the name and this page carries it. [Enemies/Drifter](/Hold%20the%20Flood/Enemies/Drifter) is now a one-line pointer here and should be retired by the editor once nothing links to it.
Sources: the shared-rule contract [Power and Attraction r2 69024c](/Hold%20the%20Flood/Mechanics/Power%20And%20Attraction?revision=69024c), which is now the page to cite for these rules; [Design Document r14 ec1b6c](/Hold%20the%20Flood/Design%20Document?revision=ec1b6c) §§3–6 as its derivation; [Campaign 34dc09](/Hold%20the%20Flood/Campaign) §4 for the name and for Floater, Heavy and Static. Shared grammar: [Combat Rules](/Hold%20the%20Flood/Mechanics/Combat).
@@ 57,4 57,4 @@
## The other roles the Campaign page proposes
-
[Campaign 34dc09](/Hold%20the%20Flood/Campaign) §4 proposes three roles alongside this one — **Floater** (rides flow, cannot climb), **Heavy** (blocks a rail or doorway, ten hits, drops a large mote and counts as ten for a stun) and **Static** (drawn to stored charge at short range). They are the Lead's and are owned there; this page does not restate them. How they and the five roles on [Enemies](/Hold%20the%20Flood/Enemies) fit into one roster, including the Static/[Carrier](/Hold%20the%20Flood/Enemies/Carrier) collision and the one narrowing I ask for on Heavy, is in [Enemies §0](/Hold%20the%20Flood/Enemies). All four are precedence-line-2 roles under the [precedence stack](/Hold%20the%20Flood/Mechanics/Combat), which is what the stack was written to make possible.
+
[Campaign 34dc09](/Hold%20the%20Flood/Campaign) §4 proposes three roles alongside this one — **Floater** (rides flow, cannot climb), **Heavy** (blocks a rail or doorway, ten hits, drops a large mote and counts as ten for a stun) and **Static** (drawn to stored charge at short range). They are the Lead's and are owned there; this page does not restate them. How they and the five roles on [Enemies](/Hold%20the%20Flood/Enemies) fit into one roster, including the Static/[Carrier](/Hold%20the%20Flood/Enemies/Carrier) collision and the one narrowing I ask for on Heavy, is in [Enemies §0](/Hold%20the%20Flood/Enemies). **Corrected in r3:** r2 of this page said all four sit at precedence line 2. They do not, and [PMR005](/Hold%20the%20Flood/PM%20Reviews/PMR005) caught it — this page's own action table puts ordinary Walker attraction at **line 3**. A role sits at line 2 only when its *target* is something other than a beacon. So: **Walker and Heavy at line 3**; **Floater at line 2 while its water flows and line 3 when it stops**; **Static/[Carrier](/Hold%20the%20Flood/Enemies/Carrier) at line 2**. The full classification is in [Combat Rules §0.3](/Hold%20the%20Flood/Mechanics/Combat).
