Blame
|
1 | # Hold The Horde — Design Plan |
||||||
| 2 | ||||||||
|
3 | You leave home with a modest rig, fight through a growing horde, discover a powerful interaction between your equipment and the station, and return with something that changes the next expedition. That sequence must be exciting on the third trip as well as the first. |
||||||
|
4 | |||||||
|
5 | ## The current design |
||||||
|
6 | |||||||
|
7 | The owner chose fresh hordes each expedition and regular combat growth with larger transformations. Permanent changes and physically carried property remain, while temporary power resets on returning home. The [Owner Brief](/Hold%20The%20Flood/Brief) records the requirements. |
||||||
|
8 | |||||||
|
9 | The main reading path now begins with [The Game](/Hold%20The%20Flood/The%20Game), follows [three expeditions](/Hold%20The%20Flood/Expedition%20Proposal), returns to [the people aboard](/Hold%20The%20Flood/Coming%20Home), and opens into [discovery in the changing station](/Hold%20The%20Flood/Connecting%20The%20Station). [Hordes and Builds](/Hold%20The%20Flood/Hordes%20and%20Builds) explains the current examples; [Build Comparison](/Hold%20The%20Flood/Build%20Comparison) presents alternative controls and payoffs for owner reaction. |
||||||
|
10 | |||||||
|
11 | Fifteen proposal or editorial packages completed review and response today: builds/expeditions, hospital story/survival, regular growth on a renewed route, a second route state after permanent source seals, the six-page reading path, the moving-scan expedition, the short-rescue comparison, the station-completion payoff, the campaign scope comparison, the language journal, the whole-campaign overview, the cast and rescue map, the equipment guide, the Receiver Vault expedition, and the enemy guide. [Combat Rules](/Hold%20The%20Flood/Combat%20Rules) and the room/encounter references describe the two concrete route states. They preserve completed work while giving fresh opposition a physical route. Other seal combinations and shifted layouts remain design work. |
||||||
|
12 | |||||||
|
13 | The new Ricochet and Gravity mechanisms remain proposed replacements for parts of the detailed build rules. The [hospital-story alternatives](/Hold%20The%20Flood/Hospital%20Story%20Directions) remain revisable. Completed review does not select them for the owner or establish fun, balance or duration. |
||||||
|
14 | |||||||
|
15 | ## Completed: the moving scan |
||||||
|
16 | |||||||
|
17 | The [Moving Scan Expedition](/Hold%20The%20Flood/Moving%20Scan%20Expedition) now places the lamp in Cable Junction. Three source areas supply the rising fight; ordinary growth precedes the electrical climax. Observations from three positions reveal a receiver across a void, and the player unfolds and walks a bridge to it. Living return preserves the useful shortcut. A changed alignment makes the old samples historical and exposes a visible rewind for a new scan. |
||||||
|
18 | |||||||
|
19 | The price is a fourteenth proposed major mechanism and substantial rail, bay, bridge and receiver geometry. The room, encounter, combat and information references now agree; physical fit and the intended pleasure remain untested. |
||||||
| 20 | ||||||||
|
21 | ## Ready for a choice: the short rescue |
||||||
|
22 | |||||||
|
23 | [Rescue Under Pressure](/Hold%20The%20Flood/Rescue%20Under%20Pressure) is now a reviewed comparison: the astronaut’s movement and build earn a short crossing for Yeva, followed by a specific homecoming. It compares a protected retreat with completing the crossing after the astronaut dies. The owner can judge the stakes, preparation burden and effect on the shifting-station premise. Neither survivor mortality nor the first survivor is selected by this comparison. |
||||||
|
24 | |||||||
|
25 | The single critique and response are complete. The proposal now makes physical clearance, living blockage and both death-protection windows explicit. The owner is considering whether the survivor should finish or take shelter; shared rescue rules remain unchanged. |
||||||
|
26 | |||||||
|
27 | ## Ready to compare: the final connection |
||||||
|
28 | |||||||
|
29 | [Completing The Station](/Hold%20The%20Flood/Completing%20The%20Station) now offers two reviewed consequences. The last join completes route certainty earned gradually, with a further visit to the newly secured core. The alternative adds an optional departure carrying the station and docked ship, with its added story and production work explicit. Review and response finished at 14:36; neither ending nor final effect is selected. |
||||||
|
30 | |||||||
|
31 | ## Ready to compare: campaign scope |
||||||
|
32 | |||||||
|
33 | [Campaign Scope Choices](/Hold%20The%20Flood/Campaign%20Scope%20Choices) completed review and response at 14:56. It compares 40 rooms with a denser 36-room alternative through named discoveries, build moments and recovery spaces. Five supporting references now agree on fourteen proposed mechanisms, while the historical cost allowance keeps its original thirteen-mechanism basis and leaves the added work uncosted. Neither scope nor a revised hour estimate is selected. Systems has finished this outcome. |
||||||
|
34 | |||||||
|
35 | ## Ready to read: the language journal |
||||||
|
36 | |||||||
|
37 | The existing [Language And Journal](/Hold%20The%20Flood/Language%20And%20Journal) page has been rewritten around what the player does: capture a clue during an expedition, pause to compare records, make a prediction and try it. The revision preserves the current observation, testimony and historical-route rules while making the pleasure and cost of discovery easier to understand. The rewrite completed its independent critique and reasoned response at 15:06. No material correction was needed; its longer visitor and scan examples retain the reasoning behind those discoveries. |
||||||
| 38 | ||||||||
|
39 | ## Ready to read: the whole campaign |
||||||
|
40 | |||||||
|
41 | [Whole Game Outline](/Hold%20The%20Flood/Whole%20Game%20Outline) completed review and response at 15:26. It follows the player’s journey from forced docking through deeper investigation and optional secrets. The page makes the horde scale, growing builds, useful discoveries and relationships concrete, with carried equipment and open choices preserved. The home-loop page’s old living-return clearance wording has also been corrected to fresh hordes after either return. |
||||||
| 42 | ||||||||
|
43 | ## Ready to read: five people |
||||||
|
44 | |||||||
|
45 | The [Cast And Short Rescue Map](/Hold%20The%20Flood/Cast%20And%20Short%20Rescue%20Map) completed review and response at 15:44. Meet the five people through their wishes and disagreements, then follow each person’s rescue, home contribution and later change of belief. All fifteen scenes remain. The rescue references now preserve a person’s current shelter if the astronaut dies while preparing a retry. The separate owner choice about death during a crossing remains unanswered. |
||||||
| 46 | ||||||||
|
47 | ## Ready to read: equipment and combinations |
||||||
|
48 | |||||||
|
49 | The [Equipment Catalogue](/Hold%20The%20Flood/Equipment%20Catalogue) completed review and response at 16:05. It starts with a working build, then shows each part's visible behavior, useful combinations and costs. The shared references now make clear that a failed attempt preserves the rig's current readiness, and that a part installed aboard is already home while remaining outside the carried inventory. |
||||||
| 50 | ||||||||
|
51 | ## Ready to read: the Receiver Vault expedition |
||||||
|
52 | |||||||
|
53 | The [Receiver Vault Expedition](/Hold%20The%20Flood/Receiver%20Vault%20Expedition) completed review and response at **16:30**. It proposes a transformation earned by opening a firing angle during the horde, a banked-disc climax and an old hospital record acquiring a new meaning at the iris. A proposed shorter approach can deliver the first major transformation here; the established longer route retains its earlier reward. Ordinary equipment and partial progress remain options. Timing, useful banks, breathing margin and repeat-visit upgrade variety remain explicit design risks. Combat and encounter references now link the proposal and describe actual burst limits. |
||||||
|
54 | |||||||
|
55 | ## Ready to read: the enemy guide |
||||||
|
56 | |||||||
|
57 | The [Combat And Enemy Roster](/Hold%20The%20Flood/Combat%20And%20Enemy%20Roster) completed review, response and integration at **16:46**. It opens with a mixed horde, then introduces six ordinary creatures and three specials through visible warnings, pressure and useful responses. Existing placements and both setpieces remain. The rescue example now includes safe bypass and bodies still present after a door seals; the carrying example allows both finds when there is room. The two proposed roster cuts retain their different reasons. |
||||||
| 58 | ||||||||
| 59 | ## Working now: two trips, two different builds |
|||||||
| 60 | ||||||||
| 61 | Design support is developing two expeditions with the same physical equipment but different earned upgrade choices, including a useful hybrid. The first Echoing Arc versus Rebound Disc choice already exists; this proposal works through repeated offers, how earlier selections change later possibilities, and what each declined option would have bought. It will compare that freedom with the clearer teaching and lower production cost of a fixed ladder. |
|||||||
| 62 | ||||||||
| 63 | The author is working and an independent reviewer is preparing criteria. The draft target is **18:30** today and the reviewed proposal target is **19:45**, with plausible ranges on [Progress](/Hold%20The%20Flood/Progress). This develops a shared choice problem while keeping all three proposed build families available for owner reaction. |
|||||||
|
64 | |||||||
|
65 | One focused critique and one response belong to each bounded outcome. The outside-edit preservation audit is complete and its factual follow-ups are published; broader readability and design readiness remain open. States and estimates are on [Progress](/Hold%20The%20Flood/Progress). |
||||||
|
66 | |||||||
|
67 | ## What makes a proposal useful |
||||||
|
68 | |||||||
|
69 | The reader can picture what the player wants, sees and does. Pressure develops through meaningful horde combat. A growth choice changes the next movement decision; a build breakthrough creates a visible payoff; quiet lets a discovery change an understanding or future action. |
||||||
|
70 | |||||||
|
71 | Builds differ in behavior, attention and cost. Their strongest results should feel constructed and discovered. Practical limits should support interesting choices without automatically suppressing powerful combinations. Each substantial scene identifies a plausible way its intended pleasure could fail. |
||||||
|
72 | |||||||
|
73 | Readable prose leads with an example and explains necessary terms where they arise. Detailed references support the explanation. Discussion history and execution records stay outside game descriptions. Written consistency helps us design; later evidence is still needed to establish the experience. |
||||||
|
74 | |||||||
|
75 | ## Remaining design work |
||||||
|
76 | |||||||
|
77 | - Extend renewal and regular growth across worthwhile expeditions with different goals and crowd patterns. |
||||||
| 78 | - Reconcile selected build directions with their detailed mechanics while retaining expressive combinations. |
|||||||
| 79 | - Develop the hospital, alien setting, people, short rescues, languages and story consequences through concrete scenes. |
|||||||
| 80 | - Decide what completing the station connection changes and cost a content model that can support the intended journey. |
|||||||
| 81 | - Continue the readability pass through supporting articles, preserving useful outside edits and resolving actual contradictions. |
|||||||
|
82 | |||||||
|
83 | Use [Open Decisions](/Hold%20The%20Flood/Open%20Decisions) as an overlapping issue index. Its recommendations remain proposals; the team handles routine consistency and brings consequential creative alternatives to the owner. Development, simulations, playtests and game assets await separate authorization. |
||||||
