It's strange, because I only use Firefox and have never been able to reproduce this bug, and meanwhile, I've had other people stream the game to me and have a 100% reproduction rate. It consistently doesn't happen on Chrome, either.
I am iffy on Node.js, as I've experienced strange corruptions with it and it's a lot less lightweight. I've also experienced it causing projects running an older version of Node.js to stop working altogether, which is strange. We will see, but I don't consider Win7 support a priority.
I've gotten dozens of reports about this and all I can say is that it's most definitely on Firefox's side. I had a user send in a bug report and the best we can hope for is for them to fix it on their end. Standalone or Chrome should work fine.
Unfortunately I think most things have phased out Windows 7 by now. The technology behind the Windows build (Webview2) more than likely doesn't support it.
Most antiviruses will flag new/unsigned applications, of which this is both. You're free to not use the standalone version–the web version is identical.
Oh, sorry if I came off as blunt. I was aware of it, and I tried to combat it with this latest patch but it seems that hasn't worked. It's very annoying to circumvent this for new applications.
Leaving this secret out was a conscious decision–this was a student project made from scratch in two weeks, and I didn't have the time to figure out elevator physics. There's a different secret elsewhere on the map.
There is very little I can do in the way of any virus protection measures going off. It's only because it's new/unsigned. What you're downloading is exactly what you see in the web version.
