Loop a health pickup cue for the full duration of a heal over time and the trick holds for four repetitions. By the eighth, the ear has filed the sound as ambience. By the twentieth, it is a texture nobody parses as recovery, and when it stops there is no event to hear, only the removal of a sound. The player has no signal that the heal finished.
The unit was wrong from the start. A pickup is an event: it happens, it resolves, it gets out of the way. Heal over time is a state, and eight seconds is long enough for the ear to prove it needs a different vocabulary.
The decomposition that works is three parts with three envelopes: an entry that announces the state, a bed that maintains it, and an exit that closes it. Most engines can play all three from one event or one AudioSource cluster, and each part answers a different question.
Entry, Bed and Exit Are Three Different Jobs
The Entry Says Recovery Started
The entry is a one-shot of roughly 150 to 250 milliseconds, front-loaded the way any game cue has to be. It fires before the player looks away from the enemy. A 5 to 10 ms attack with most of its energy between 1 and 3 kHz survives gunfire and footsteps, which is where an entry usually dies.
Do not reuse the pickup cue. A pickup says you gained something now. The entry says something is working on you. Those are different promises, and a player who hears the second as the first will stop dodging because the heal seems complete. A short two-note rise, or a filtered noise sweep that settles on a stable pitch, reads as a process rather than a payout.
The Bed Says It Is Still Running
The bed is the state itself: a continuous layer that lasts as long as the effect does. It carries presence, not information. No strong transient, no rhythmic content, no melody that wants to resolve. A clear pulse in the bed competes with the tick and forces the player to decide which one counts.
Place it around -18 dBFS to -12 dBFS under the entry and high-pass it at 250 to 400 Hz so it stays clear of explosions and music. A slow shimmer, a filtered noise layer, a quiet pad all work. A 400 ms cue on repeat is not a bed, it is a metronome.
The Exit Says It Is Over
The exit is its own cue of 120 to 300 milliseconds, sent when the effect ends. It resolves, then the mix goes quiet. This is the part most projects skip, and it tells the player they can commit to the next action without checking the health bar.
Tick Period Reads as Urgency Whether You Chose It or Not
Between entry and exit sits the tick, the short sound at each heal increment. It is a small sound with a large side effect, because period carries emotional weight even when nobody designed it to.
- 2000 ms: patient. Reads as ambient detail. Fits long buffs and out-of-combat regen, though the ticks can feel disconnected from the heal they represent.
- 1000 ms: steady. The default starting point for in-combat recovery. It is frequent enough to confirm progress and slow enough to stay out of the way.
- 500 ms: active. Fits short bursts of three to five seconds. It begins to read as urgency, which is fine if the effect is urgent and wrong if it is not.
- 250 ms: alarm. Almost always reads as a warning. Use it only for very short effects, and check it against the low-health cue before shipping.
Two rules keep the period honest. Tick period is not the heal rate: a game can restore health continuously and still tick once per second. And do not shorten the period as the effect nears its end or as health drops — a faster tick reads as danger, not completion. To signal that a heal is almost done, lift the bed with a filter opening and leave the tick alone.
Keep each tick between 30 and 80 ms. A tick with a 200 ms tail smears into the next one at a 500 ms period and turns the effect into a drone. Give it a different note from the entry so the two stay distinct. The repetition problem is covered in designing regeneration tick sounds .
Crossfade the Loop; Do Not Retrigger It
If the bed loops, the loop point is where the design gets exposed. Retriggering a one-shot every N milliseconds gives a transient at every repetition and a gap or overlap at the seam whose length depends on frame timing. A 400 ms cue looped for eight seconds produces twenty seams, and listeners hear the rhythm.
The fix is a crossfaded loop. Two copies of the bed, offset in time, with equal-power fades of 150 to 300 ms at the join: while A fades out, B is already at full level, so the seam never reaches zero. Unity usually means two AudioSources with volume ramps; FMOD a loop region with a transition marker; Wwise a looping container with a crossfade at the loop point. The mechanism changes, the requirement does not: no amplitude dip and no doubled transient at the join.
A retriggered one-shot is still correct for the entry, the exit and the tick. Those are events. The bed is the only part that should loop, and even then it should be crossfaded. The same reasoning about intended mode applies to loop versus one-shot playback .
The Bed Ducks; the Tick Does Not
Eight seconds is long enough for a static layer to bury the mix or disappear inside it. Ducking fixes the first half. Route the bed to a group sidechained to the combat bus: 20 to 50 ms attack, 4 to 6 dB reduction, 200 to 400 ms release. Explosions push it down, and it returns between them.
Duck the bed, not the tick. The tick is information and should hold its level; if the sidechain drops it whenever an explosion lands, the confirmation becomes unreliable exactly when it matters. Split the routing: bed to the ducked group, tick to an unducked one.
Two cautions. Do not duck to silence: a bed at -40 dB through a fight removes the sense that recovery is ongoing. And do not let the tick trigger the duck; a one-second tick sidechaining the bed produces a breathing rhythm that reads as a pulse. The routing side is laid out in ducking the mix .
Frequency planning helps more than level. Keep the bed above 250 Hz, put most of the tick between 1 and 4 kHz, and give the entry a transient in the same band with a wider body. Then the three parts coexist when they stack instead of masking each other.
The Exit Teaches the Grammar
End the effect with a release, not a fade. A bed that fades out over two seconds says nothing: the player cannot tell whether recovery completed, was canceled by damage, or ended because health reached full. A 120 to 300 ms exit gesture — a short upward interval, a filter that opens and closes, a soft chime that shares a note with the entry — says done.
The exit also has to fire when the effect ends early. If the player reaches full health at second three of an eight-second heal, play the exit then. Do not let the bed simply stop, because the cue that marks the end of the state is the point.
Three end states are worth separating when the game supports them: completed, which gets the full exit; canceled, which gets a shorter and duller version that says it stopped without saying it finished; and expired, which gets the most neutral version. One fade for all three teaches players that the sound means nothing.
A short room or plate on the exit is fine at 0.3 to 0.6 seconds, but the gesture has to finish before the next hit or it will be heard as part of the fight. The tradeoff is covered in how the tail shapes recovery .
What the Player Should Learn to Expect
Once the three parts exist, the effect stops being a sound and becomes a grammar. Rising entry: recovery started, keep moving. Continuous low bed: still running. Soft tick: a chunk landed. Resolving exit: finished, commit. A player who has heard it reads all four without looking at the health bar.
That grammar works only if it is consistent. A potion, a regen aura, a lifesteal weapon, a campfire — each can have its own timbre and bed, but the entry and the exit should share a family: same pitch direction, same rough envelope, same region of the spectrum. When every heal source invents its own vocabulary, players relearn the meaning each time.
Test it the way dialogue gets tested. Play a fight with the HUD hidden and ask whether you can tell, from sound alone, that recovery started, that it is still running, and that it stopped. If the answer depends on the health bar, the loop is doing work the language should be doing.