Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Not sure if this was a crash or just the end of the demo, but when the first guard gets droned, the game seemed to freeze/crash when the option for the tutorial was selected. 

It's a somewhat comon issue on firefox that I haven't been able to work out yet. Did you also play through firefox?

Nope. I'm on Brave. However, both are somewhat more on the privacy focused side of things. Might be a caching/cookie issue or conflict with the save system? It wasn't crashing when saving but I haven't actually tried to load one yet.

(1 edit) (+1)

Just loaded the save and it loaded without crashing, however, the UI or at least the health and such on the bottom right didn't load. After dying to the guard that entered, and loading from that screen, the UI displayed properly but it still crashed at the tutorial selection when selecting "Answer". Further testing, it crashes on both the "skip tutorial" option as well as "Answer". Will try on a different browser shortly.

(+1)
Downloaded Chrome and it still crashed at the same spot. I don't know if it's relevant but the console shows this right when you select an option.

2index.js:459 res://Scenes/Dialogue Balloon/balloon.tscn

I dunno' if the "2" right before index.js:459 means it's trying to load the same thing twice, but it seemed like the only line in the console that showed that little number in a bubble just to the left of "index.js:459". 

Best of luck with the bug squashing! Seems like a very fun game!

I've done some tweaking and got it working on my end, would love to know if you can get past the bug now. Thanks so much for the detailed responses!

Yup, got past the crash this time around. Haven't tried the option to skip the weapons tutorial but seems like it's fixed.

I ended up just removing the option 🙃

(+3)

got the same crash only i downloaded it and am playing localy.

(+1)

It gives an error called "content-warningac46e200.json" maybe that's the problem?

That might actually be something, thank you!