1.0 Armageddon
Armageddon 1.0
The official August 2026 launch boundary for modes, maps, progression, platforms, and the manual pages affected by the release.
Release index
No More Room in Hell 2 Updates: updates that change the manual
Use the release index to connect a dated official game boundary with the maps, modes, progression systems, platforms, and manual pages it affects.
All updates
Open update
Read the No More Room in Hell 2 update boundary
The current index contains one published release record, Armageddon 1.0. Its detail page identifies August 11, 2026 as the launch date and PC, PlayStation 5, and Xbox Series X|S as the recorded launch platforms. It also establishes the manual inventory of six Objective maps, three Survival maps, Solo, Training Grounds, achievements, Weekly Assignments, and Rescue Beacon progression. Those statements come from the dated official release feed.
Open the release record for the affected routes
The Armageddon article links to the mode comparison, permadeath and Rescue Beacon explanation, Credits and Weekly Assignments guide, platform and edition guide, Raven Rock map, Build Planner, and achievement hub. These relations identify where the manual applies the release boundary. They do not imply that every page changed in the same way or that an unlisted mechanic was altered by the release.
Separate release facts from later hotfix state
A launch record is stable evidence for what the announcement said on its date, but live faults can move after launch. The article notes that the official feed continued through hotfix 1.0.3.1 on August 17 and directs crash, server, controller, console, and cloud-play questions to the newest official post. The index therefore does not freeze a launch-window issue into a permanent troubleshooting claim.
Use the release index without inventing patch notes
Each update row is built from stored frontmatter: version, title, description, update date, status, sources, and affected routes. The body supplies the visible release summary. This hub does not calculate a diff from the game files or infer balance changes from a version number. If the official feed does not state a damage adjustment, drop change, platform fix, or server result, the index does not add one.
Check which evidence can become outdated
Launch date and the article's recorded inventory belong to the 1.0 boundary. Current matchmaking, online availability, store text, performance, and controller behavior are more volatile. For those questions, compare the article's August modification date with the newest official release or platform notice. A newer source may update the present state without making the historical launch record wrong.
Trace a change into the manual
Begin with the update detail, identify the affected route that matches the question, and then inspect that page's own data and date. A map route exposes its task record, a guide explains a bounded decision, the achievement hub tracks the 35 stored records, and the planner resolves one of seven local presets. This keeps the release summary short while preserving checkable detail at the correct destination.
Understand what one indexed update does not prove
One published update page does not prove that the site has captured every announcement after August 20, 2026. It proves only that the current content loader found one renderable English update record in this build. A missing later article is an inventory gap, not evidence that no later patch exists. The official feed remains the authority for checking newer release posts.
Use version labels as references, not freshness guarantees
The 1.0 Armageddon label appears across maps and structured records because it is their maintained game-version boundary. That label does not update itself when a hotfix ships. Readers should pair it with the visible update date and source. Editors should add or revise a record only when a named source supports the new statement, keeping historical and current claims distinguishable.
Report a correction with a route and source
A useful correction identifies the update route, the exact claim or affected manual page, the relevant game version, and a dated source that contradicts or extends the current record. That evidence lets the bounded claim change without rewriting unrelated pages. General recollection, an uncited screenshot, or an inferred patch effect is not enough to replace the release boundary shown here.