Watch enough co-op playtests and the same hesitation repeats. A player drops, a teammate picks them up, the revive sound fires. The revived player then spends another second and a half sitting on the respawn screen, or stands still with the camera aimed at the floor, because the cue told them they had gained something. It never told them they could move.
The asset probably tested well on its own. A bright rising figure with a shimmer on top, expensive-sounding in the browser. In the game it shared its first interval, its contour and its brightness with the level-up stinger, and the ear filed it under reward. Rewards are things you stop to admire. State changes are things you act on.
A revive has under a second to say “the fight is back on”. The rest of this article is about spending that second.
A Revive Is a State Flip, Not a Gain
The usual mistake is treating revive as a large heal. They are not the same kind of event. A heal pickup patches a number while the player stays inside the same fight: same body, same position, same threat, just more margin. A revive changes whether the player is in the fight at all. It sits closer to a spawn than to a pickup, and it is almost never the player's own decision.
That difference has to appear in the vocabulary. Heal cues tend to be short, round and warm, with a small upward step that resolves quickly, because they repeat constantly and must never sit on top of the mix. Scale that shape up for a revive and players read a large heal; they keep waiting for the actual resurrection. The small version's timing is covered in health pickup cue design, and the revive should deliberately diverge from it rather than occupy the loud end of the same family.
Direction is the part worth keeping. Restoration rises and damage falls, which is why the same upward motion can survive in both a heal and a revive while everything else changes. The pairing logic behind that is laid out in why healing needs opposite cues to damage. What a revive adds is a landing: something has to arrive, not just climb.
The Ally Layer
A revive is also social. Someone else did something to you, and in a firefight the sound is the only confirmation of it. Two voices carry that better than one: a stable low element for the player's own state, and a second element slightly apart from it, six to ten cents sharp or a fifth above with a slower attack. It does not need to be musical. It needs to be plural. A single clean tone, however well tuned, sounds like the game talking. Two tones sound like another player doing something on your behalf.
The distinctions in party heal vs single heal are about how many listeners a cue addresses. A revive addresses one player, but it always implies two participants.
Spending the Second: Three Windows
Treat the cue as three consecutive windows rather than one gesture. The values below are a starting point for a fast action game, not a specification. A slower game can stretch every window and still work, as long as the proportions hold and the total stays under a second.
- 0–50 ms: impact. A noise transient high-passed around 1.2 kHz, eight to fifteen milliseconds long, with a pitched body starting on the same frame. Do not let it fade in. Check the generator's default ramp first — five milliseconds of anti-click fade is enough to remove the edge this window exists to provide.
- 50–400 ms: the rising gesture. Pitch climbs from a stable low note to a target a fifth or an octave up, so 220 Hz to 330 Hz, or 300 Hz to 450 Hz in a brighter mix. Keep it continuous across 250 to 350 ms instead of stepping it in notes. This is the longest window and it carries the meaning: up reads as returning.
- 400–900 ms: confirmation and tail. The rise lands on a stable pitch, holds for 80 to 120 ms, then releases exponentially over 200 to 300 ms. The landing is the part that says “you have control”. Close the file by 900 ms. A longer tail will still be ringing when the player fires the first shot back.
Trigger the impact on the frame the revive state flips, not the frame the animation peaks. In Unreal that is usually the notify that sets the state rather than the visual beat; in Unity, the call that flips the revived flag. Deriving it from an animation end notify can slide it by 100 to 200 ms after a blend or a network correction, which is a large error inside that budget.
Two Stages Beat One Long Swell
Most first drafts are a single swell: one sound that grows louder and brighter for most of a second and then stops. It feels dramatic in isolation and fails in play, for a mechanical reason. A swell has one edge, at the start, and no second edge at the end. The ear hears that something is happening and keeps waiting for the sentence to finish.
Two stages give the ear two answers. The impact and the front of the rise answer “something is happening to me”. The landing answers “and now I can act”. The player's decision — sprint, reload, get behind cover — happens at the second answer, so that is the edge the cue has to place accurately.
In practice, two stages means two envelopes, not one long ADSR.
Build them as separate events and post them independently: a
start event on the state flip and a confirmation event on control
return. Two PostEvent calls in Wwise, two
EventInstance objects started at different times in
FMOD, or AudioSettings.dspTime with
PlayScheduled in Unity. Separate events also let the
confirmation move when revive durations change, without
re-rendering anything.
Peak Placement
If the peak sits at 800 ms, the cue is still climbing when the player regains control, and the ear keeps following it instead of the room. Aim for the impact to be the loudest single moment and the landing to be the most resolved.
Surviving Combat Noise
A revive plays in the worst mix the game has. Teammates are firing, the downed player's screen is red, the music has moved to its combat layer. A cue that works in the editor at minus six will vanish here unless it owns a band nothing else needs.
Explosions and heavy impacts live below 200 Hz. Gunfire transients are broadband, but the crack that carries them sits high, often between 1 and 4 kHz. Put the revive's identity in the 500 Hz to 1.5 kHz region, with a harmonic layer at 2 to 3 kHz that only has to survive the impact window. Low-end weight is support, not message; on laptop and phone speakers it is not there at all.
Ducking helps more than level. Sidechain the music and ambience by
three to six dB for the length of the cue and leave gunfire
untouched — ducking the shot that is killing your teammate is the
wrong trade. In Wwise that is a sidechain on the music bus driven
by the revive bus; in FMOD, a duck on the music bus with a 10 to
20 ms attack and 300 to 400 ms release; in Unity, a
Duck Volume effect on the music mixer group.
Play it 2D. A revive is information about the player's own state, and panning it to a body that may be off-screen adds nothing but confusion. Cap the instance count as well: two revives inside the same second should not sum into a louder copy of one sound. Vary the second by a couple of semitones, or let the first finish.
Three Questions Before You Ship
One: mute the screen and listen. Play the cue with no visuals and no context. Does it say “you are back”, or does it say “you got a thing”? If it is the second, the problem is contour and timbre, and no amount of level will move it.
Two: find the control-return edge. Have someone listen to the cue in a loop and press a key the instant they believe they can move. If they consistently press early, the landing arrives late; if they press late, it arrives early or gets buried. A spread of more than about 150 ms means the confirmation is not doing its job.
Three: play it inside the fight. Full mix, music on, gunfire on, phone speaker at half volume. The impact and the landing should both survive. If you have to lower the music to hear the cue, it is not competing in the band that matters.
When all three pass, stop. A revive cue is not a moment players are meant to enjoy; it is a sentence the game says once, quickly, and then gets out of the way of the next fight.