[0.69.420 -BACKER#1105] Siegwulfe Crash

[zabcdefg]

Siegwulfe:
(TL;DR: Crashing on crew interaction + Activation scene never plays)
Interacting with Seigwulfe (bought from Dr.Badger) in the crew menu causes the following crash:

Version: 0.69.420 -BACKER#1105
Message:
e is undefined
Stack:
hC@https://www.fenoxo.com/play/TiTS/backer/content_follower.e6de3f65.js:1:8381400
value@https://www.fenoxo.com/play/TiTS/backer/main.7681cd5b.js:1:11096481
47349/A

Siegwulfe works fine in combat, save for the tease damage appearing as a separate line refering to the PC rather than being in the same line like most teases.

The button for Siegwulfe shows the following:


Looking at some commented out code in a debugger, the flag "WULFE_ON_SHIP" is never set to false when its supposed to be. The function activateSiegwulfe() is never called either, as it requires the flag to be false. Manually setting the flag to false shows the proper button in the crew menu and calls the activate function when you access your storage, but pressing the "Name Her" button gives the following error:

Version: 0.69.420 -BACKER#1105
Message:
this.userInterface is undefined
Stack: iC@https://www.fenoxo.com/play/TiTS/backer/content_follower.e6de3f65.js:1:8373796
doClick@https://www.fenoxo.com/play/TiTS/backer/main.7681cd5b.js:1:10935013
value/a<@https://www.fenoxo.com/play/TiTS/backer/main.7681cd5b.js:1:10597775
s@https://www.fenoxo.com/play/TiTS/backer/main.7681cd5b.js:1:7267600
setTimeout handler*k/<@https://www.fenoxo.com/play/TiTS/backer/main.7681cd5b.js:1:7267638
u@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:284902
d@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:285045
64448/y/<@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:285191
y@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:285277
ut@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:300793
it@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:300603
lt@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:300961
ht@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:302168
L@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:398968
U@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:286600
Jt@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:308125
Yt@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:307343
60053/t.unstable_runWithPriority@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:428730
$o@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:329666
M@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:398745
Xt@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:307158
EventListener.handleEvent*Qt@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:307082
qt@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:306884
vt@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:302476
cn@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:310147
eu@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:361396
bl@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:381544
yl@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:381433
vl@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:381286
ul@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:378316
nl@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:375080
Vl@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:396334
64448/Xl/<@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:397579
cl@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:378663
Xl@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:397564
64448/t.render@https://www.fenoxo.com/play/TiTS/backer/vendors.6eddb424.js:1:400551
37326/

Exiting out of the scene using mainGameMenu() doesn't cause a crash, but the button reverts to the picture shown above.

[Goo armor moved to separate thread]

 

[zabcdefg]

Decided to make a couple saves that reflect my char at the time of the error if it makes fixing any easier. Although I did use cheats to make these, it shouldn't have anything that isn't possible to get in the current version of the game (just added money and leveled to max level to make quests easier).

 

[Fenoxo]

Different bugs should REALLY go in different threads, so that they can be individually assessed, responded to, and closed as appropriate.

 

[Fenoxo]

Paging through Siegwulfe, it looks like she needs a lot of touching. Some buttons still use the flash-style methodology (that crashes hard when it tries to load them), and I'm converting them when I see them.

I'm not 100% happy with how tease responses are displayed in JS version atm, but I went ahead and matched the alignment to PC-style.

 

[Fenoxo]

I've adjusted button calls for ~80 spots in Siegwulfe's main file for now.

 

[Fenoxo]

Looking at some commented out code in a debugger, the flag "WULFE_ON_SHIP" is never set to false when its supposed to be.

Feeling a bit worn down today, so gonna commit what I have here, then dig into the more involved stuff like the above.

 

[zabcdefg]

Feeling a bit worn down today, so gonna commit what I have here, then dig into the more involved stuff like the above.

Thanks!

Different bugs should REALLY go in different threads, so that they can be individually assessed, responded to, and closed as appropriate.

That is fair, i didn't want to spam all at once (probably should've reported the bugs as I got them). I can see how it would mess with workflow. I can yoink all the Goo Armor stuff and put it in a different post if it'd make it easier for y'all, but I wouldn't want to mess up anything that you've already done in terms of assessment.

 

[Fenoxo]

then dig into the more involved stuff like the above...

...LATER.

More evidence I need a brainectomy.

Yeah by all means spin the goo armor off into another thread.