create-autoload

Create Autoload

Generate a single autoload singleton. For the canonical starter set (EventBus, GameState, SceneManager, AudioManager, SaveManager) use the bootstrap-godot-project skill.

Steps

1. Create the script

autoload/<snake_case_name>.gd:

extends Node
## {OneLinePurpose}.
## Registered as autoload "{PascalCaseName}". Access globally via {PascalCaseName}.

# signals
# enums
# constants
# vars

func _ready() -> void:
    pass

extends Node is the safe default. Use Node2D / Node3D only if the autoload needs a transform (rare). Object won't work — autoloads must be Node.

2. Register in project.godot

Add under [autoload] (create the section if missing):

[autoload]
{PascalCaseName}="*res://autoload/{snake_case_name}.gd"

The leading * enables the singleton — without it, the script just gets instantiated as a child of the root node, NOT exposed by name.

Order matters: an autoload that depends on another must appear after it. Example: SceneManager depends on EventBus → list EventBus first.

3. Reload project

Either restart Godot or open Project Settings → Globals → Autoload to see the entry. The editor exposes the autoload to scripts only after registration is loaded.

4. Use it

# anywhere in any script
SaveManager.save_game(0)
EventBus.player_died.emit()

Decision rules

When to autoload

✅ Cross-scene state that must persist across scene changes (current run data, audio bus volumes, save slot) ✅ Cross-scene event hub (EventBus) ✅ Single-instance services (AudioManager, SaveManager, SceneManager) ✅ Settings / config that any scene reads

When NOT to autoload

❌ Anything tied to a specific scene's lifecycle (player, level) ❌ Anything you might want multiple of (camera rig, AI brain) ❌ Heavy _process work that runs even when irrelevant ❌ Things that should be Resource instead (pure data)

Alternatives

Alternative	When
Group + get_tree().call_group()	Many-to-many broadcasts (alert all enemies)
Static class (class_name X extends RefCounted)	Pure utility functions, no state
Resource singleton via preload	Shared read-only data (curves, constants)
Service locator on a non-autoload root node	Tested apps where DI is preferred