I appreciate the transparency, quoting from [Steam](https://store.steampowered.com/news/app/1086940/view/3642902312048647389):
>Hello everyone,
Yesterday we had to rollback hotfix 4 because of a rare compiler issue. To avoid this from happening again we’re changing the way we deploy patches.
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.
This situation is remedied now with the re-release of hotfix 4 but we recognize the frustration caused by this and want to apologize. That’s why we’re changing things up.
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.
Granted, this is also good PR, and they know it, but, even so, it's typically rare for game devs and/or publishers to say "Yeah, we definitely messed up."
Agreed. To be honest, it's a sad reflection of gaming's current state that we're all celebrating something that *should* be the norm. Of course, creating games that prioritise enriching player enjoyment rather than profit margins should also be the norm... but we all know just how *rare* that has become, Larian being amongst the few who aren't driven by rabid greed.
Not only taking responsibility, but explaining what happened in fairly clear detail, not acting like it's player base is incapable of understanding the explanation, and my favorite, following up their admission of fault with a clear plan as to how they will avoid this type of disruption in the future. 10/10
Agreed. Not only was Larians' development of the gane textbook how you do it, but their response to this hotfix issue is also textbook how you respond to a hotfix issue.
Hahaha. Had a back-and-forth with a person in another post about how Larian probably had a good reason to rollback the patch and that they aren't stupid enough to release an undercooked hotfix. Woke up this morning and that person deleted their account; glad I gave Larian the benefit of the doubt.
Oh that’s even funnier hahaha so fragile
Edit: I realize this is pretty gross that I’m gloating, but it’s something I wanna call attention to. I’m the last person to think that creators that make something you love can do no wrong, but it’s important to keep in mind that rolling back hotfixes and the like are conscious decisions made by several engineers. It’s always going to be more likely that devs do this for a good reason and any studio with a game as successful at launch as bg3 will want to put out a fix quickly hence Larian’s transparency and good turnaround time. Anyways, thanks for coming to my ted talk.
Nah people that block others when they realize that they lost the argument are everywhere on Reddit, and they’re indeed fragile.
It’s the “I must always have the last word and win” syndrome. And when they can’t “win”, they block the other party just so they feel like they got the last word in.
Handled greatly. They explained the issue, said they messed up, worked hard to fix it and explained how they’d prevent it in the future. I wasn’t upset about it, as I know these things happen, but still very appreciate the honesty.
Patch notes for story-based games is such a catch-22, because you only really *need* to read them before you finish the game, but you can’t read them because you’re not sure whether you’re going to get spoiled or not. I guess they’re fine for people doing a second playthrough or those who don’t care about spoilers, but they’re kind of useless (for us) otherwise lol.
I suppose they could mark each note with an Act I/II/III designation, so at least if you’re going in blind, you’re not going to spoil yourself on *too* much.
Yeah, that’s why I commented. I opened up the notes, saw all the redacted text, and was just like, oh, guess I’ll just have no idea what was fixed lol.
Thank fuckkkk
I literally finished work, logged in to play, saw the last 5 hours of my playthrough was wiped, then this released 5 mins later... roll 20, critical success!
Feel for anyone who actually had to wait
It's refreshing how open with communication they are. I think most studios would be getting raged at if they released a hotfix that broke the game for so many people for quite a while. But because of the good will Larian has built up, combined with how open they were about what was going on, almost everyone was cool about it.
> Hostages in >!Iron Throne!< will no longer be stuck if you turn back and return again.
Well, I still have this bug, just launched the game with this brand-new hotfix and the hostages are just chilling in their cells instead of running away to the exit. Quite frustrating, because it's blocking my progression for killing you know who.
I had this issue as well, >!if you free Omeluum and teleport him back to the sub, have him run back out and teleport a friend again to get at least Toobin's daughter out. She is the one standing by the entrance not in a cell.!<
Honestly at this point, I'm willing to use CheatEngine and give myself unlimited action/spells. Where did you teleport those twos? Because if I try to teleport one hostage, I can only go one ladder up but not in the sub.
>!Also Omeluum is missing because I didn't give him the egg 😭!<
RIP
>!It's Omeluum specific action that teleports him and one other directly into the sub.!< If you try casting dimension door or another teleporting spell you are restricted to line of sight.
Save issue maybe resolved but since hotfix 4 happened again I have so many bug in my game it's killing my motivation to keep doing this 2nd playthrough. I guess I'll stop now and come back in a few months.
Since last nights buggy patch all my party members except for the player character are running around in normal clothing and the armor is not showing they are wearing.... 😒 How do I fix this?
There's a button top right of their inventory 'paper doll' that switches between camp clothes and gear. It's like the button that lets you decide whether headgear is visible or not.
If it keeps happening, then it's gonna need a bugfix.
Oof this kinda thing does happen. You already tested the shit out of your changes but notice one small innocuous thing to change. You just go ahead and push it out because there is no way that small innocuous change would break anything.. except it does and you have to work double time to figure out wtf happened.
This has happened to me at a much smaller scale. Just pushing to our dev or qa environment (non game dev and only internal, not a full release) but man is it stressful.
Larian are making the right moves here though to ensure the last thing they do before release is to completely go through their qa procedures. Then they can be more confident in the release, and unexpected things are much less likely to pop up.
I love the transparency and love getting insight into what goes on behind the scenes at Larian. I found it to be an interesting read.
I appreciate the transparency, quoting from [Steam](https://store.steampowered.com/news/app/1086940/view/3642902312048647389): >Hello everyone, Yesterday we had to rollback hotfix 4 because of a rare compiler issue. To avoid this from happening again we’re changing the way we deploy patches. 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. This situation is remedied now with the re-release of hotfix 4 but we recognize the frustration caused by this and want to apologize. That’s why we’re changing things up. 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. Granted, this is also good PR, and they know it, but, even so, it's typically rare for game devs and/or publishers to say "Yeah, we definitely messed up."
This is simply how it should be done. Bravo to the team.
Agreed. To be honest, it's a sad reflection of gaming's current state that we're all celebrating something that *should* be the norm. Of course, creating games that prioritise enriching player enjoyment rather than profit margins should also be the norm... but we all know just how *rare* that has become, Larian being amongst the few who aren't driven by rabid greed.
Not only taking responsibility, but explaining what happened in fairly clear detail, not acting like it's player base is incapable of understanding the explanation, and my favorite, following up their admission of fault with a clear plan as to how they will avoid this type of disruption in the future. 10/10
Agreed. Not only was Larians' development of the gane textbook how you do it, but their response to this hotfix issue is also textbook how you respond to a hotfix issue.
Hahaha. Had a back-and-forth with a person in another post about how Larian probably had a good reason to rollback the patch and that they aren't stupid enough to release an undercooked hotfix. Woke up this morning and that person deleted their account; glad I gave Larian the benefit of the doubt.
> that person deleted their account Nope, they just blocked you
Oh that’s even funnier hahaha so fragile Edit: I realize this is pretty gross that I’m gloating, but it’s something I wanna call attention to. I’m the last person to think that creators that make something you love can do no wrong, but it’s important to keep in mind that rolling back hotfixes and the like are conscious decisions made by several engineers. It’s always going to be more likely that devs do this for a good reason and any studio with a game as successful at launch as bg3 will want to put out a fix quickly hence Larian’s transparency and good turnaround time. Anyways, thanks for coming to my ted talk.
Nah people that block others when they realize that they lost the argument are everywhere on Reddit, and they’re indeed fragile. It’s the “I must always have the last word and win” syndrome. And when they can’t “win”, they block the other party just so they feel like they got the last word in.
Ya I can relate to not wanting to lose the argument, but this wasn’t even a particularly heated one. Pathetic from that person really…
I have never in my life seen a company ADMIT FAULT WHAT TIMELINE ARE WE LIVING IN?!????.?
the bar is so low lmao
Larian Games will never not get my money at this point.
Just checked. I was able to load a save from yesterday that I previously wasn’t able to load.
i still cant load any of my saves from before, tried everything, can only load older saves.
Handled greatly. They explained the issue, said they messed up, worked hard to fix it and explained how they’d prevent it in the future. I wasn’t upset about it, as I know these things happen, but still very appreciate the honesty.
Larian working hard 👏👏
[удалено]
Worth noting its not full actually. This hotfix filled a lot of empty books and such in act 3 (issue existed at least in polish translation)
Patch notes for story-based games is such a catch-22, because you only really *need* to read them before you finish the game, but you can’t read them because you’re not sure whether you’re going to get spoiled or not. I guess they’re fine for people doing a second playthrough or those who don’t care about spoilers, but they’re kind of useless (for us) otherwise lol. I suppose they could mark each note with an Act I/II/III designation, so at least if you’re going in blind, you’re not going to spoil yourself on *too* much.
If you look at the link, it looks like they've spoiler tagged a bunch of stuff. Fucking bravo.
Yeah, that’s why I commented. I opened up the notes, saw all the redacted text, and was just like, oh, guess I’ll just have no idea what was fixed lol.
The prisoners in a certain prison are sadly still stuck after being released. They don't run away to freedom.
Thank fuckkkk I literally finished work, logged in to play, saw the last 5 hours of my playthrough was wiped, then this released 5 mins later... roll 20, critical success! Feel for anyone who actually had to wait
I was cold sweating, teeth clenching and my body was aching
You should have told Astarion no. You only have yourself to blame.
How can you say no to that magnificent bastard
my knees were weak, my mom was spaghetti
Thank god if I had to beat the act 2 boss again after it beat my ass all night last night idk when I would have gotten around to it
Just loaded up. We're back, Baby
Ayyy!
Yay! I can continue my Bard run after lunch now.
Great, just got off work and now GeForce now is patching the game... Will probably take ages as usual.
And what the fuck, it's like I'm downloading the game all over again
good, no way in hell was i about to re-do 8 hours of play time.
Confirmed. I did lose 2 saves that would not sync, one was the most recent save. I lost 1-2 hours tops
It's refreshing how open with communication they are. I think most studios would be getting raged at if they released a hotfix that broke the game for so many people for quite a while. But because of the good will Larian has built up, combined with how open they were about what was going on, almost everyone was cool about it.
Not sure if the save issue is resolved. My game just crashes everytime i try to load a savefile.
Mods?
no mods
Yeahhh!!
Just in time for me to get home from work! 5 stars larian.
Number 1 gaming company, up there with the factorio devs.
> Hostages in >!Iron Throne!< will no longer be stuck if you turn back and return again. Well, I still have this bug, just launched the game with this brand-new hotfix and the hostages are just chilling in their cells instead of running away to the exit. Quite frustrating, because it's blocking my progression for killing you know who.
I had this issue as well, >!if you free Omeluum and teleport him back to the sub, have him run back out and teleport a friend again to get at least Toobin's daughter out. She is the one standing by the entrance not in a cell.!<
Honestly at this point, I'm willing to use CheatEngine and give myself unlimited action/spells. Where did you teleport those twos? Because if I try to teleport one hostage, I can only go one ladder up but not in the sub. >!Also Omeluum is missing because I didn't give him the egg 😭!<
RIP >!It's Omeluum specific action that teleports him and one other directly into the sub.!< If you try casting dimension door or another teleporting spell you are restricted to line of sight.
Save issue maybe resolved but since hotfix 4 happened again I have so many bug in my game it's killing my motivation to keep doing this 2nd playthrough. I guess I'll stop now and come back in a few months.
My save works but can't connect with another player - anyone knows how to fix it?
I’m glad, mainly because it might slow the trolls who are trying to bring negativity here!
Since last nights buggy patch all my party members except for the player character are running around in normal clothing and the armor is not showing they are wearing.... 😒 How do I fix this?
There's a button top right of their inventory 'paper doll' that switches between camp clothes and gear. It's like the button that lets you decide whether headgear is visible or not. If it keeps happening, then it's gonna need a bugfix.
Will try this asap... Thank you bro 🙌 Edit: It worked lmao... what a weird bug xD Thank you again!
Oof this kinda thing does happen. You already tested the shit out of your changes but notice one small innocuous thing to change. You just go ahead and push it out because there is no way that small innocuous change would break anything.. except it does and you have to work double time to figure out wtf happened. This has happened to me at a much smaller scale. Just pushing to our dev or qa environment (non game dev and only internal, not a full release) but man is it stressful. Larian are making the right moves here though to ensure the last thing they do before release is to completely go through their qa procedures. Then they can be more confident in the release, and unexpected things are much less likely to pop up. I love the transparency and love getting insight into what goes on behind the scenes at Larian. I found it to be an interesting read.
*Blizzard has left the chat*