No More Room in Hell 2 Hotfix 1.0.3.1 (Update 1.005)
Post-Armageddon stability patch for PC and consoles — what changed and what to re-check.
Torn Banner shipped hotfix 1.0.3.1 in mid-August 2026 as the first major post-Armageddon stability pass. On consoles it appears as update 1.005 (August 18). This is not a balance rewrite or a new map drop — it is a technical rescue for crashes, customization bugs, legacy Early Access save leftovers, and Asia matchmaking latency. If your squad still treats “1.0 launch notes” as the whole story, read this page before you blame a teammate’s controller layout or a Hong Kong ping spike.
Use this alongside the Armageddon Update baseline and the ongoing habit on Patch Notes.
What shipped in 1.0.3.1 / 1.005
Crash and memory fixes
- Fixed crashes tied to memory pressure when Responders were heavily customized, especially in full squads, with DLC outfits, patterns, and extra cosmetic data loaded.
- Fixed a crash that could fire when you left character customization menus too quickly.
- Broader server stability improvements to reduce disconnect noise after the launch surge.
If your lobby was hard-locking in the wardrobe or during ready-up with fashion-heavy Responders, this hotfix is the reason those nights should calm down.
Customization and Early Access leftover data
- Fixed cases where Responder customization items showed the wrong patterns.
- Fixed an issue where players who came from Early Access could keep hidden save data that forced an incorrect controller scheme.
- That save cleanup resets keybinds with the hotfix. Re-open Controls and re-bind VoIP, compass (C on PC), shove, and Unstuck before you queue Hard with a main.
Do not assume your muscle memory survived. The studio called out the keybind reset explicitly and apologized for the inconvenience — treat it as mandatory homework, not optional flavor text.
Hong Kong server region
Torn Banner added a Hong Kong server region for players who were seeing higher ping than expected after the multi-platform launch. Asian squads should re-test matchmaking and note whether party latency improved before blaming cross-play itself. Cross-play setup details still live on Cross-Play and Play with Friends.
What this hotfix does not change
Expect no new Scenario map, no Survival arena swap, and no advertised melee/skill retune in 1.0.3.1. Keep using:
- Survival Mode and Survival Maps for wave rules
- Raven Rock Walkthrough for the bunker finale
- How to Unlock Skills and Best Builds for loadout theory
- Weekly Assignments for Merits resets (still Tuesday)
If a later patch touches balance, the Patch Notes routine still applies — this page stays the dated log for the first console/PC stability train.
Post-hotfix checklist (10 minutes)
- Install 1.0.3.1 (PC) or 1.005 (PS5 / Xbox Series).
- Open settings and rebuild keybinds after the forced reset.
- Inspect your main Responder’s cosmetics; confirm patterns look correct.
- If you play from East / Southeast Asia, verify you can land on the Hong Kong region and compare ping.
- Run one low-stakes lobby — Solo Mode or Beginner Scenario — before Nightmare fashion shows.
- Tell your squad in one line: “keybinds reset, customization crash fixed, HK servers live.”
Why Responders should care
Permadeath makes stability patches personal. A crash in a customized squad used to delete evenings; a wrong controller scheme used to delete Responders. Hotfix 1.0.3.1 is how Torn Banner answered the first week of 1.0 support tickets. Pair it with extract discipline on How to Extract and infection control on How to Treat Infection so the technical win is not wasted on a preventable wipe.
When the next numbered hotfix lands, skim official Steam / console patch text first, then return here only as historical context. Living process lives on Patch Notes; living launch fantasy lives on Armageddon; this page is the dated bridge between them.
Frequently Asked Questions
Quick answers for Responders preparing for the next deployment.
What is No More Room in Hell 2 hotfix 1.0.3.1?
A mid-August 2026 stability hotfix (console update 1.005) focused on customization crashes, wrong cosmetic patterns, Early Access save/controller fixes, a keybind reset, server stability, and a new Hong Kong region.
Why did my keybinds reset after the patch?
The hotfix clears hidden Early Access save data that could force the wrong controller scheme. Re-bind critical actions before high-risk queues.
Does 1.0.3.1 change Survival or Raven Rock rules?
No meaningful gameplay rewrite was advertised. Treat it as a technical patch and keep using the Survival and Raven Rock guides for mode rules.
Who benefits from the Hong Kong server region?
Players who saw higher-than-expected ping after the multi-platform launch, especially in Asia. Re-test matchmaking after updating.
Where should I go after reading this hotfix page?
Re-check Controls, then follow Patch Notes for future updates and Armageddon for the 1.0 feature baseline.