Yesterday, Larian Studios released Baldur’s Gate 3 Hotfix 4, which the studio had to roll back due to save issues plaguing gamers. Today, the studio has released the Baldur’s Gate 3 update for August 17, which redeploys Hotfix 4! Read on for the patch notes, as well as Larian’s statement on what happend.

Baldur’s Gate 3 Update for August 17 Patch Notes | BG3 Hotfix 4 Patch Notes:

CRASHES AND BLOCKERS

• Fixed players getting stuck mid-Long-Rest due to companions not waking up.
• Fixed being able to Long Rest in the Astral Prism, potentially causing the portal to disappear.
• Fixed getting pulled from her location in the Temple of Bhaal if the door was opened before killing Gortash in Wyrm’s Crossing.
• Fixed a script issue preventing some players from loading savegames.

MULTIPLAYER

• Fixed characters disappearing when disconnecting and reconnecting in split-screen.
• Added a warning for hosts in multiplayer when clients join through drop-in during Character Creation.
• Hosts must now grant approval before new players join.
• Fixed the visibility of multiplayer servers on GOG.

COMBAT

• Slightly increased Isobel’s HP so she doesn’t die as easily.
• Fixed a bug that would make Gortash join the combat taking place in Wyrm’s Rock’s Audience Hall while he was in his office upstairs.
• Fixed Cruel Sting adding infinite additional Psychic damage to attacks.

FLOW AND SCRIPTING

• Fixed the ‘Enemy of the Absolute’s crime not clearing from player characters, resulting in a soft block when speaking to the Steel Watch.
• Fixed the game thinking the Emperor had died in the Astral Prism when you healed a downed ally.
• Player resources are now correctly restored at the end of Act II.
• Having dead party members no longer prevents you from entering the Astral Prism.
• Fixed a bug preventing you from talking to Ravengard if he gets moved to the camp in a certain case.
• Hostages in the Iron Throne will no longer be stuck if you turn back and return again.
• Players with modded or cheated savegames with characters at Level 13 or above can now travel to the House of Hope.
• Killing Anders will no longer make the other paladins leave the Tollhouse.

Here’s the statement released by studio on what happened yesterday:

Players who had downloaded hotfix 4 were unable to continue from their hotfix 4 saves once we had rolled back the patch. While this is not ok, rolling back the patch in order to diagnose the problem and limit those exposed to it was the lesser of two evils. We truly appreciate your patience & understanding while we worked to understand the problem.

All of you should now be able to continue your adventures, but essentially, here’s what happened:

Hotfix 4 went through a rigorous QA pipeline and was confirmed as a candidate for release yesterday. However, we triggered a rebuild of the version relatively last minute to change the version number. The version that was cooked was unfortunately plagued by compiler corruption, which was causing certain exceptions that normally wouldn’t cause crashes to – you guessed it – cause crashes.

Since compiler issues like that are extremely rare, we weren’t prepared for it. We should’ve been. We messed up.

It didn’t help that it happened at the worst possible time of day but luckily we have studios in multiple countries. Overnight (for Europe), our teams in Canada and then Malaysia worked to diagnose what went wrong, so that work could begin on redeploying a fixed version of the hotfix

To avoid this from happening in the future, we’ll make sure that any change made to future version candidates – no matter how small, or innocuous – will always go through our full & comprehensive QA pipeline, which include a global in-house QA team, automated testing, unit tests, and save-game compatibility testing.

That is fantastic communication, no? Hopefully, nothing like this surfaces again, and especially not for Patch 1.

Source: Steam