Baldur’s Gate 3 – Patch 6 disaster!

I have not played Baldur’s Gate 3 in a while now, so I have not experienced patch 6 myself. But going by the news, this patch seems to have totally broken the game, and this is not to exaggerate the problems. Some of these issues are actually game-stopping, or will just cause your game to crash outright.

Someone has made a 10-page Google document of all the issues, which can be found here. Here is a small list that caught my eye of some of the complications (text copied from the Google document).

  • Players are unable to switch to another companion for “lockpicking” as the “main character” will always be the one to appear on the lockpicking screen.
  • Destroying the steel watch foundry in any way causes Duke Ravengard to aggro onto you when you get back to camp, which in turn forces Wyll to leave your party (triggered by using “knock ” on the boss door or pick locking it).
    This also makes all civilians aggro as they are convinced that you are “trespassing”, making the whole game a huge red aggro zone (including your own camp). Not even reloading to an old save seems to fix this issue.
  • In Act 2, after agreeing to meet Halsin at the Portal, he gets stuck on a door on the way there, not being able to move to the portal. Sometimes after entering the portal he will fail to come back out, even after the required turns are completed.
  • Selling certain items to Shops will crash the game. An item that currently reproduces this bug with a 100% chance is: “Scroll of Protection from Energy”.
  • After some time, the game crashes on the next conversation. The time varies, which conversation does not seem to matter.
  • Since the 6.0 update, in multiple instances, the game simply soft locks when certain NPCs are to take their turns. In 5.0 these NPCs would skip their turns in order to prevent a full game soft lock. This seems not to be the case in 6.0 anymore.

And so on… This is only a tiny list of all the things the patch screwed up. What the hell happened here? Did the patch even get one hour of playtesting, or did Larian just hope for the best here? Also, what kind of spaghetti code does Baldur’s Gate 3 have, where so much random stuff breaks from a simple patch? If we go full conspiracy mode – maybe a developer or publisher outside of Larian got someone on the inside to purposefully mess up the code, as it is known these guys don’t like Larian much. Industrial sabotage baby! A bit of a stretch, but you never know. 

Hopefully, Larian will fix these problems, which they surely will do. However, I would recommend they at least give the patches a few hours of playtesting before releasing them to the public.

/Thomas

Leave a comment