The music is just such a hard clash to the original and the whole atmosphere 😅

Always love seeing cool shit done in Godot - nice work friend!

FYI, on your web-page, in the "Heros" section, the "R" in Warrior is cut off. Same with the "ER" of sorcerer.

In game, Decard Cain's "Gossip" has an bug. I think it's supposed to be a new line but is missing the slash so is just being printed as text.

Overall, kind of fun nostalgia. It really needs optimization though, that was rough a rough play through. I'd say the enemies need to be more challenging, but after fixing the low frame-rates. Otherwise, everyone will just die.

Awful choice of music for that trailer

Vulkan GPU with 6 GB+ VRAM

Why target such a high spec? Why not aim lower?

To what extent is this project AI-assisted/generated?

What's the plan for the full release? Will it be open-source?

It does work on geometry, as I'm bit flipping the buffers, just not the shader values.

I've thought about making other effects that get added as another pass, but the joke with corruptor is to ruin the models directly, through unnecessarily convoluted and dangerous methods.

Option 1 behaves closer to Python's setdefault, since it only writes when the key is actually missing. Option 2 calls set_value on every read, which is harmless, but anyone reading a call site later will assume something changed

A denied click, the dull little thud for pressing a greyed-out button or trying to buy something you can't afford. Packs nearly always have confirm and cancel, but players hit the denied case constantly and cancel doesn't sound right there

It got a standard camera as well.

It got a standard camera as well.

I'm still waiting

They are for tracking I suspect but yeah it looks like the ultimate in pervert glasses for sure. Maybe time for this form factory to vanish.

I think they have cameras to track position in real space because these are virtual reality type glasses... Like, I thought XReal were for watching movies and stuff on planes, not for creeping. Am I wrong?

For crying out loud… creep glasses with cameras in them have to be banned, not enabled like this.

personally id go with option 1 since I have the preference to not set the config value if I dont have to

Thanks for the feedback!

It's based on Python's set_default dictionary method - it sets a value and The base class already has a set_value.

Not specific to Godot but I prefer the second one. The if breaks the flow of reading IMHO. You could add a comment to explain the whole thing though.

No judgement but why is it not called set_value instead of set_default_value? And why is it returning a value? I'm a noob at Godot.

Oh man. I have been learning Godot and have been working sporadically on a game which I would call an epilogue to the 70s science fiction movie Silent Running, called Running Silent. You play as the little robot sent off into deep space all alone. Wish I could have finished it in time to submit to this. Oh well.

Nice to see the XR jam back for another round. Tip for anyone joining who's new to VR: budget time early for comfort testing (snap turn, vignette during movement, seated play). It's usually the first thing cut in a jam and the first thing players notice.

Thanks! In fact, ambient light is controlled through Sky Contribution, so if it remains at its default maximum value, it's entirely driven by the sky shader's lighting. Of course, ambient light can also be controlled independently from a script. I'm actually using a script to control the DirectionalLight3D as well, simulating sunlight. And those transitions look pretty nice. Part two will be out in a week, and part three in two weeks. 😎

Nice topic for a series. Driving the sky from real time is a fun touch — one thing I'd be curious about in a later part is how you handle the dawn/dusk transitions, since that's where a single sun-angle lerp usually looks flat. Do you plan to tie ambient light / fog color into the same time value too?

Fun effect. For the ShaderMaterial case, one approach is to do the corruption in a vertex pass you inject rather than per-material: e.g. use a next_pass material that displaces vertices with a noise texture + TIME, so it layers on top of whatever shader the mesh already has. Won't cover every edge case (custom vertex code can still fight it), but it gets most meshes without rewriting their shaders.

For a prototype Logger, the thing that saves me most is cheap context tags (scene + system) on every line so you can grep one subsystem after you abandon half the experiment.

Second: a "debug only" channel that is a no-op in export builds — keeps the habit of logging freely without shipping noise.

Curious how you handle log volume when a prototype runs for weeks and the file grows — rotate, ring buffer, or just wipe between sessions?

Cracked-glass as a tutorial topic is useful because the effect fails loudly when UVs or normals are wrong — easy to learn from. In a browser export I've had to watch overdraw on the shatter pass more than the look itself; once the shards fan out, fill-rate eats mid-range GPUs fast.

Curious whether the tutorial stays on a single draw call with a dissolve mask, or spawns mesh shards. The former has been kinder to web exports in my experience.