No More Room in Hell 2 Updates Hub

No More Room in Hell 2 left Early Access with the Armageddon Update on August 11, 2026. That date marks full 1.0 on Steam and Epic, console arrivals on PlayStation 5 and Xbox Series, Survival mode’s proper launch window, Raven Rock, Solo Mode, Rescue Beacon, weekly Merits, and a broader cross-play audience. August 13 brought Launch Week Support. Mid-August brought hotfix 1.0.3.1 (console 1.005). On August 25, Hotfix 2 shipped as Hotfix 1.0.4.0 (Steam build 24830003; PlayStation 5 1.006) with weapon spread rebalance, sensitivity ceiling 6, Survival final respawns, and scoreboard mute on controller. August 27 opened a live 2X Responder XP Weekend through August 31 at 12:00 EDT. This Updates Hub is where you track what changed, what still matters, and which wiki pages to revisit after the next patch.

Featured update pages

• Armageddon Update — 1.0 launch features: Survival, Raven Rock, Solo Mode, Rescue Beacon, difficulty rename, wipe/Merits, cross-play, and consoles.
• 2X XP Weekend — doubled Responder XP through August 31, 2026 at 12:00 EDT across all modes and difficulties.
• Launch Week Support — Oceanic servers, loadout corrections, Deck/Machine status, and the original Hotfix #2 plan.
• Hotfix 1.0.3.1 — first post-launch stability train: crash fixes, keybind reset, Hong Kong region.
• Hotfix 1.0.4.0 — live balance and QoL: spread rebalance, Survival Wave-3/extract respawns, Guiding Light, Broadway tracks, Beacon match-exit fix.
• Hotfix 2 Roadmap — how the August 24 plan landed as 1.0.4.0 and what remains under investigation.
• Weekly Assignments — Merits goals and Tuesday board habits.
• September Update — preview: Lewiston permutations, new Pottsville scenario, muzzle/laser attachments, controller deadzones (not live yet).
• Patch Notes — how to follow official notes after each client update.

The Updates dropdown keeps the first pages; open this hub for the full list.

Why update literacy matters here

This is a permadeath co-op game. A quiet change to difficulty, ammo finds, skill behavior, gene-therapy timing, or map scripting can invalidate last week’s “safe” route. Even a “technical only” hotfix can wipe your keybinds or change which server region you land on. Squads that never read patch notes keep donating Responders to outdated assumptions. Treat updates as part of loadout planning, not as optional news.

When friends ask “what is new?”, send Hotfix 1.0.4.0 first if they updated after August 25, 2X XP Weekend if they are grinding this week, then Armageddon for launch baseline and September Update for what is still coming.

How to use this hub after launch week

1. Skim official Steam news or console patch text when a client update appears.
2. Note anything that touches skills, maps, Survival waves, Merits, anti-cheat, keybinds, sensitivity, or server regions.
3. Re-test your main Responder in a safer lobby—or Solo Mode—before Hard queues.
4. Check Known Issues before teaching day-one workarounds that 1.0.4.0 already fixed.

If a patch lands while you are mid-session, finish or abort cleanly. Installing mid-extract is how war stories and support tickets are born.

Cross-links for context

After Armageddon, continue into Survival Mode, Raven Rock Walkthrough, Maps & Objectives, and the Game Review. After 1.0.4.0, re-open Controls, Weapons Tier List, and Inventory & Weight.

Share this hub in party chat whenever someone asks “did they change anything?” A short update culture—read, call out risks, then queue—keeps Responders alive longer than any single weapon drop.