Summary

Baldur’s Gate 3’s last major update, Patch 8,dropped last week, adding a bunch of new content and features. This includesnew subclassesand cross-play multiplayer.

However, it also appears to have added a new detail toMinthara’s story - and it might not have been intentional. A few fans have noticed that previously cut dialogue has appeared in Baldur’s Gate 3 following Patch 8, referencing Minthara having a child.

mixcollage-08-dec-2024-02-20-pm-5221.jpg

Baldur’s Gate 3 Cut Content Added In Patch 8

Quite a few fans have referenced the dialogue on social media, and YouTube user Finrod Felagund was able to demonstrate how to find it. As you can see in the video, Minthara has to be killed, and the player has to use Speak with Dead on her. Then, you can ask her some questions, and one of the answers references her finding a home for herself and her child.

Now, anyone who has played the game with Minthara in their party will know that she doesn’t mention having a child. This line was previously in the game files, but was inaccessible, so it is seemingly in reference to a cut storyline rather than referring to her having a child before the events of the game.

There areunused linesfor other companions that reference Minthara discovering that she is pregnant throughout the course of the game, but it doesn’t seem that these trigger in Patch 8. Therefore, it seems likely that the patch accidentally re-enabled Minthara’s dialogue,something which happened with her in a previous update.

Fans are reacting negatively to the line being reincluded in the game, since the cut story element has always been controversial. Presumably, Minthara would have become pregnant while being controlled by the Absolute, and then would have decided to keep the child in spite of this.Some fans have been eager for Larian to restore this storyline, whereas others feel that it would be in poor taste, and potentially out of character for Minthara.

In any case, Baldur’s Gate 3 is still receiving smaller updates fromLarian. If adding this line back in was a mistake, then we can expect it to be removed in a hotfix.