Interesting indeed, that is VERY helpful feedback. I assumed it was working the same for everyone. I cannot reproduce the bug so it may be a browser and/or OS difference. Would you mind sharing what browser you were using? Also, did you try different combinations for those first 2 frame-entries in that room, or did you always try the same one (and if yes, do you remember what the combination was)?
If it is a browser difference issue, this may explain why I get fewer ratings than I expect at most game jams. If I use different browsers the lighting looks different in each but the core game mechanics all work the same in my builds where I've tested my projects, even on mobile phone browsers, so this is a very helpful moment to find someone with a setup that it works different on, so I do really appreciate whatever bug report info you can provide.
Speaking of which, I did not encounter anything glitching through the floor on yours like you described, but I encountered different issues, so just in case it's helpful to you I'll do the same: I was using Google Chrome on Windows to use yours, and the bugs were almost entirely with the green/cyan key which would show up on the floor sometimes next to the sliding shelf object it was in, but even after it was away from that shelf if I slid the shelf around the key would move around too wherever it was, and it would even slide right through walls while doing so. Also, sometimes (or was it every time?) after getting that key if I put it on top of a container then flicked the lights off/on it would teleport the key to the middle of the floor in that room, though that happened consistently enough that I'm guessing that might have been intentional on your part to reset the key.
Thank you much for the feedback.
Here is what my second room does for me on Google Chrome:
Viewing post in Escape Room jam comments
I am on a slightly hardened Firefox (i implemented just a few of the things shown in https://brainfucksec.github.io/firefox-hardening-guide-2024 ) and it has been causing issues, such as Unity using WebGL, which is why i had to ignore this hardening technique, however recently it has been very stable for me. My OS is Linux Mint which should not interfere and it is praised to be the most stable Linux ever. Browsers are usually OS agnostic as they run completely separately, but idk, i’m not a browser expert!
I usually try something random, but most commonly i just take the fire orb and win using that. I would like randomly use the orbs on the wall and then take the fire orb and usually it gives me the win screen. I did use the fire orb right to left, but not always.
As for your feedback on my game, i would rather we keep both organized in each game’s own section, it gets a bit confusing. However thank you for providing this feedback, it certainly is interesting as i have not programmed anything physics related other than freezing and un-freezing physics to lock and unlock stuff. There is no code to reset anything, to move anything, etc. (well there is, for the floating mechanism and for the springing sliding mechanism, but it just applies a directional force) That must be a problem with Godot or the way Google Chrome handles this type of game, or maybe even load order, as i am using web multithreading which is a brand new and not very stable yet Godot feature. But it dramatically improves web performance. Also about stuff clipping through the floor, i also had no issues with that, but i decided to keep it since during development the drawer door that you clog the water pool with, that fell through the floor several times.
Your idea to share a video is actually quite genius, we’ve been explaining stuff that is so much easier to just show! I appreciate it a lot.
Here goes (i don’t want to use YouTube, so a random file website it is, hopefully it works): https://files.catbox.moe/at31xj.mp4
Also forgot to mention about rating. I did count the rates earlier and the average seems to be about 3.8 currently (61 rates / 16 entries), so if a game in this jam has 3-4 ratings, that should basically be average and you have 5.
Ah, hahahaha! Thank you for that video, I get it now. The win message happens when you get to the next room, but I must not have added a check to make sure that it was the player who entered the room... it looks like you triggered it just by holding the orb and putting the orb through the door, triggering the next room's trigger collider. I must have forgotten the if statement in that room's code.
I just tried and can easily reproduce it now, so yeah, it's a simple bug in my own code that will take seconds to fix. Thank you again.