We will create a global Audio Manager to handle sound effects.
We will create a global Audio Manager to handle sound effects.
Embedded Files
What is an Autoload / Singleton / Global?
What is an Autoload / Singleton / Global?
An Autoload is a script or node that Godot loads automatically when the game starts, and—crucially—it never dies.
It is a globally accessible node that persists for the entire duration of the game. We use it for two main things:
An Autoload is a script or node that Godot loads automatically when the game starts, and—crucially—it never dies.
It is a globally accessible node that persists for the entire duration of the game. We use it for two main things:
- Data Persistence: Saving information (like High Scores) that shouldn't disappear when the level restarts.
- Global Communication: Allowing distant objects to talk without being directly connected."
Right-click on the Scripts folder
Right-click on the Scripts folder
in FileManager and add a script
in FileManager and add a script
Name it AudioManager.gd
Name it AudioManager.gd
Go to Project => Project Settings => Globals
Go to Project => Project Settings => Globals
Add it as a global variable (Autoload)
Add it as a global variable (Autoload)
Open the script
Open the script
Preload all the sfx files
Preload all the sfx files
Create a function to play sounds
It receives a sound and the volume level
Create a new AudioStreamPlayer
Set the sound and volume
Add to the scene
Play the sound
When finished playing destroy
Create a function to play sounds
It receives a sound and the volume level
Create a new AudioStreamPlayer
Set the sound and volume
Add to the scene
Play the sound
When finished playing destroy
Create functions to play
Create functions to play
All the different sounds
All the different sounds
Lower the volume as you wish
Lower the volume as you wish
In the Asteroid script
In the Asteroid script
In the on_destroy function
In the on_destroy function
Play the explosion effect
Play the explosion effect
In the UFO script
In the UFO script
When a bullet hits it
When a bullet hits it
Play the ufo hit effect
Play the ufo hit effect
In the UFO script
In the UFO script
In the shoot function
In the shoot function
Play the ufo shot effect
Play the ufo shot effect
In the Player Scene
In the Player Scene
Add an AudioStreamPlayer
Add an AudioStreamPlayer
Set engine.ogg as the stream
Set engine.ogg as the stream
Add an onready var
Add an onready var
for the AudioStream
for the AudioStream
When the player thrusts
When the player thrusts
If the audio is not already playing
If the audio is not already playing
Play the thrust audio
Play the thrust audio
When releasing the key stop playing
When releasing the key stop playing
When the shoot button is pressed
When the shoot button is pressed
Ask the audio manager to play the shot sound
Ask the audio manager to play the shot sound
Why is the engine sound not in the AudioManager?
Why is the engine sound not in the AudioManager?
The engine sound shouldn't be global because it needs to start and stop instantly when you press/release the key. It belongs on the ship.
The engine sound shouldn't be global because it needs to start and stop instantly when you press/release the key. It belongs on the ship.
It comes down to the difference between an Event (something that happens once) and a State (something that is ongoing).
Here is the breakdown of why the Engine sound is the "Exception to the Rule."
1. The "Light Switch" vs. "The Doorbell"
1. The "Light Switch" vs. "The Doorbell"
Think of the sounds in your game like household items:
The Laser/Explosion (Doorbell): You press the button once, and the sound plays to completion ("Ding-Dong"). You don't hold the button down to sustain the "Diiiiiiiiing." Even if you walk away from the door, the sound finishes.
Global Manager handles this best: It plays the clip and cleans it up when done.
The Engine (Vacuum Cleaner): The sound only exists while you are holding the button. The moment you let go, it must cut off immediately.
Local Node handles this best: The sound needs to be tightly coupled to your finger pressing the key.
2. The "Ghost Engine" Problem
2. The "Ghost Engine" Problem
If you put the Engine sound in the Global Audio Manager, you run into a serious logic trap when the player dies.
Scenario: You are holding UP (Thrust) to fly away from a UFO.
Action: The UFO shoots you. Your ship calls queue_free() and disappears.
The Bug (If Global): The Global Manager doesn't know you died. It just knows you told it to "Start Engine Sound" 2 seconds ago. So, even though your ship is gone, the empty space where you used to be continues to hum with an engine noise until you respawn.
The Fix (If Local): Since the AudioStreamPlayer node is a Child of the Ship, when you queue_free() the Ship, the Sound Player is deleted too. The silence is instant and automatic.
In the die function
In the die function
Play the explosion sound
Play the explosion sound
Page updated
Google Sites
Report abuse