godot-autoload-architecture

To manage global game state in Godot without circular dependencies, use AutoLoad singletons combined with signal-based communication and a Service Locator pattern for dependency injection. This decouples system access, preventing initialization order issues and tight coupling between scenes.

The best way to structure a GameManager singleton in Godot is to use AutoLoad for global state, player scores, and pause functionality across scenes. Rely on signals for cross-scene communication and avoid storing scene-specific state within the singleton.

Accessing AutoLoads in _init() causes initialization order issues in Godot because other singletons or scene nodes may not have been instantiated yet. You should enforce anti-patterns to avoid this, ensuring dependencies are ready before they are accessed.

Handle scene transitions using Godot singleton architecture by routing global state and transition triggers through an AutoLoad manager. Use signal-based communication to notify nodes of scene changes, ensuring decoupled system access and preventing scene-specific state storage.

You should avoid using singletons for state management in Godot when storing scene-specific state or when over-reliance on global access creates tight coupling. Instead, use dependency injection patterns like Service Locator for decoupled system access.