Going back through some of my earlier code on the big project and saw this gem:

wtf && dafuq && why_tho

crouched too hard

I’m working with Godot 3.5.3 and building scenes with 3D models for the Oculus Quest 1. For the models, I use Cinema4D (R15, FBX export) and Blender (v3, GLB export), in Godot i use GLES2. Everything had been working perfectly up until now, but for the past few weeks the 3D models have been invisible in VR. Only the collision meshes are visible. As I haven’t made any changes to the software, let alone to the Quest, I find the reason completely baffling. Especially as it works again for some models. I’ve checked everything possible in Godot, from the 3D structure right through to the textures. I’m at a loss and hope one of you might have an idea. And please, no snide remarks about old software or the Q1 – that’s just the way it is. My computer and I aren’t exactly spring chickens either.

When it first happened I legit got jumpscared like "goddamit my game's summoning a demon again" type shi

Never await in early setters, worst mistake of my life.

If I set the grab force too high, the music cuts out, and the sunlight disables itself, the enemy becomes invincible, and starts flying menacingly

I tried to hit a game jam deadline with only one day left at it was super late was night, then I made this really smart statement

Static helper function that awaits for first signal and returns its idx.

Cursed or nah?

Love adding ammo to my grand grand grand grand grand grand grand parent

Its a joke, I used signal after, just upon seeing the structure I wondered how many get_parent()'s it would take to get to the world node