Objective01Power Plant
Stored setting: Pennsylvania wilderness surrounding a central Light & Electric power plant objective.
Mode
Objective
Route
Objective 1
Checklist
4 sections
Hub · 9 maps
Compare all nine recorded maps by mode, mission order, setting, and checklist size before opening the route that matches the current run.
Objective01Stored setting: Pennsylvania wilderness surrounding a central Light & Electric power plant objective.
Mode
Objective
Route
Objective 1
Checklist
4 sections
Objective02Stored setting: A rural Pennsylvania town with suburbs, randomized houses, and a downtown route.
Mode
Objective
Route
Objective 2
Checklist
4 sections
Objective03Stored setting: A Maine city route beginning in barricaded stores with randomized urban locations.
Mode
Objective
Route
Objective 3
Checklist
4 sections
Objective04Stored setting: A night-time Queens route through city streets, subway tunnels, and sewers after a failed extraction.
Mode
Objective
Route
Objective 4
Checklist
4 sections
Objective05Stored setting: A daytime Manhattan hospital with a central courtyard and wards whose locations can change between runs.
Mode
Objective
Route
Objective 5
Checklist
4 sections
Objective06Stored setting: A southern Pennsylvania military installation leading into an underground emergency operations bunker.
Mode
Objective
Route
Objective 6
Checklist
4 sections
Survival07Stored setting: A storm-flooded rural Pennsylvania industrial complex with machinery, containers, and scarce dry ground.
Mode
Survival
Route
Wave holdout
Checklist
4 sections
Survival08Stored setting: A cliffside coastal holdout spanning a lighthouse, small neighborhood, and abandoned construction.
Mode
Survival
Route
Wave holdout
Checklist
4 sections
Survival09Stored setting: A rural farmhouse holdout expanded across the main house, guest house, and barn.
Mode
Survival
Route
Wave holdout
Checklist
4 sections
The map index contains the complete local 1.0 inventory: six Objective routes and three Survival holdouts. Use the All, Objective, and Survival controls to change only the visible rows; the underlying nine records remain available. Every row names the stored mode, describes the recorded setting, shows mission order when the field exists, and reports how many checklist sections the detail page will render.
Power Plant through Raven Rock carry Objective 1 through Objective 6 in their current records. That ordering helps select the corresponding page, but it does not replace the active CRC text shown in a run. Objective detail pages therefore begin by telling the reader to read the current prompt, then follow the stored sequence through mission flow, a stalled-progress check, and final extraction.
Flooded, Lighthouse, and Night of the Living Dead use the Survival checklist shape rather than an Objective number. Their stored sections cover preparation, three successful speaker-site defenses, the recorded failure branch, and helicopter extraction. The index labels these rows as wave holdouts so a Survival run is not mistaken for the six-map Objective sequence.
Open a detail page for the exact setting and task labels attached to that map. A checkbox records only whether this browser marked a stored step complete; it cannot inspect the game, verify a random branch, or advance the active objective. Reset affects the selected map record rather than all saved manual state, which makes it useful for starting a fresh checklist without erasing unrelated favorites, Builds, or achievements.
Every map detail links back to this nine-map comparison and to the relations declared on its record. Objective maps connect to the mode comparison and final-extraction guidance. Survival maps connect to the mode comparison and early-extraction guidance. Those links explain the system around a task chain; they do not add unrecorded locations, item spawns, shortcuts, or success rates to the map data.
Map names, modes, settings, mission-order fields, and task structures are bounded to the captured structured reference reconciled with the official Armageddon release feed. Detail pages expose the record update date and source link so a reader can distinguish this maintained snapshot from a live game session. If a later patch changes an objective, the dated record needs revision before the manual should state the new behavior.