dependency-injection

To decouple Godot systems, wire dependencies using autoloads, service locators, and @export injection. This avoids hard-coded get_node lookups, preventing tight coupling and brittle scene hierarchies in projects with multiple interdependent systems.

The best way to wire Godot node dependencies is through explicit declarations using @export or public properties. This scene injection approach enables modular composition by avoiding hard-coded paths and replacing fragile get_node lookups.

Yes, this dependency injection approach is designed for Godot 4.3+ projects. It supports multiple interdependent systems such as audio, gameplay components, UI, and testing scenarios, requiring explicit dependency declarations via @export or public properties.

Yes, you can use the service locator pattern for optional or swappable Godot components. This approach is specifically useful for managing plugins or injecting test doubles, allowing flexible dependency wiring without tight coupling to specific scene tree paths.

You should avoid get_node lookups because they create tight coupling and brittle scene hierarchies. By requiring explicit dependency declarations via @export, components remain decoupled, significantly improving both testability and maintainability.

To test Godot gameplay components, use the service locator pattern to inject test doubles. This Skill includes specific guidance on testing scenarios and anti-patterns, ensuring your explicitly declared dependencies remain fully swappable during tests.