Install Asset
Install via Godot
To maintain one source of truth, Godot Asset Library is just a mirror of the old asset library so you can download directly on Godot via the integrated asset library browser

Quick Information

Easily add Dependency Injection to your project.With the plugin enabled, simply create a [DependencyProvider] node in your Main scene and assign your dependencies, then in any sub scene, so long as it is in the scene tree and has any node that has a script with an '_inject' function, add a [DependencyInjectionRequester] node.This tool is useful in cases where:1. You do not have direct access (via @export) to the nodes you need in a script and do not wish to create a global autoload.2. You want to rely on abstractions to interact with other parts of your code.3. The nodes you need have their own in-scene dependencies they need to have direct access (via @export) to.
dependency-injection-system
A simple DI implementation for Godot 4 made with GDScript.
Easily add Dependency Injection to your project.
With the plugin enabled, simply create a [DependencyProvider] node in your Main scene and assign your dependencies, then in any sub scene, so long as it is in the scene tree and has any node that has a script with an '_inject' function, add a [DependencyInjectionRequester] node.
This tool is useful in cases where:
1. You do not have direct access (via @export) to the nodes you need in a script and do not wish to create a global autoload.
2. You want to rely on abstractions to interact with other parts of your code.
3. The nodes you need have their own in-scene dependencies they need to have direct access (via @export) to.
Reviews
Quick Information

Easily add Dependency Injection to your project.With the plugin enabled, simply create a [DependencyProvider] node in your Main scene and assign your dependencies, then in any sub scene, so long as it is in the scene tree and has any node that has a script with an '_inject' function, add a [DependencyInjectionRequester] node.This tool is useful in cases where:1. You do not have direct access (via @export) to the nodes you need in a script and do not wish to create a global autoload.2. You want to rely on abstractions to interact with other parts of your code.3. The nodes you need have their own in-scene dependencies they need to have direct access (via @export) to.