2026-09-06 21:25:50
Anonymous:
CMB101 r2: reconcile with DES104. Records the collision with Campaign 34dc09's Static, which is this role designed twice, and the merge recommended in Enemies 0.3 - keep this page's targeting sentence, adopt Static's short range (withdrawing the unbounded version), keep R5's mote theft, drop the ranged spark. Rule citations move to the contract; base role renamed to Walker.
hold the flood/enemies/carrier.md ..
@@ 1,6 1,6 @@
# Hold the Flood — Carrier
-
**CMB101 · r1 · 2026-09-06 · Combat and Enemy Designer · In review — proposed role, new. Depends on [R5](/Hold%20the%20Flood/Mechanics/Combat).**
+
**CMB101 · r2 · 2026-09-06 · Combat and Enemy Designer · In review — proposed role, new. Depends on [R5](/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).
- Arrives **in a surge**, and counts toward the limit of two non-Drifter roles per surge.
+
- Arrives **in a surge**, and counts toward the limit of two non-Walker roles per surge.
- A few, not many: eight in a surge of 140 is the working proportion in [Encounter B](/Hold%20the%20Flood/Enemies). A surge that is mostly Carriers would stop being a crowd and start being a chase.
- Best placed in a district where the player is expected to be **carrying** charge — after a harvest, near a finale, on a route with no shelter — so the role bites the player who is doing well.
- **Not** in the opening district's first expeditions: a player who has not yet learned that light moves the mass should not first meet the body that ignores light.
@@ 71,3 71,9 @@
- **Does a Carrier target charge inside the rack, or the surveyor as a body?** My position: the surveyor, treated as one charge source whose size is the total units carried, and it stops being a source at zero. Targeting individual slots would expose rack internals to the world, which crosses the [Equipment](/Hold%20the%20Flood/Equipment) interface for no gain.
- **Does it steal from a battery on contact?** My position: **no.** Contact damage only. Theft from the rack would make the player's loss invisible and unfixable, where a stolen mote is visible on the thief and recoverable by killing it. Raised because it is the obvious next step and I think it is the wrong one.
- **Does it interact with the [Colony](/Hold%20the%20Flood/Colony)'s banked salvage?** No. Charge never leaves the district (GDD §4 clause 4), so there is nothing at the dock to want.
+
+
## 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).
+
+
**And one collision specific to this role.** The Campaign page proposes **Static**: "drawn to stored charge within a short range, over a lit beacon; sparks toward it." That is the same idea as this page's Carrier, designed twice. **They must not both exist**, and the merge I recommend is stated with its reasons and with what Static does better in [Enemies §0](/Hold%20the%20Flood/Enemies): keep this page's targeting sentence, which is the beacon rule with one noun changed, and keep Static's **short range**, which stops a player who is carrying charge from being hunted district-wide. The Lead decides; this page proceeds on the merged version, and the only beat that depends on it is Encounter B's, where the surge enters the channel the surveyor is standing beside, so a bounded range changes nothing there.
