Applied The Lora Playbook

The Sound and VFX Lab

Last reviewed

Intermediate

What you'll learn

~55 min
  • Add particle systems for blood splatter, dust, and energy trails using Phaser's built-in emitters
  • Implement screen shake, hit flash, and camera zoom punch for combat impact
  • Build a sound trigger system that plays effects on attack, hit, dodge, and ambient events
  • Understand why 'game juice' transforms a tech demo into something that feels like a real game

What you’re building

Play the Combat Loop Prototype with the sound off and your eyes half-closed. The mechanics work. The combo chains. The dodge has i-frames. But it feels flat. Thin. Like watching a fight scene with the audio muted and the camera locked to a tripod. Something is missing, and that something is juice.

“Juice” is the game design term for the feedback layer that makes interactions feel impactful. Screen shake when the boss slams the ground. A burst of red particles when a blade connects. A white flash on the enemy sprite at the instant of damage. A subtle camera zoom on a finisher. The whoosh of a dodge roll. The thud of a hit landing. None of these change the mechanics. All of them change how the game feels. And feel is what separates a prototype that people play once from one that people cannot put down.

In this lesson you are building a VFX and sound lab — a Phaser 3 scene that layers particles, screen effects, and sound triggers on top of a combat room. Every effect is configurable with sliders so you can dial in exactly how much juice is right for your BloodRayne remake.

💬This is the lesson where it stops feeling like code

Everything up to now has been systems — health bars, state machines, physics tuning. This lesson is where the game starts to feel like a game. The first time you land a three-hit combo and see blood particles scatter while the screen shakes and a slash sound plays, you will understand why game developers call this the fun part. Because it is.


The showcase

Here is what the finished lab gives you:

  • Combat room with a player (Rayne) and two enemies (grunt + ranged), fully playable
  • Particle systems:
    • Blood splatter on enemy hit (red particles scatter from impact point)
    • Dust puff on landing after a jump (brown-gray particles spread at feet)
    • Energy trail on dodge roll (purple-red particles trail behind player)
    • Death explosion on enemy kill (large burst of red particles)
  • Screen effects:
    • Screen shake on player damage (short, intense)
    • Screen shake on boss attacks (long, heavy)
    • Camera flash (red tint overlay) on player hit
    • Camera zoom punch on combo finisher (quick zoom in then snap back)
    • Hit-stop (50ms game freeze) on heavy attacks and kills
  • Sprite effects:
    • White flash on damaged enemy (tint white for 80ms then restore)
    • Red tint pulse on player damage
    • Afterimage on dodge (semi-transparent copy at start position, fades out)
    • Scale bounce on combo hits (enemy squishes slightly on impact)
  • Sound triggers (Web Audio API with generated tones, no external files):
    • Attack whoosh (filtered noise burst, different pitch per combo hit)
    • Hit thud (low frequency impact sound)
    • Dodge swoosh (quick high-to-low sweep)
    • Enemy death crunch (layered low + high impact)
    • Ambient low drone (continuous, very quiet)
  • Tuning panel with sliders for every effect: particle count, shake intensity, flash duration, zoom amount, sound volume

Before you start

If your AI tool is open from the previous lesson, leave it (/exit, or Ctrl+D in Antigravity) so you are back at your terminal prompt. Create a folder for this lab and step into it:

Terminal window
mkdir -p ~/retro-remake/13-sound-vfx-lab && cd ~/retro-remake/13-sound-vfx-lab

In Windows PowerShell, run mkdir ~/retro-remake/13-sound-vfx-lab; cd ~/retro-remake/13-sound-vfx-lab. In a desktop agent app, open ~/retro-remake/13-sound-vfx-lab as your workspace folder. Then start your AI tool the way Workbench Setup showed.

Switch to plan mode

Switch into Plan mode (Shift+Tab, /plan, or the mode picker) so your agent aligns on the particle emitters, camera punch, hit-stop, and Web Audio synthesizer before writing index.html.

The conversation

Each message below is an example. Say it in your own words.

Say what you want

Ask for a browser-based sound and VFX lab layered over a playable combat room:

Build a browser-based sound and VFX lab that adds particles, screen shake, hit-stop, and synthesized sound effects to a playable combat room with live tuning sliders. Ask me what you need first.

