CameraIntermediate

Slow Motion

Briefly dropping the game's time scale to stretch out a dramatic moment.

impactcombatjuicetime

Examples

Captured from this page's own interactive demo below.

Overview

Slow motion reduces the game's overall time scale for a short window — a finishing blow, a narrow dodge, a big explosion — stretching an instant into something the player has time to actually perceive and enjoy.

It works because it directly manipulates the pacing information the player's perception relies on: slowing everything down (uniformly, so it doesn't feel like lag) tells the brain 'this moment matters, look closer.'

Unlike hit stop (a near-instant full freeze), slow motion holds a partial time scale over a longer window, so it reads as cinematic and dramatic rather than as a sharp punctuation mark.

Interactive Demo

Time Scale0.3

Duration600ms

Use Cases

CombatFPSFighting gamesCinematic finishers

Best Practices

Do

✓Ease into and out of the slowed time scale over a few frames rather than snapping — a hard cut reads as a hitch.
✓Keep player input responsive (even if slowed) rather than locking it out entirely, unless the moment is meant to be a cutscene beat.
✓Reserve it for genuinely rare, significant moments — overuse flattens its impact fast.

Don't

✕Don't scale UI timers, countdowns, or real-time systems (like network sync) with the same time scale used for gameplay slow-mo.
✕Don't stack multiple overlapping slow-motion triggers without resolving to a single target time scale.
✕Don't forget to restore audio pitch/rate handling — naive time-scaling can make sound stutter or pitch-shift unpleasantly.

Common Mistakes

⚠Changing `Time.timeScale` without also adjusting `Time.fixedDeltaTime`, causing physics to feel wrong during the slow-mo window.
⚠Leaving the slow-motion state stuck active if the triggering object is destroyed mid-effect.
⚠Using it as a substitute for hit stop on every hit — they serve different moments and durations.

Implementation

Paste this into your AI assistant (Cursor, Copilot, Claude) to add the effect to your project.

Prompt

Add the "Slow Motion" game-feel effect to my project: Briefly dropping the game's time scale to stretch out a dramatic moment.

How it works: Slow motion reduces the game's overall time scale for a short window — a finishing blow, a narrow dodge, a big explosion — stretching an instant into something the player has time to actually perceive and enjoy.

Guidelines:
- Ease into and out of the slowed time scale over a few frames rather than snapping — a hard cut reads as a hitch.
- Keep player input responsive (even if slowed) rather than locking it out entirely, unless the moment is meant to be a cutscene beat.
- Reserve it for genuinely rare, significant moments — overuse flattens its impact fast.

Avoid:
- Don't scale UI timers, countdowns, or real-time systems (like network sync) with the same time scale used for gameplay slow-mo.
- Don't stack multiple overlapping slow-motion triggers without resolving to a single target time scale.
- Don't forget to restore audio pitch/rate handling — naive time-scaling can make sound stutter or pitch-shift unpleasantly.

Implement the effect in whatever engine/stack the project already uses and follow its existing code style. Wire it up where it makes sense.