Baldur’s Gate III Community Update #9 - Launch
-
Category: News ArchiveHits: 1342
Following a successful early access launch that managed to break Steam’s servers, Larian Studios brings us a new Community Update for Baldur’s Gate III. This time around, we get some launch day anecdotes, a bunch of early access stats, and the patch notes for the game’s first non-hotfix update. If you’re interested in reading about Larian’s customary by this point launch day misadventures, you should definitely check it out.
Here are the text parts:
Hello everyone!
We launched Baldur’s Gate 3 exactly 1 week ago, ish. The launch surpassed all our expectations. Our philosophy heading into Early Access was to hit a comfortable amount of players, gather feedback, and incrementally iron out and improve the game towards launch.
Good news! That’s still the plan. But the *bigger than expected launch* broke a few things. In chronological order, it apparently broke Steam, it then broke our launcher sign ups because the servers couldn’t keep up, and then it went on to break our support pipeline with a huge influx of support tickets. We’re not complaining. These are good problems to have.
The day before launch, the weather also broke the Ghent basement. Which was suboptimal because we were shooting a thing for those who get to the end of Act 1 (no spoilers).
Soon after, the power broke in Quebec. This is the 3rd launch in a row where Larian has had a powercut somewhere. One of the good things about upscaling to 5 studios globally, is that now if one gets defeated by water or electricity (please, not both together), we have 4 other studios to deal with the tornado, earthquake, or a Kaiju. At this point launching a game is basically like playing Sim City.
On launch, which we managed to get to in the end, we celebrated very socially, very distanced, and watched you all play the game. Someone at the office (we won’t mention the name of the perpetrator... I mean, we get it) stole Gale from the gateau. We have since recovered Gale.
Since then, we’ve shot out 3 hotfixes that have greatly reduced the number of crashes and stability issues experienced in the first week of launch. The real heroes in this are the community who stuck with us as we were working on those patches and hotfixes. We know that jumping into an unfinished game in Early Access, when your saves will eventually be wiped, is a big ask. We are phenomenally grateful to each and every one of you who’ve jumped in, provided feedback, and sent error reports. These reports are channeled back to our QA leads and producers, and the information you provide helps us to understand why certain things are happening, and thus reproduce and solve them.
Working with feedback
All feedback, positive or negative, is extremely helpful and important to us. We’re really grateful to everyone who organizes their thoughts and talks to us on Steam, or the forums, or the feedback form. For us, that’s a big part of what Early Access is about. Keep the feedback flowing, and we’ll keep shooting out those updates.
Under the hood we’re starting to get our first look at data, and decisions players are making, which teaches us how you’re playing the game. Before you launch a game, you’re making a lot of assumptions about what people will do, and why they’ll do it. When you launch, you can start to see if you were right.
As an example, let’s look at a cut down version of a heatmap (avoiding spoilers)! This is a *map of death* (make a spooky noise when you read that). *MaP of dEaTh*.
As our early access campaign progresses, you’ll see a shift as combat is tuned and content is altered. It might not look like much, but this shows us where to investigate. We can correlate this with direct player feedback, balancing feedback, and even bug reports to find out why people are dying where they’re dying, and also is it normal that people are dying there? It’s just one example of how people are helping simply by playing the game.
A strange point of interest is for instance that there are lots of deaths where you first meet Gale. Maybe people don’t like being ambushed by a spooky wizard jumping out of a rock? Something to investigate.
The amount of death in the camp is also surprising. We won’t spoil as to why that may be, but there are many, many in depth stories online, and on Reddit, about how death befell the campsite. They’re hilarious so please keep sharing them!
We also know how many times characters are dying. Gale died 333757 times. 333758 if you include the cake incident. Gale has a party-member kill-rate 4 times higher than any NPC in the game, so maybe he deserved it?
The Owlbear Cub has killed 5717 of you brave enough to try and tame it. Exactly 4000 people died as a result of interrupting the intimate moments of Ogres and Bug Bears.
And Shadowheart is the only companion that died more than the player character.
We’ll continue to share more data and insights over Early Access, but this is early days. Play however you want, in whatever way you want. There’s no one way to play the game. We’ve created systems that try to react to whoever you are, and whatever you do. The results of this make the game better.
(We’re working on this btw. Soon.)
Quick note on Discord and public multiplayer lobbies: The public multiplayer lobbies will soon be set live. Discord integration is in the works, so your friends can stop pinging you when you’re trying to tame a Mind Flayer (and dying 3753 times).
With that said, here are the full notes for Patch 1 - Launch. TLDR; fewer glitches, better stability, and more polish.
Improvements:Bug Fixes:
- Added polish and bug fixes to several in-game cinematics, such as Shadow Heart recruitment, Astarion recruitment and Volo's Poem. (These will be ongoing throughout EA).
- Added minor text tweaks to various bits and bobs.
- Altered certain dialogue choices for different NPCs.
- Added extra combat tutorial messages to better explain the basics (let us know how you get on).
- Astarion no longer thinks Lae'zel inspected you at camp when she is not in your party. Quite rightly.
- Fixed a crash related to having the level up screen open while in a dialog.
- Fixed a crash related to dropping items from inventory.
- Fixed a rare crash that could happen at the start of combat.
- Fixed a possible blocking issue when using the transponder at the end of the tutorial twice.
- Fixed black screen issue when ending tutorial if the transponder was used by any character that is not the main player avatar.
- Fixed a possible blocking issue when reassigning characters to others players while in combat.
- Fixed an issue with lip sync not working correctly.
- Fixed several localization issues.
- Fixed combat UI not updating correctly when someone joined during combat.
- Fixed party shared gold and items not always working in dialog checks.
- Fixed summons from NPC’s getting stuck in combat.
- Fixed levelled up characters having duplicated racial and class features.
- Fixed not being able to level up to level 4 on a Zariel Tiefling Cleric of Light due to cantrip selection.
- Fixed text cut-off issues in several interfaces.
- Fixed party members getting stuck trying to open doors they run past.
- Fixed listening in to dialogs getting stuck in multiplayer, also causing players not being able to save.
- Fixed camp button being broken after closing the camp window with escape key.
- Fixed "end the day" multiplayer message being broken if a player closed it with an escape key.
- Fixed certain quests not having map markers.
- Fixed certain secret entrances incorrectly showing up on the map.
- Fixed incorrect player portraits in the lobby screen as more people joined.
- Fixed Cambion wings and Tiefling tail animations.
- Fixed map not centering correctly on player characters in smaller subregions.
- Fixed health values not being synced correctly to the Baldur's Gate 3 twitch extension.
- Fixed superiority die not showing actual values when using abilities such as Menacing attack.
- Fixed minor issues with hair, skinning and textures on several models.
- Fixed lighting issue in owlbear cave.
- Fixed not being able to walk over corpses.
- Tweaked ragdolls to reduce the possibility of models exploding (or glitching. Idk how to explain it, but it’s spooky).
