Guide

Game slow motion and time dilation systems explained

Harbor Ruins’ frost knight boss fired three ice shards in a tight spread that players could not dodge on reaction alone. Perfect parries felt identical to regular blocks — same animation, same SFX, no extra information. After a refactor, a successful perfect parry triggered a 0.35× time-scale window lasting 1.2 seconds of real time: projectiles hung mid-air, the knight’s recovery animation stretched into readable frames, and the riposte prompt glowed. Parry usage on that encounter rose from 8% to 41%; encounter clears improved without lowering damage. Slow motion did not make players stronger — it made the skill they already had legible.

Slow motion and time dilation are systems that reduce the simulation clock (globally or for selected actors) so players gain reaction time, tactical planning space, or cinematic emphasis. Unlike hitstop, which freezes a few frames on impact, slow-mo runs the world at reduced speed while preserving continuous motion. This guide covers time-scale architecture, trigger modes and meter economies, AI and physics tick behavior, input handling during dilation, presentation layers, multiplayer constraints, the Harbor Ruins refactor, a technique decision table, pitfalls, and a production checklist.

What slow motion and time dilation are

Every game loop advances simulation by deltaTime each frame. A time scale multiplier (timeScale) scales that delta: at 0.25×, one real second passes 0.25 simulated seconds for affected systems. Designers use dilation to:

Extend reaction windows — dodge a bullet spread, aim a headshot, select a spell.
Reward skill moments — perfect parry, flawless dodge, stealth takedown from cover.
Sell power fantasy — activated bullet time, super ability, kill cam.
Teach mechanics — first boss attack plays at 0.5× until the player parries once.

The design question is never “can we slow time?” (every engine can) but who slows, for how long, at what cost, and what still runs at full speed. Getting those four answers wrong produces either trivial combat (infinite bullet time) or a feature players forget exists.

Global vs localized time scale

Global slow-mo scales the entire simulation: physics, AI, animations, particles, audio pitch (usually via resampling). Superhot-style games invert this — time moves only when the player moves — which is global but input-gated. Global dilation is simplest to implement and easiest for players to read, but it pauses ambient life (NPC idle loops, UI timers) unless you exempt systems explicitly.

Localized dilation applies different scales per actor or layer:

Player-only — the hero animates at 1.0× while enemies and projectiles run at 0.3×. Creates strong power fantasy but can look uncanny if foot sliding is not compensated.
Enemy-only — stun states, finisher setups, or “focus” modes where the player plans while one target slows.
Volume triggers — a bubble around the player; entities entering the bubble adopt the reduced scale.
Category filters — slow projectiles and AI logic but keep camera shake, UI, and music at real time.

Most action games mix approaches: a global 0.4× scale during an activated bullet-time meter, but the player’s turn rate stays at 0.8× so aiming still feels responsive. Document which subsystems ignore timeScale in a central table — audio, haptics, network send rate, and cutscene timelines are the usual exceptions.

Trigger modes and meter economy

How slow-mo starts defines whether it feels earned or spammed:

Manual activation

Player holds a button to enter bullet time while a meter drains (Max Payne, Bayonetta Witch Time when dodging on beat). Tune drain rate, regen delay, and minimum activation threshold so one dodge refill cannot chain infinite slow-mo.

Automatic skill rewards

Perfect parry, flawless dodge, stealth kill, or headshot trigger a short unbidden dilation. Duration should match the action’s difficulty — a 0.8 s window for a parry, 0.3 s for a standard dodge — not a flat two seconds for everything.

Cinematic and scripted

Kill cams, finisher sequences, and story beats use authored time curves (ease-in to 0.1×, hold, ease-out). Keep player input scoped: allow aim adjustment but not movement, or vice versa, and signal invulnerability during the clip.

Conditional / environmental

Low health, slow-motion zones, or consumable “chrono” items. Pair with clear UI so players understand the ruleset is temporarily different.

Economy knobs: max meter capacity, drain per second, regen per successful action, cooldown after exit, and whether slow-mo stacks with other buffs. Cap total real-time spent below ~25% of a standard encounter or players will optimize around never playing at 1.0×.

Simulation behavior during dilation

Slowing animation without slowing logic produces bugs; slowing everything without adjusting feel produces mush. Key systems:

AI tick rate — decision trees and behavior trees should use scaled delta; otherwise enemies think at full speed while moving in molasses. Some games run AI at reduced frequency (every N dilated frames) to save CPU.
Projectiles and physics — velocity integration must multiply by timeScale. Hit detection windows widen in real time, which is the point — but multi-hit boxes may need per-frame caps to avoid double procs.
Player input — raw input is real-time; translate to simulated movement with an optional player bias (0.7× to 1.0×). Buffer windows for attacks often widen during slow-mo; document this so combat designers do not accidentally create infinite combo extensions.
Cooldowns and DoT ticks — decide whether ability cooldowns use real time or dilated time. Real-time cooldowns feel fair; dilated cooldowns extend CC chains and can break PvP.
Networking — authoritative servers must agree on time-scale state. Broadcast a TimeDilationStarted event with scale, duration, and affected entity IDs; clients interpolate. Never let client-only slow-mo affect hit validation.

