HOTFIX DETAIL / VERSION 1.0.3.1
Hotfix 1.0.3.1
A complete in-site breakdown of the August 17, 2026 hotfix: crashes, controller schemes, keybinds, customization patterns, and server stability.

What this hotfix fixed
Hotfix 1.0.3.1 was the official post-launch hotfix for No More Room in Hell 2, published on August 17, 2026. Its scope covers customization-related crashes, an incorrect controller scheme caused by leftover Early Access save data, incorrect customization patterns, and server-stability improvements. The sections below keep the full confirmed change scope on this site.
Memory crashes caused by heavy customization
The official notes fixed a memory-related crash that could occur when a Responder had a large amount of customization data. The issue appeared most often in squads, especially when DLC outfits, patterns, and other added data were involved.
This was more specific than a generic “crash fix”: the risk was associated with the amount and type of customization data being handled during play. Hotfix 1.0.3.1 lists this crash class as fixed rather than leaving the cause vague.
Crash when leaving the customization menu too quickly
The hotfix also fixed a crash that could occur when players left the character-customization menu too quickly while handling customization. It is a separate trigger from the memory issue above, even though both are connected to the same menu and workflow.
The delivered change therefore covers both heavy customization data and the fast-exit path from the customization menu. Both are confirmed parts of the 1.0.3.1 notes.
Early Access save data and controller schemes
Some players who participated in Early Access could have hidden save data that caused the game to use the wrong controller scheme. The hotfix fixes that incorrect scheme selection instead of treating it as a normal input-setting choice.
The change comes with a keybind reset. After the update, players should review and set their keyboard, mouse, or controller bindings again if they no longer match their previous layout; this reset is a player-facing consequence of the official fix.
Incorrect patterns on customization items
The official notes also fix an issue where some Responder customization items displayed the wrong patterns. The selected customization and the pattern shown in-game could disagree, producing an incorrect visual result.
This entry is a fix for customization-item pattern display. It does not announce new customization content, and it should not be expanded into a claim that every appearance issue has been solved.
Server-stability improvements
Hotfix 1.0.3.1 includes improvements to server stability. The official notes do not provide a percentage increase or a latency guarantee, so this page records the change without inventing a numerical performance claim.
This is a delivered general stability adjustment. Cross-platform matchmaking, regional servers, and other launch-week reports should be read alongside their separate official status rather than being folded into this one line.
Do not confuse planned work with this delivered hotfix
The launch-week post also listed later work such as the Normal-mode respawn message, additional chances to respawn before extraction, higher sensitivity limits, more memory fixes for lower-end machines and Xbox Series S, missing PS5 textures, and missing Beginner supply drops in Solo Mode. Those items were described as Hotfix #2 plans or issues under investigation, not as the completed 1.0.3.1 list.
The same post listed GeForce Now crashes after the terms-of-service screen, controller focus loss in some UI areas, crossplay matchmaking adjustments, an Unload keybind that would not rebind correctly, and random controller vibration as investigation items. Keeping those statuses separate prevents a planned or unresolved item from being presented as fixed.
Official sources
The confirmed 1.0.3.1 changes are written above; the external links are kept only for source tracing: official Hotfix 1.0.3.1 notes and the official launch-week issues post.