12-16-2019, 02:26 PM
A QA breakdown of The Outer Worlds’ elusive companion killing bug
<div style="margin: 5px 5% 10px 5%;"><img src="https://www.sickgaming.net/blog/wp-content/uploads/2019/12/a-qa-breakdown-of-the-outer-worlds-elusive-companion-killing-bug.jpg" width="200" height="200" title="" alt="" /></div><div><p><em><big><strong>“All of the cases we had were essentially ‘hey something bad happened in the last ten hours and now my quest is broken.’”</strong></big></em></p>
<p><em>– Obsidian QA lead Taylor Swope offers a candid look at how the team worked through an especially mysterious bug.</em></p>
<p>Devs and players alike always get a kick out of bug stories, especially when the cause of whatever bug managed to perplex the teams dedicated to sniffing out those issues ahead of and following launch.</p>
<p>Obsidian QA lead Taylor Swope shared <a href="https://twitter.com/_taylorswope/status/1205252714680045568">one such story on Twitter</a> about the studio’s recent release <em>The Outer Worlds</em>. The thread chronicles the team’s own internal efforts to figure out why some companions were being marked as dead in-game, something impossible on most game modes, and explains how a player’s offhanded comment helped track down the eventual culprit.</p>
<p>The bug itself marked certain companions as dead, despite the fact that they were still alive and present in the game itself. But that deceased designator automatically failed personal companion quests, permanently locking players out of those questlines without any idea as to why.</p>
<p>“There were one or two cases before launch where this issue seemed to happen but no one in QA ever managed to reproduce it and despite our best efforts we couldn’t learn anything concrete about it,” tweeted Swope. “One reason it was so hard to pin down is that it was impossible to tell when the bug actually happened—all of the cases we had were essentially ‘hey something bad happened in the last ten hours and now my quest is broken’. Investigating it involved figuring out the location of every script and line of code that could possibly make the game think that a companion was dead.”</p>
<p>Swope’s full thread is a great read, and <a href="https://twitter.com/_taylorswope/status/1205252714680045568">can be found here</a> for a full rundown of how the QA team attempted to piece through the information they had to fix whatever was killing companions behind the scenes.</p>
<p>To spoil the ending, the culprit ended up being tied to how characters interact with ladders, and how initiating a conversation with an NPC prevents characters for initiating new actions, but allows them to continue the ones they’ve already started.</p>
<p>“Eventually, an offhand comment in one user’s review mentioned seeing a weird bug where a companion was ‘climbing nothing,’ and this comment led me to figuring the whole thing out,” tweeted Swope.</p>
<blockquote class="twitter-tweet" data-conversation="none">
<p dir="ltr" lang="en">So, if someone started climbing a ladder and the player entered a conversation before they stopped, they wouldn’t be able to exit the ladder, and, well…. (18/18) <a href="https://t.co/xcduTy4d12">pic.twitter.com/xcduTy4d12</a></p>
<p> — Taylor Swope (@_taylorswope) <a href="https://twitter.com/_taylorswope/status/1205252973611237376?ref_src=twsrc%5Etfw">December 12, 2019</a></p></blockquote>
</div>
https://www.sickgaming.net/blog/2019/12/...lling-bug/
<div style="margin: 5px 5% 10px 5%;"><img src="https://www.sickgaming.net/blog/wp-content/uploads/2019/12/a-qa-breakdown-of-the-outer-worlds-elusive-companion-killing-bug.jpg" width="200" height="200" title="" alt="" /></div><div><p><em><big><strong>“All of the cases we had were essentially ‘hey something bad happened in the last ten hours and now my quest is broken.’”</strong></big></em></p>
<p><em>– Obsidian QA lead Taylor Swope offers a candid look at how the team worked through an especially mysterious bug.</em></p>
<p>Devs and players alike always get a kick out of bug stories, especially when the cause of whatever bug managed to perplex the teams dedicated to sniffing out those issues ahead of and following launch.</p>
<p>Obsidian QA lead Taylor Swope shared <a href="https://twitter.com/_taylorswope/status/1205252714680045568">one such story on Twitter</a> about the studio’s recent release <em>The Outer Worlds</em>. The thread chronicles the team’s own internal efforts to figure out why some companions were being marked as dead in-game, something impossible on most game modes, and explains how a player’s offhanded comment helped track down the eventual culprit.</p>
<p>The bug itself marked certain companions as dead, despite the fact that they were still alive and present in the game itself. But that deceased designator automatically failed personal companion quests, permanently locking players out of those questlines without any idea as to why.</p>
<p>“There were one or two cases before launch where this issue seemed to happen but no one in QA ever managed to reproduce it and despite our best efforts we couldn’t learn anything concrete about it,” tweeted Swope. “One reason it was so hard to pin down is that it was impossible to tell when the bug actually happened—all of the cases we had were essentially ‘hey something bad happened in the last ten hours and now my quest is broken’. Investigating it involved figuring out the location of every script and line of code that could possibly make the game think that a companion was dead.”</p>
<p>Swope’s full thread is a great read, and <a href="https://twitter.com/_taylorswope/status/1205252714680045568">can be found here</a> for a full rundown of how the QA team attempted to piece through the information they had to fix whatever was killing companions behind the scenes.</p>
<p>To spoil the ending, the culprit ended up being tied to how characters interact with ladders, and how initiating a conversation with an NPC prevents characters for initiating new actions, but allows them to continue the ones they’ve already started.</p>
<p>“Eventually, an offhand comment in one user’s review mentioned seeing a weird bug where a companion was ‘climbing nothing,’ and this comment led me to figuring the whole thing out,” tweeted Swope.</p>
<blockquote class="twitter-tweet" data-conversation="none">
<p dir="ltr" lang="en">So, if someone started climbing a ladder and the player entered a conversation before they stopped, they wouldn’t be able to exit the ladder, and, well…. (18/18) <a href="https://t.co/xcduTy4d12">pic.twitter.com/xcduTy4d12</a></p>
<p> — Taylor Swope (@_taylorswope) <a href="https://twitter.com/_taylorswope/status/1205252973611237376?ref_src=twsrc%5Etfw">December 12, 2019</a></p></blockquote>
</div>
https://www.sickgaming.net/blog/2019/12/...lling-bug/