Blame
|
1 | # Hold The Horde — Design Coverage |
||||||
| 2 | ||||||||
|
3 | The existing wiki contains first-pass material across fifteen areas. The owner's review showed that this breadth did not produce an adequate game direction or a readable wiki. The table below identifies what exists and what the correction needs to address; it is a guide to work, not a completion score. |
||||||
|
4 | |||||||
|
5 | ## Immediate correction |
||||||
|
6 | |||||||
|
7 | | Area | Existing material | What now matters | |
||||||
|
8 | |---|---|---| |
||||||
|
9 | | Expeditions and regions | [Whole Game Outline](/Hold%20The%20Flood/Whole%20Game%20Outline), regional and room inventories | Rebuild the ordinary rhythm around pressure, powerful play, discovery, climax and relief | |
||||||
| 10 | | Combat and contested objectives | [Combat Rules](/Hold%20The%20Flood/Combat%20Rules), combat roster | Make crowded combat a substantial part of travel and objectives; explain the player's moment-to-moment decisions | |
|||||||
| 11 | | Enemies, encounters and traps | [Encounter inventory](/Hold%20The%20Flood/Encounter%20And%20Mechanism%20Placement%20Inventory) | Replace the small tactical examples with convincing horde behavior, escalation and breathing room | |
|||||||
| 12 | | Connected equipment | [Build Rules](/Hold%20The%20Flood/Build%20Rules) | Design from spectacular, earned outcomes; revisit restrictions that prevent them | |
|||||||
| 13 | | Equipment and acquisition | [Equipment Catalogue](/Hold%20The%20Flood/Equipment%20Catalogue), acquisition proposal | Show exciting power growth during expeditions and across returns, with understandable construction choices | |
|||||||
| 14 | | Languages and discovery | [Two Language Discovery Map](/Hold%20The%20Flood/Two%20Language%20Discovery%20Map) | Give deductions substantial payoffs and explain how learning opens new possibilities | |
|||||||
| 15 | | Information and accessibility | [Player Information And Options](/Hold%20The%20Flood/Player%20Information%20And%20Options) | Preserve clear survival information and journal pause; make the proposed experience and wiki legible | |
|||||||
|
16 | |||||||
|
17 | The revised [game overview](/Hold%20The%20Flood/The%20Game) and [horde/build proposal](/Hold%20The%20Flood/Hordes%20and%20Builds) have completed a combined critique, bounded author responses and PM verification. They are ready for owner reaction; the earlier reference pages listed here still need reconciliation with the selected direction. |
||||||
|
18 | |||||||
|
19 | ## Material to revisit after the direction is selected |
||||||
|
20 | |||||||
|
21 | | Area | Existing material | Required follow-through | |
||||||
|
22 | |---|---|---| |
||||||
|
23 | | Death, shifts and station connections | [Death And Persistence](/Hold%20The%20Flood/Death%20And%20Persistence), [Connecting The Station](/Hold%20The%20Flood/Connecting%20The%20Station) | Preserve carried-property return and selected permanence; explain stakes and late mastery within the revised rhythm | |
||||||
| 24 | | Oxygen and carrying | [Survival And Loadout](/Hold%20The%20Flood/Survival%20And%20Loadout) | Make preparation and exposure meaningful without turning routine play into accounting | |
|||||||
| 25 | | Story and endings | [Story And Ending Map](/Hold%20The%20Flood/Story%20And%20Ending%20Map) | Give major revelations and the climax understandable emotional weight; keep the owner's early story draft revisable | |
|||||||
| 26 | | Authored people and short rescue | [Cast And Short Rescue Map](/Hold%20The%20Flood/Cast%20And%20Short%20Rescue%20Map) | Make people memorable and rescues consequential while respecting the rejection of long escorts | |
|||||||
| 27 | | Home and colony | [Home And Colony Loop](/Hold%20The%20Flood/Home%20And%20Colony%20Loop) | Show relief, attachment and reasons to depart again; reduce repetitive preparation | |
|||||||
| 28 | | Saves and content state | [Save And Content State](/Hold%20The%20Flood/Save%20And%20Content%20State) | Reconcile concrete rules after the experience is selected; avoid allowing bookkeeping to dictate implausible events | |
|||||||
| 29 | | Content scope and feasibility | [Production Scope](/Hold%20The%20Flood/Production%20Scope) | Re-estimate the chosen design rather than treating the earlier finite inventory as fixed scope | |
|||||||
| 30 | | Development and validation | [Development And Validation Handoff](/Hold%20The%20Flood/Development%20And%20Validation%20Handoff) | Refresh the proposed handoff after correction; implementation and human testing remain separate phases | |
|||||||
| 31 | ||||||||
| 32 | The detailed opening mechanism and paired-transfer drafts remain parked and unaccepted. Existing numerical limits, enemy populations, cast allocations and content counts are team proposals unless explicitly selected in the Owner Brief. The 30/90/100–200-hour ambitions have not been established by the inventory. |
|||||||
| 33 | ||||||||
| 34 | See [Progress](/Hold%20The%20Flood/Progress) for dates and statuses, and [Design Plan](/Hold%20The%20Flood/Design%20Plan) for the correction's acceptance criteria. Historical coverage and review records remain in revision history. |
|||||||
