Larian Studios Forums Baldur's Gate III Baldur's Gate III - Technical & Gameplay Problems bugs patch 7

3 new bugs
the spell Expeditious Retreat has a bug that makes it cost a spell slot under some conditions
if you take it as a charisma based spell in a multiclass and the spell slot is already used then it will burn one of your other spell slots on cast

[see image] example Druid 1, Warlock 1 where Expeditious Retreat is my Warlock spell
1 casting it as a Warlock works normally but should you use up that warlock spell slot it then burns the druid spell i.e, counts as a normal spell not a ritual and in fact should not have been castable at all

the cause of this bug is the same as other charisma based shot cuts done by Larian during dev and will need work to fix


bug 2 the clift face in the image has a clipping hole that allows characters to walk off the map... becoming stuck in terain [fast travel workaround]

bug 3 sanctuary treats damage over time as breaking its effect... even when the spell was cast after your attack turn

only a minor bug but explains some strange ai moves

Expeditious retreat isn't a ritual spell. It's also intentional that you can use other spell slots for warlock spells.

Sanctuary I believe is intentional. It makes sense to me at least that you can't claim sanctuary when still intentionally harming people. The attack that caused the damage over time was made with intent to harm. That intent is still there when the harm happens, so you've broken sanctuary. And we're talking about a situation that involves divine magic and beings who can tell your actual intentions.

Unfortunately, unlike tabletop there's no way to really argue about intent (accidentally hitting someone with splash damage for instance), or roleplay a change of heart mid-combat. So for that and mechanical reasons, it makes sense to me to just have it break on any damage.

Had another annoying bug yesterday - with a druid in Panther form I used Pounce on a bhaal cultist to get him prone, to get the bonus damage on the melee attack the following turn. The prone state following Pounce is supposed to last two turns and the icon on the enemy said as much - but when that enemy's next turn came up it immediately got up on its feet, so when it was my druid's turn again the bhaalist did not have prone status.

In general I see the AI doing similar things fairly often - snapping out of stuns, paralyze and other means of CC. Combat log saying nothing, the state just disappears between turns as if it was never there. This makes CC spells too unreliable, the AI's supernatural knack for making their saving thows should be enough, they don't need to cheat!