event-bus

You can decouple Godot nodes by using a typed global EventBus autoload that lets unrelated parts of your project communicate through signals without holding direct references to each other. This eliminates tight coupling and brittle dependencies across UI, gameplay, and system layers.

Yes, the EventBus supports both GDScript and C# for emitting and listening to typed signals. It enforces explicit connections and disconnections in _ready() and _exit_tree(), with C# specifically requiring explicit disconnection to manage signal lifecycle properly.

You emit typed signals with optional payloads through the EventBus singleton to pass structured data between nodes. Producers emit these signals without knowing who consumes them, enabling scalable event-driven architectures across different systems.

You should use an event bus when unrelated nodes must emit and listen to signals across UI, gameplay, and system layers without holding references to each other. This approach prevents brittle dependencies and supports scalable event-driven architectures.

You need to explicitly disconnect C# signals in _exit_tree() because the typed EventBus requires explicit connection management in C# to prevent memory leaks and orphaned signal callbacks. GDScript handles this lifecycle differently, but C# enforces strict disconnection.