[Fixt?] Crash on V-Ko trying to heal Furpies Game Version: 0.69.420#756

[lowercase_donkey]

A critical error has occurred. Please create a bug report on the forums here.
Please include what you did before the error and a screen-shot or copy-paste of the error message below:

Message:
e[r] is undefined

Stack:
kf/<@https://www.fenoxo.com/play/TiTS/backer/content_mhenga.a9bcd10c.js:1:3329402
doClick@https://www.fenoxo.com/play/TiTS/backer/main.a4d37f30.js:1:10198638
value/a<@https://www.fenoxo.com/play/TiTS/backer/main.a4d37f30.js:1:9912550
s@https://www.fenoxo.com/play/TiTS/backer/main.a4d37f30.js:1:6043520

 

[lowercase_donkey]

@Fenoxo, Sorry for bump, but I don't think there's any way to fix SSTD at the moment in the game.

V-Ko is broken:

Crash on Treat C.Snk at V-Ko

Cannot read properties of undefined (reading '1') Stack: TypeError: Cannot read properties of undefined (reading '1') at Object.func(https://www.fenoxo.com/play/TiTS/backer/content_mhenga.a9bcd10c.js:1:3329413) at Object.doClick...

forum.fenoxo.com

SSTD Cure

e[r] is undefined Stack: kf/

forum.fenoxo.com

and we can't return to FRST-14 for Tika:

Not sure if bug or not: Can't return to First-14

Only reporting this because on the non-java version you can so not sure if its intentional change or not, but there doesn't seem to be a way to return to First-14... doesn't show up in destinations when flying.

forum.fenoxo.com

Hoping one of these could be looked at, as I didn't want to progress until it was.

 

[lowercase_donkey]

If anyone else is stuck with this, you can heal from your browser console as a temporary fix.

chars.PC.statusEffects will display your current status effects. Find the one you want to remove, and note its storageName. In my case, it was "Sneezing Tits" this time.

Then delete it using JS:

chars.PC.statusEffects = chars.PC.statusEffects.filter(s => s.storageName !== "Sneezing Tits")

 

[lowercase_donkey]

Ok, you guys slay me

edit: besides the todo, I'm guessing it's an issue with the paren and lambda.

 

[Fenoxo]

Nah the issue is with javascript for loops containing var i instead of let i behaving badly with buttons. It should be fixed in the patch I pushed today.