Armageddon 1.0

Launch date and platform boundary

The official launch announcement places Armageddon 1.0 on August 11, 2026 and describes No More Room in Hell 2 moving out of Early Access. The recorded launch platform set is PC, PlayStation 5, and Xbox Series X|S. Those are release facts attached to the announcement date, not a prediction of later ports, editions, store policies, or service availability.

Use the platforms and editions guide for the current source-bounded store fields and the crossplay guide for multiplayer preparation. This update does not copy one platform's subscription, purchase, or device wording to another platform family, and it does not treat an old launch listing as proof of a live store condition.

Nine-map launch inventory

The 1.0 release inventory contains six Objective maps: Power Plant, Lewiston, Pottsville, Broadway, Beaulieu Hospital, and Raven Rock. It also contains three Survival maps: Flooded, Lighthouse, and Night of the Living Dead. Raven Rock is the sixth Objective map named by the release boundary; the three Survival names belong to their separate mode inventory.

The maps index links to the maintained records for all nine locations. Those pages carry their own dated setting, task-chain, checklist, and source boundaries. A map name in this release article does not authorize an invented room order, item location, spawn rate, shortcut, reward value, or guarantee that a later patch leaves every objective unchanged.

Objective and Survival release roles

Objective and Survival are distinct launch loops in the current manual. Objective records expose ordered CRC task chains that lead toward final extraction. Survival records use preparation and speaker-site defense states before their extraction branch. The map count confirms the inventory; it does not rank the modes, publish completion times, or promise a reward comparison.

Open the mode comparison when choosing between Objective, Survival, and independent practice. Open the extraction guide for the bounded final-versus-early extraction decision. Those pages explain the current stored behavior without turning the Armageddon announcement into a universal tactic for every map.

Solo, Training Grounds, and progression additions

Armageddon's launch inventory includes Solo and Training Grounds. Solo supplies the independent mode boundary used by the manual, while Training Grounds provides the guided tutorial context for combat, objective, and inventory practice. Their presence in the update does not establish universal offline behavior, ideal control values, live server status, or a guarantee that practice reproduces a squad mission.

The same release set includes platform achievements, Weekly Assignments, and Rescue Beacon progression. Use the Credits, Merits, and Weekly Assignments guide for the maintained economy boundary, the permadeath and Rescue Beacon guide for protection limits, and the achievement index for local-only checklist tracking.

Affected manual pages and local tools

The affected-page list beside this article connects the release boundary to modes, progression, platforms, Raven Rock, Builds, and achievements. A relation means the release changes the context required to read that manual page; it is not a claim that every linked page received the same code or balance change. Each destination remains responsible for its own date and source limits.

The Build planner and achievement controls store their current state locally in the browser. Saving an item there does not write to a game account or confirm in-game completion. The update page links those tools because Armageddon supplies their release context, not because this site can observe the player's live inventory, assignment state, Responder, or platform profile.

Post-launch hotfix boundary

The official feed continued after launch and records hotfix 1.0.3.1 on August 17. That later entry is relevant to named crash, controller, customization, and server-stability work. It does not transform the August 11 inventory into a live status report, close every issue, or identify the cause of a future technical symptom.

For crashes, connection failures, matchmaking, controller behavior, console presentation, PC performance, or cloud play, open the newest official post before using a launch-window statement. This article does not infer an unlisted fix from a higher version number or from the absence of an issue in one note. Current status remains unknown when the available official material does not state it.

Verify changes newer than this article

Compare the installed game version, the update's publication date, and the newest relevant official entry. If a newer note changes a map, mode, platform field, progression rule, or technical item, prefer that explicit dated statement and then revise the affected manual record. Keep the historical Armageddon launch inventory separate from current service or patch behavior.

The single official release feed linked here is the source boundary for this article. It does not provide unsupported performance values, player counts, popularity, issue priority, guaranteed outcomes, or every future change. Readers should use the named links for narrower decisions and treat any behavior not present in the captured official record as unknown until newer evidence supports it.