Visual and audio presentation

Presentation sells the mechanic; without it, 0.3× scale feels like lag.

Post-processing — desaturation, increased contrast, vignette, chromatic aberration, motion blur tuned for low speed (avoid smear).
Particles — spawn rate scales with time; trails stretch to emphasize velocity even when slow.
Audio — pitch-shift SFX and music (0.5× pitch at 0.5× time is the naive default; many games use 0.7× pitch instead for clarity). Duck ambient noise; emphasize heartbeat or whoosh on entry.
UI — meter drain, remaining seconds, and target highlights (weak points, parry prompts) at full framerate even when world slows.
Camera — slight FOV narrowing and dolly-in on activation signal focus; pair with camera shake on exit for punctuation.

Offer an accessibility toggle: full slow-mo VFX, reduced VFX with same gameplay scale, or replace with high-contrast telegraphs and extended parry windows at 1.0× time.

Harbor Ruins frost knight refactor (worked example)

Before: perfect parry granted +20% damage on next hit only; no time change. Telemetry showed players blocked instead of parrying because the reward was invisible during the chaos of three-shard volleys.

After:

Perfect parry triggers global 0.35× scale for 1.2 s real time; regular parry stays at 1.0×.
Player turn and attack animation play at 0.85× within the window so riposte input remains snappy.
Ice shards get cyan outline + pulsing trajectory ribbon at dilated speed.
Riposte prompt appears at 0.4 s real time; successful riposte exits slow-mo immediately with 0.15 s hitstop on connect.
Meter-free on this boss — reward is per parry, max once every 4 s to prevent stunlock loops.
Audio: low-pass filter sweep on entry, normal pitch on exit snap.

Results: parry rate 8% to 41%, mean attempts per clear 4.2 to 2.7, no change to boss DPS ceiling. Players described the fight as “finally readable.”

Technique decision table

Approach	Best when	Skip when
Activated bullet time (meter)	Power fantasy shooters, tactical planning phases	Tight soulslike timing where pause breaks tension
Skill-triggered micro dilation	Reward parry/dodge mastery with readable windows	Skills are already trivial or spammable
Move-to-advance time (Superhot)	Puzzle-combat hybrid, turnless planning	Continuous movement core loop (racing, platforming)
Hitstop only	Impact feel, combo punctuation, fighting games	Player needs seconds of aim/plan time, not 3 frames
Full pause (menu / tactics)	Turn-based tactics, RPG command menus	Real-time action integrity is the product promise
Telegraph extension (no time scale)	Accessibility, simpler netcode	Cinematic power fantasy is a core sell

Common pitfalls

Infinite slow-mo loops — dodge refills meter faster than drain; cap regen per dilated second.
Player moves at full speed, world at 0.1× — breaks animation grounding; use 0.7× to 0.9× player bias instead of 1.0×.
AI thinks at full speed — enemies instantly counter during your bullet time; scale decision ticks.
Audio pitch unreadable — extreme pitch shift hides parry audio cues; keep critical SFX near normal pitch.
Stacking with hitstop — 0.3× scale plus 12-frame freeze feels like a bug; budget total real-time pause per exchange.
PvP asymmetry — one client in slow-mo sees different positions; only cosmetic dilation in competitive modes unless synchronized.
Scripted slow-mo on every kill — flow killer in horde modes; gate finisher cams on elites or player toggle.

Production checklist

Document global vs per-actor time scales and subsystem exemptions.
Define trigger types, durations in real seconds, and cooldowns per trigger.
Tune meter drain, regen, and minimum activation threshold on hardest encounter.
Verify AI, physics, projectiles, and DoT ticks use scaled delta consistently.
Set player input bias; widen input buffers explicitly if intended.
Pair activation with VFX, audio, and UI meter readable at a glance.
Cap total dilated real time per encounter to prevent degenerate strategies.
Test exit transitions for camera pops and animation snaps.
Implement accessibility preset (reduced VFX or telegraph-only mode).
For multiplayer, synchronize dilation state on server authority.

Key takeaways

Slow motion extends readable time — it rewards skill only if the trigger is earned and the presentation is obvious.
Harbor Ruins raised parry usage from 8% to 41% by pairing perfect parries with 0.35× scale and riposte telegraphs, not raw damage buffs.
Decide early which systems ignore timeScale — audio, UI, networking, and player turn rate are the usual split.
Micro dilation complements hitstop; it does not replace it — use hitstop for impact, slow-mo for planning.
Meter economies need hard caps; otherwise bullet time becomes the only way to play.