Screen Shake in Godot 4: The Trauma Method (with Code)

Screen shake is the single fastest way to make your game feel alive. Without it, bullets feel like pokes, explosions feel like firecrackers, and deaths feel like a timeout screen. With it, every impact has weight. Here is how to wire up the trauma method in Godot 4 — the most flexible approach and the one used behind the scenes in countless indie hits.

Why the Naive Approach Breaks Down

The first screen shake most devs write looks like this: on impact, pick a random offset, apply it for a few frames, done. The result is a choppy, jittery flicker that reads as a visual glitch rather than impact. Two problems:

1. Frame-to-frame random values create jitter, not motion. The camera teleports instead of swinging.
2. A flat amplitude means every hit feels the same. A fist and a grenade get the same nudge.

The trauma method solves both.

Why It Works

The trauma model, popularized in the indie community through Jan Willem Nijman's (Vlambeer) 2013 talk "The Art of Screenshake" at INDIGO Classes (YouTube, 2013), works on three ideas:

• Accumulation. Trauma is a 0–1 value that adds up. Fire three shots and the shake compounds; it does not reset each time.
• Squaring. The actual shake displacement is trauma² (or trauma³). At 0.3 trauma the camera barely moves (0.09 of max); at 1.0 it hits full force. Small hits stay subtle; big hits are violent.
• Smooth noise. Instead of randf() each frame, the camera samples a FastNoiseLite texture along a moving axis. Consecutive frames are correlated — the camera swings, not twitches.

The result scales naturally: a bullet hit adds 0.2 trauma, an explosion adds 0.7, a screen-clearing bomb adds 1.0. Each event earns its own drama.

The Recipe

Parameters table

How much trauma to add per event

The Code

Attach this script to your Camera2D node. It needs a FastNoiseLite resource (created at runtime) and nothing else — no additional nodes required.

# TraumaCamera2D.gd
# Attach to a Camera2D node.
# Call add_trauma(amount) from anywhere in your code on impact.

extends Camera2D

## How fast trauma decays per second (0 = never, 2.5 = very quick).
@export var decay: float = 0.8

## Maximum pixel displacement at full trauma.
@export var max_offset: Vector2 = Vector2(80.0, 60.0)

## Maximum rotation at full trauma (~4.5 degrees). Keep below 0.15.
@export var max_roll: float = 0.08

## Exponent applied to trauma before displacing. 2 = quadratic, 3 = cubic.
@export_range(2, 3, 1) var trauma_power: int = 2

# Current trauma value, 0.0 (calm) to 1.0 (full shake).
var trauma: float = 0.0

# Noise position advances each frame to get a continuous wobble.
var _noise_t: float = 0.0

@onready var _noise: FastNoiseLite = _make_noise()


func _make_noise() -> FastNoiseLite:
    var n := FastNoiseLite.new()
    n.noise_type = FastNoiseLite.TYPE_SIMPLEX_SMOOTH
    n.seed = randi()
    n.frequency = 0.5
    return n


## Call this on every impact. Amount is 0.0–1.0.
## Values stack: calling twice with 0.3 results in 0.6 trauma (capped at 1.0).
func add_trauma(amount: float) -> void:
    trauma = minf(trauma + amount, 1.0)


func _process(delta: float) -> void:
    if trauma <= 0.0:
        return

    # Decay trauma linearly over time.
    trauma = maxf(trauma - decay * delta, 0.0)

    # Raise to power so small trauma stays subtle.
    var t: float = pow(trauma, trauma_power)

    # Advance noise position (speed is arbitrary; 50 gives a nice pace).
    _noise_t += delta * 50.0

    # Sample three independent noise channels for x, y, and rotation.
    # Multiplying the seed offsets ensures channels are uncorrelated.
    rotation    = max_roll    * t * _noise.get_noise_2d(0.0,          _noise_t)
    offset.x    = max_offset.x * t * _noise.get_noise_2d(1000.0,       _noise_t)
    offset.y    = max_offset.y * t * _noise.get_noise_2d(2000.0,       _noise_t)

    # Reset when fully decayed.
    if trauma <= 0.0:
        offset   = Vector2.ZERO
        rotation = 0.0

Where to put it

1. Select your Camera2D node in the scene tree.
2. Click Attach Script and paste the code above (or save it as TraumaCamera2D.gd).
3. That's it — no autoload, no singleton required.

Triggering shake from other scripts

Export a reference or use a group to reach the camera:

# Option A: direct reference (simplest)
@onready var camera: TraumaCamera2D = $Camera2D

func _on_enemy_hit() -> void:
    camera.add_trauma(0.25)

# Option B: via group (useful when the camera lives in a different scene)
# In _ready(): add_to_group("trauma_camera")
# From anywhere:
func _on_explosion() -> void:
    for cam in get_tree().get_nodes_in_group("trauma_camera"):
        cam.add_trauma(0.7)

Tuning Tips & Common Mistakes

Start smaller than you think. Playtest with add_trauma(0.2) for a standard hit before reaching for 0.5. Players sitting close to screens are more sensitive than you are during development.

Tune decay, not max_offset. The duration of the shake matters more than the distance. A 0.3-trauma hit that lingers 0.8 seconds feels heavier than one that pops to 50 px and vanishes in 2 frames.

Cap rotation aggressively. max_roll = 0.08 (about 4.5°) is the sweet spot for most 2D games. Go above 0.15 and players start to feel motion-sick, especially on mobile.

Don't add trauma every frame for continuous effects. A flamethrower calling add_trauma(0.3) at 60 FPS locks the camera at 1.0 forever. Use add_trauma(0.3 * delta) for sustained effects so trauma accumulates at a controlled rate per second.

Reset offset when trauma hits zero. The code above already does this. Forgetting it leaves the camera permanently displaced by whatever noise value it landed on when trauma ran out.

Physics-interpolated cameras need extra care. If your project uses ProjectSettings → Physics → 3D → Run Physics in Thread or physics interpolation, offset the shake after interpolation runs. A common fix is to set position_smoothing_enabled = false on the shake camera and handle following manually — check the Godot forum thread on this topic for details.

Famous Examples

Nuclear Throne (Vlambeer, 2015) — Every gun has a distinct shake signature: the pistol nudges, the shotgun bucks, the laser rifle vibrates. Nijman's INDIGO 2013 talk (YouTube) walks through the exact moment screen shake was added to the prototype and the immediate "oh, that's it" reaction it produced. The core idea of intensity proportional to weapon weight maps directly to the trauma table above.

Celeste (Maddy Thorson & Noel Berry, 2018) — Uses extremely restrained shake. Dashing barely moves the camera; death is the only action with a large shake. This deliberate understatement keeps the game readable at high speed — when the shake arrives, it means something. The GDC 2017 level design talk (GDC Vault) touches on how every feedback element was kept minimal to serve precision platforming.

Hollow Knight (Team Cherry, 2017) — The nail clashes and parries use a brief, sharp shake paired with a freeze frame (hit-stop). The combination is what makes hits land: the freeze holds the frame at the moment of impact, then the shake announces the collision result. If you are building an action game, screen shake and hit-stop belong together.

FAQ