Thank you so much for playing! Especially despite the framerate issue. This is easily the most time I've put into one project and learned a lot. Would you belive that I got the hopper and 100 fence challenge in the last 8 hours 😌? Just missed putting in an example setup for the hopper so I'm tempted to put an explanation of how here, but will refrain in the spirit of fair voting + self explanatory mechanics is a goal of mine. Again appreciate the play despite the frame rate issue, 3D is my focus so this is good information on how far I can push godot's web build with this kind of stuff, after the voting period I'm defintely going to take it as a challenege to optimize it so it's more playable on the web.
I also dabble in Godot, and there’s some optimizations I can give tips on, but the Debug tab is really useful for things like this, but I can give some shots in the dark. Using functions like set_process() and set_physics_process() to disable unnecessary logic. Use collision layers for big Area3D nodes so they only collide with what they need. Have physics objects “process_mode = Node.PROCESS_MODE_DISABLED” in _ready() function. These are some things that helped in my random projects. If you’re up you can hmu on discord: proti7 we can troubleshoot the issue, but if you want to go about it alone then good luck and I hope you’ll narrow down the issue because it could be a really cool experience with some extra polish.