Answer its questions

Your agent will ask about the combat setup, particle effects, camera and sprite feedback, audio generation, and tuning controls:

If it asksYou might say
What combat setup should the room include?Rayne with a 3-hit combo and dodge roll fighting one melee grunt and one ranged soldier that respawn.
Which particle effects do you want?Blood splatter on hit, dust puffs on landing, an energy trail during dodge, and a 360-degree death burst.
What screen and sprite feedback should trigger?Camera shake, red damage flash, zoom punch and hit-stop on heavy hits or kills, white hit flash, and impact squash.
How should sound work without external audio files?Synthesize attack whooshes, hit thuds, dodge sweeps, death crunches, and a toggleable low ambient drone right in the browser.
What controls belong in the tuning panel?Sliders for particles, screen effects, sprite effects, and volume, plus Kill All Juice, Max Juice, and Balanced buttons.

Read the plan

Before approving the build, check the agent’s plan for these four details:

  1. Phaser 3.60+ particle API (in a single index.html file): creates a small generated square texture first, then calls this.add.particles(x, y, textureKey, config) (which returns the emitter directly in Phaser 3.90.0) for blood splatter, landing dust, dodge energy trails, and death bursts.
  2. Screen and sprite impact layer: implements camera shake, red damage overlay, 1.1x camera zoom punch on Hit 3 and kills, brief physics/tween pause for hit-stop (30ms on Hit 3, 60ms on kill), solid white hit flash (setFillStyle(0xFFFFFF) on rectangles or setTintFill(0xFFFFFF) on sprites), dodge afterimages, and impact squash-and-stretch.
  3. Lazy Web Audio synthesis: creates AudioContext on the first user click or keypress and synthesizes pitch-descending bandpass noise whooshes across the 3-hit combo, a 60Hz hit thud, an 800-to-200Hz dodge sweep, a layered death crunch, and a quiet 55Hz ambient drone.
  4. Juice comparison presets: the right-hand sidebar wires sliders to window.vfxConfig and includes “Kill All Juice” (sets all feedback to 0/off so you can feel the contrast), “Max Juice”, and “Balanced”.

If the plan uses the old Phaser 3.55 createEmitter API or creates the AudioContext on page load before the player interacts, steer it before approving:

Make sure particle bursts and trails use the current Phaser 3 emitter setup, and wait until my first click or keypress before starting browser audio.

Once the plan covers all four checks, approve it and let your agent build index.html. After testing “Kill All Juice” versus “Balanced” in your browser, ask your agent to save a Git checkpoint.

💡Zero external audio files

The sound system uses the browser’s Web Audio API to synthesize procedural sounds from oscillators and noise buffers. That means the entire lab, including audio, runs from a single HTML file while proving where every sound cue belongs.


What you get

After the AI finishes, the project folder structure looks like this:

13-sound-vfx-lab/
index.html

Play it

Ask your agent to open the sound and VFX lab in your browser:

Open the sound and VFX lab in my browser so I can test the combat feedback and juice presets.

Or open it from a terminal:

Terminal window
cd ~/retro-remake/13-sound-vfx-lab
open index.html # macOS (Linux: xdg-open index.html; WSL: explorer.exe . then double-click index.html)

Click anywhere on the game canvas first (this initializes the audio context — browser policy requires a user interaction before sound can play). Then start fighting. Hit the grunt with a three-hit combo. Watch the blood particles scatter, feel the screen shake on the heavy cleave, hear the whoosh deepen with each successive hit. Dodge through the ranged soldier’s projectile and hear the swoosh. Kill an enemy and feel the hit-stop freeze followed by the death burst.

Now click “Kill All Juice.” Fight the same enemies. Notice how hollow it feels. Every hit is silent, every death is quiet, every dodge is invisible. That flatness is what your combat prototype sounded like 30 minutes ago. Click “Balanced” to restore effects and feel the difference wash back in.

That difference is juice.

If something is off

