← PathwayLesson 6 · Animation & Game FeelNext lesson →

Lesson 06 · 60 minutes · Feedback layer

Make every event readable.

A working mechanic becomes satisfying when the game responds immediately. Layer motion, light, particles, sound, and camera feedback onto the events that matter most.

ANIMATIONPLAYERTWEENPARTICLESAUDIOCAMERA SHAKE
Big ideaFeedback translates invisible game state into something a player can notice.
PredictA stronger consequence should receive clearer feedback than a routine action.
TestMute or hide one feedback channel and ask whether the event is still understandable.
Why it mattersReadable feedback improves both accessibility and the feeling of control.
01 / READ

Feedback stack

Show the cause, the action, and the result.

Anticipation

A flash or sound warns that an enemy will attack.

Action

Motion and sound make the collision or collection unmistakable.

Result

The HUD changes, particles disperse, and the object leaves the scene.

Priority

Large consequences receive stronger feedback than small routine events.

Rule of restraint: Feedback should clarify an event. If everything shakes, flashes, and explodes, nothing feels important.
02 / CELL

Collection burst

Replace disappearance with a short sequence.

Add GPUParticles3D, AudioStreamPlayer3D, and AnimationPlayer to EnergyCell. Turn off monitoring before the effect so it cannot be collected twice.

energy_cell.gd · feedback
func collect() -> void:
    monitoring = false
    collected.emit(value)
    $Mesh.hide()
    $Particles.emitting = true
    $CollectSound.play()
    await get_tree().create_timer(0.7).timeout
    queue_free()

Do not free the node until its sound and particles have enough time to play.

Godot's Animation panel, showing the toolbar, track list, timeline, and keyframe editor sections that make up the AnimationPlayer dock.
This is the AnimationPlayer dock you'll open. The track list on the left holds one row per animated property; the timeline on the right is where you place keyframes for the burst — mesh hide, particle emission, sound cue — in order.

Screenshot: Godot Engine documentation, © Juan Linietsky, Ariel Manzur and the Godot community, CC BY 3.0.

03 / MOTION

Procedural animation

Use a tween for one-time motion.

HUD score punch
func punch_score() -> void:
    var tween := create_tween()
    tween.set_trans(Tween.TRANS_BACK)
    tween.tween_property($UI/ScoreLabel, "scale", Vector2(1.25, 1.25), 0.1)
    tween.tween_property($UI/ScoreLabel, "scale", Vector2.ONE, 0.18)

AnimationPlayer

Best for authored timelines, repeated animations, and editing multiple properties visually.

Tween

Best for short code-driven transitions toward a known value.

04 / CAMERA

Impact without nausea

Shake briefly, then return exactly home.

camera_shake.gd
extends Camera3D
var strength := 0.0
var rest_position: Vector3

func _ready() -> void:
    rest_position = position

func shake(amount := 0.12) -> void:
    strength = max(strength, amount)

func _process(delta: float) -> void:
    strength = move_toward(strength, 0.0, delta * 0.8)
    position = rest_position + Vector3(randf_range(-strength, strength), randf_range(-strength, strength), 0)
Why save rest_position?

05 / MIX

Audio and camera

Give each event a feedback budget.

  1. Collectible: use a bright chime, small particle burst, and HUD scale punch.
  2. Player damage: use a low impact sound, brief red vignette, and tiny camera shake.
  3. Enemy detection: use one warning tone and change the enemy light from yellow to red.
  4. Level win: stop threat music, play one success phrase, and reveal the win panel.

A/B playtest

Let a classmate play once with feedback enabled and once with audio muted. Ask which events became harder to notice and record the evidence.

Duplicate the project as SignalRun_06_Feedback.Your restore point must include distinct feedback for collection, detection, damage, and winning.
06 / CHECK

Definition of done

Your feedback helps when…

0/4 checked

Evidence: Ask a partner to name each event with the HUD hidden. If they cannot, revise the feedback.

Lesson 6 complete

Your systems now communicate with the player.