Check build and prerequisites
Applies to: Warhammer 40,000: Boltgun 2 Steam PC October 20, 2026 patch
- The objective is the Lord of Skulls boss, not a random level-complete screen.
- The failure happens after a save/load around the neck weak point or during the collapsing arm animation.
- You can confirm the October 20 update or later is installed.
Step-by-step answer
Identify the relevant softlock trigger
Ask whether the boss stopped taking a finishing hit after reloading immediately after the neck weak point, or whether your character was trapped by its arm during death.
Why this matters: The developer distinguishes these two Lord of Skulls issues in the same official patch.
Check: Your symptom matches one of the documented cases.
Install the October 20 update before repeating the encounter
Check that the patch containing both fixes is active before trying unsupported combat or save editing solutions.
Why this matters: The developer explicitly lists both softlocks as fixed in the patch notes.
Check: Your game build is no older than the recorded fix.
Use the normal encounter state after updating
Return via the game’s documented campaign load route and retry the boss normally; avoid deleting save files or reproducing a known broken reload sequence deliberately.
Why this matters: The official report is about repairing a bug, not providing a magic boss-kill command.
Check: The boss death/level-complete process can finish normally in the corrected case.
What result should you see?
The Lord of Skulls boss encounter reaches a proper kill and level progression state after the fixed conditions are applied.
If your result is different
If the game still locks on the corrected build, report build number, whether the trigger involved a weak-point save/load or arm animation, and which save path you used. Do not claim the October 20 patch guarantees every unrelated boss failure is resolved.
Important version, route and evidence differences
Two distinct failure modes
One bug made the boss impossible to kill after a specific neck weak-point save/reload timing; the other could trap the player when a falling boss arm occupied their location. Both are named separately in the patch.
Why pre-patch video tips can be misleading
If a video tells you to shoot an unseen part of the neck repeatedly on an affected build, that may not be the real problem. The official patch removes a state bug, so version verification comes before searching for a new hitbox.
Campaign load versus Level Select
The same update changed the Continue button to load campaign saves. If your run appears to resume the wrong level, a separate Guide explains the main-menu state difference.
Frequently asked questions
Was the neck weak point changed?
The developer fixed an unkillable boss state after immediate save/reload at that weak point; this is not a universal attack pattern change.
Is the falling arm issue the same bug?
No, it was a second named softlock fixed in the same update.
Do I need to delete autosaves?
No; deleting autosaves caused a different level-complete softlock, also listed as fixed.
Sources and verification limits
Primary player reports establish that a problem was encountered; developer notes document intended changes. Third-party guides describe their observed route, not a guaranteed result for every game build. We do not reproduce other sites' screenshots or claim to have played the game.
- Boltgun 2 October 20 developer patch (SteamDB exact archive) (developer) — Both Lord of Skulls softlock fixes and related menu update.
Not independently confirmed: No direct GGClue reproduction or verified repair for post-October-20 persistent softlocks.
Related GGClue answers
Identify the two different Lord of Skulls softlocks
The developer’s October 20 patch notes in the dated build archive list two separate Lord of Skulls fixes: saving and immediately loading after shooting the neck weak point could make the boss impossible to kill; a separate failure involved the arm landing on the player when the boss died. If your issue is on an older build, distinguish which event actually happened instead of assuming the boss has a second hidden vulnerable spot.
Success: after updating, a normal encounter can be finished and the next objective becomes available. This is not evidence that every already-broken boss checkpoint is restored. Do not repeatedly overwrite a sole affected save as a speculative cure; note the load timing and phase in a reproducible report if the state persists.