ProblemFollow-up prompt
No sound plays at allNo sound effects play during combat. Start the browser audio system on my first click or keypress on the page, and make sure every attack, hit, dodge, and death sound checks that audio is ready before playing.
Particles don’t appearNo particles show up when I attack, land, dodge, or defeat an enemy. Fix the particle emitters so hits burst blood splatter, landings puff dust, dodges leave an energy trail, and kills trigger a 360-degree explosion.
Screen shake is too violentThe screen shake is way too intense and throws the whole room off screen. Tone down the camera shake intensity range so even the highest slider setting feels like a punchy tremor, not an earthquake.
Hit-stop freezes the game permanentlyWhen a heavy hit or enemy kill triggers hit-stop, the game freezes and never unfreezes. Make sure the brief impact pause always resumes movement and animations after 30 to 60 milliseconds.

Deep dive

Particles are communication, not decoration

Every particle effect in this lab serves a purpose. Blood splatter confirms your attack connected — without it, the player has to look at the health bar to know they dealt damage. Dust on landing grounds the character in the world — without it, jumping feels like the character is disconnected from the floor. The death burst is a reward — killing an enemy should feel good, and a shower of particles is your brain’s receipt that something meaningful happened.

Hit-stop is the most powerful tool in the box

Hit-stop (also called hit-freeze or hit-stun) is a 30-60 millisecond pause on impact. It is nearly imperceptible consciously, but it makes every hit feel like it has weight. Without hit-stop, a sword slash passes through an enemy at 60fps — one frame the blade is here, the next it has passed through. With hit-stop, the game freezes at the moment of impact. Your brain registers the collision. The attack feels like it HIT something rather than phased through it. Fighting and action games have used it for decades.

Sound validates what your eyes see

The attack whoosh tells your brain the slash happened even before the particles appear. The hit thud confirms contact. The dodge swoosh tells you the i-frames are active. Players in noise-canceling headphones will feel the sound effects physically. A sound cue that lands with the hit makes the particle effect read as more impactful, and game audio designers lean on that pairing constantly.

🔍Why procedural audio for a prototypeclick to expand

Professional games use recorded and mastered audio files. You are using oscillators and noise buffers. That is fine. At the prototype stage, the question is not “does this sound good?” but “does having sound here make the game feel better?” The answer is always yes. Even a synthesized thud at 60Hz makes a hit feel more impactful than silence. When you move to production, you will replace these procedural sounds with real recordings. But you will know exactly where every sound trigger goes, what frequency range it needs, and how loud it should be — because you already tuned all of that in this lab.


Customize it

Add a combo hit counter with escalating juice

Add a floating x1, x2, x3 combo counter near the player that fades after 1 second without a hit, plus a Combo Escalation slider (1.0 to 3.0) that scales particles, shake, zoom punch, and hit-stop.

Add a slow-motion kill cam

When the last living enemy dies, trigger a 1.5-second slow-motion kill cam at 0.3x speed with a 1.4x camera zoom on the kill point, plus a Kill Cam checkbox and Slow-Mo Speed slider.

Add environmental particles

Add ambient upward-drifting red ember motes across the arena and ground dust particles that scatter when the player runs past, with sliders for ember count (0 to 50) and dust density (0 to 30).

Try it yourself

  1. Walk through the plan-mode conversation above and open the lab in your browser.
  2. Fight both enemies with juice at default settings. Pay attention to the three-hit combo — does each hit feel progressively more powerful?
  3. Click “Kill All Juice” and fight again. Feel the difference. Write down three specific moments that felt worse without juice.
  4. Click “Max Juice” and fight. This is the opposite extreme — too much feedback can be disorienting. Find the line between “impactful” and “chaotic” by adjusting individual sliders.
  5. Mute your computer speakers and fight. Then unmute. Notice how much the synthesized sounds add.
  6. Find your personal “balanced” settings — the amount of juice that makes your BloodRayne prototype feel right. Export the tuning values (they are in the shared config object).

The mechanics were built in the Combat Loop Prototype, the Movement and Camera Feel Lab and the Enemy Behavior Sandbox. This lesson makes them sing. Rayne did not just fight — she fought with style. Now your game does too.


💡Your game has juice

Blood spatters when Rayne’s blade connects. The screen shakes when she takes damage. A whoosh accompanies every dodge. The enemy explodes in particles when it dies. These are not cosmetic upgrades — they are the layer that makes players lean forward in their chair. Next lesson: creating the visual identity that ties everything together.

intellimetrics · Arlington, VA
© 2026 intellimetrics.net
Search lessons