Title says it all. I've been trying to fast travel from the mountain pass to the myconoid colony and after leaving the camp after the long rest I get a game over.

So basicly:
I hate Gale so I killed him. Left him on the bridge in the goblin camp and collapsed it. I, not having been aware of how Gale works, keep getting game overs after long rests wich I cancelled out by loading the same save. I figure out that Gale is the issue, ressurect him using Wither, kill and resurrect him again and then kick him out for good.

Now everything was fine again but when I wanted to fast travel between regions I get the message in the attached image.

Is there any way to fix that? I also haven't updated my game ever since I managed to install it after a grueling 40 hours download session.

I honestly fear my save file is now corrupted. I can't progress at all.

Edit: Seriously does anynone have ANY idea what the problem is and if it's even possible to fix it? I'm desperate here.

What attached image? ;)

Huh, appearently GOG forums doesn't like .png. Let's try jpeg.

Edit: dafuq? Okay so basicly it's just the party defeat game over showing up while my characters are clearly fine and at full health. I almost wonder if the game still somehow registers a copy of Gale's corpse or something like that to cause that.

This might (or might not) help:

Gale DON'T EXPLODE after dying anymore (mod)
https://www.nexusmods.com/baldursgate3/mods/1094

Something to try, anyway, if you don't find another solution.

Note: There seem to be multiple versions of BGSE available from various sources - if the version linked in the mod description doesn't work with your installation, you might try the others.

Ooof.... I guess I'll try that. The thing is, technically my game should consider Gale to be alive again so I've got no idea what the hell is going on. One would think Larian, having had years of open beta to fix the most glaring issues with the game, would've already fixed such an issue at release.

yes its a known bug and the option to kill him works if you do it at first meeting or if you give the body to a certain dead guy at your camp

i think Larian was going for smart plot but they just come across as forgetful

The mod didn't help at all. Instead I'm not able to interact with anything anymore and can't choose any long rest after installing it. My game is completly broken it seems.

just to be clear, no mod will work on a game already in play but must be installed before you start your game

also the current state of play is super busted with Larian making code changes each patch and hotfix they don't bother to tell people about its extremely hard to keep your mod current so i recommend not using them until we get something half stable

I'm fully aware of that. Installed the mod and everything but when I started the game it straight up blocked out any interaction option. I could walks around and use abilites but not use any object or talk to npcs.

This game really shouldn't have been released yet. Like at all. People always bitch about Bethesda but their games are yanky but fully playable. BG3 is just a travesty.

Do you get a game over no matter which region you choose to travel to or only if you try to travel back to part 1 regions? Can you still progress into act 2 / the Shadowlands?

If this affects every travel, I guess the only thing you can do is load a previous save file with Gale still alive and bench him forever in your camp.

You can also try posting the same thread on the steam community hub. Maybe someone over there can help.

I do get it when I try to travel back to the starting region and when trying to continue to the shadowlands. The thing is: Gale should register as being alive to the game since he is.

To repeat what I've already mentioned above:

I initially killed him but then reloaded the save when I triggered his hologram. Because I wanted to avoid spoilers I didn't actually know what Gale's deal was so I thought he'll only gonna cause problems while his corpse is in camp. So I got him on one of the platforms at the goblin camp, killed him there (wich didn't trigger the hologram this time even tho as far as the game is concerned this should've been the first time of him dying) and then collapsed it, chuggin him out of bounds. When I started to get game overs after long rests I ressurected him using Withers and then managed to kick him out via the dialogue option.

As far as the game is concerned he's alive and well but just not around anymore. I've got no idea what's going on there but I hate the result. My ongoing theory is that there's still a copy of his body registering with the game.

So you're saying Gale fucking over travel and causing entire playthroughs to be rendered unplayable is deliberate? I'm hating Larian more and more. Like people whine about Bethesda but like... I've never experienced game breaking nonsense like that with them.

And if that's about the option to blow up the Absolute using Gale, I've already stumbled over that. Don't know any details only know that it's an option.

I also don't get the Gale exploding cutscene before the game overs. It just loads and then tells me that my party was defeated.

Seems to me that you tried something rather gamey/meta and you found that the game doesn't handle that weird condition very well. Lots of games do this. Get over it.

Huh? In my almost 25 years of gaming I've never experienced a game breaking so hard because I did anything out of the ordinary in it. Especially not RPGs with heavily confined areas Like BG3. Like, the worst problem I've ever found in one was floor textures not loading letting me gaze into the abyss while walking on it and that was in that rushed trash pile Dragon Age 2, wich was hastily cobbled together in 6 months. And that one infinitely spawning and dropping soup can in Fallout 3.

Also, the issue appearently was caused by Gale being out-of-bounds and that's usually one of the earliest thing that's being taken care of during development.

Like, "what is supposed to happen if any in-game object accidentally leaves the designated gaming area?" is almost at the top of the to-do list for developers because stuff like clipping through hit boxes etc. is one of the most common bugs ever. The fact that Larian seemingly didn't even think about that baffles me.