Honest question, but how often did you playtest the game? Including all the previous issues that people have mentioned (Well, including me) the game also managed to crash on night 3.
How did any of these get missed? You might want to replay your game in case you find any additional bug that no one else has spotted yet.
haha, I guess the answer is "not enough times."
If you're serious about "honest question," the game is a jam entry, and so was developed in ~10days, the last 6 hours of which were devoted to QA time and misc panicking -- and afterwards the uploads were frozen for a week for reviews until a bugfix could be released, so a lot of people ended up hitting the same known issue. It's a problem with (relatively) long games with short dev cycles that bugs inevitably show up, and I'm looking to improve on it. This is my first time putting out a WebGL build (and working with fmod in general) so it does look like there's some stability stuff that needs to be patched up with my core engine code. My playtesting has been mostly with the desktop version, which doesn't help much with bugs exclusive to WebGL -- and I'm suspecting what you've run into is one, as I can't offhand reproduce it. The other stuff that's appearing in your dev console I think is harmless?
Bu thanks for the report -- I'm a firm believer that a player's most valuable resource is their time, and both "playing bugged stuff" and "submitting bugs" are hits against that. Will try to repro and get a 1.31 out.
