0.6.2 game still crashes at start of Alissa fight

merprime

Member
Mar 31, 2023
7
2
124
In both Firefox and Chrome, the game crashes immediately at the start of the fight with Alissa, no matter what dialogue options are chosen. In Chrome, it gives the error:

version: 0.6.2 TypeError: Cannot read properties of null (reading 'isUltimate') at https://www.fenoxo.com/play/CoC2/backer/Content_Misc.c3060c066df34cb3e0bc.js:1:4142267 at Array.filter () at window.RynQuest2ConfrontAlissaDoCombat [as func] (https://www.fenoxo.com/play/CoC2/backer/Content_Misc.c3060c066df34cb3e0bc.js:1:4142238) at doClick (https://www.fenoxo.com/play/CoC2/backer/48.4a82617b0a641dde5b62.js:1:38232) at l (https://www.fenoxo.com/play/CoC2/backer/manifest.d73a790da87334be0980.js:2:4323997).

This error has been persistent since 0.6.0 across multiple saves, multiple browsers, and multiple computers, and prevents completion of the quest.
 

Upcast Drake

Well-Known Member
Moderator
May 27, 2017
2,600
2,061
Southeast USA
Have you recruited Etheryn? What level is your character?

I've made a change that should fix it in the next release, tho I think this bug could only happen if either Etheryn was never recruited, or the PC was below level 5. Was that the case for you?
 

merprime

Member
Mar 31, 2023
7
2
124
Neither of these is the case for me. My character is level 7 and recruited Etheryn when she first entered the game.
 

merprime

Member
Mar 31, 2023
7
2
124
This is the closest save I have to the crash.
 

Attachments

  • CoC2_Baitus II_691.coc2
    189.2 KB · Views: 4

Upcast Drake

Well-Known Member
Moderator
May 27, 2017
2,600
2,061
Southeast USA
Hmm very strange, the fix should resolve it either way, but your Etheryn seems to have some extra powers she shouldn't, probably some wonky state left over from the patch when equipment sets were added or something.
 

merprime

Member
Mar 31, 2023
7
2
124
Hmm very strange, the fix should resolve it either way, but your Etheryn seems to have some extra powers she shouldn't, probably some wonky state left over from the patch when equipment sets were added or something.
Interesting that it didn't cause an issue with any other encounter. Such is coding, I suppose. Thanks for taking a look.