Audacity. Mostly mixing up sounds I've recorded myself. I don't feel the need for a simpler, nor more complex tool.

Huh. I've read this article before, but never put 2 and 2 together that you could simply use it for game themes 🤔

I will definitely consider this approach in the future.

It wouldn't be too hard to write a little wrapper that would do this. Interesting to imagine how rate of change would be determined for things like color properties 🤔

So... technically you can even get the editor root node (it's all nodes!), find the dropdown, and force a selection via code. Seriously that's possible

Maybe with EditorInterface.get_editor_viewport_3d(idx).get_camera_3d(), or am I missing something about your use case?

I'm thinking that in places where I don't need time dilation, I can just multiply by the inverse to remove the dilation. So an opt-in system instead of an opt-out system.

@yurisizov.bsky.social have you seen the 4.6 release notes? 😅

I knew this feature has been suggested for ages (and a couple abandoned PRs), but I never knew it would come so quickly after I invested the time to make an editor plugin. I guess I get a bit of vindication though haha.

I use @export_group("Private") and then drag and drop w/ @export var.

It looks like this in inspector, and I never need to touch it (well, rarely):

Do you avoid export vars? For what reason?

I tend to actually create Scene files, even for scripts that wouldn't really require it (e.g., a HealthComponent). Then I attach that *scene* in multiple places. I never use a *script* in multiple places if that makes sense.

So in that sense the coupling is nearly 100% consistant for me.

Nope. I've improved upon it (according to me hahah) by making it generate @export vars, and assigning them.

It works by checking the open scene and checking if it matches the open script. I prefer export vars for refactoring reasons. Having the var auto-assigned is huge for me.

E.g., github.com/godotengine/...

I actually asked the author of the VSCode Godot plugin, and he didn't have interest in implementing. Also asked the VSCode IDE people, and same deal.

I think the disconnect is that Scenes != Scripts. Even though tighly bound Scene+Script coupling is very common in my workflow.