Game Audio

Horror Game Audio: Building One Enemy’s Complete Vocal Set

How to plan idle, locomotion, attack, hurt and death sounds — and variations — for a single horror enemy.

By ScreamBeast Team 8 min read

Horror Game Audio: Building One Enemy’s Complete Vocal Set

Horror game audio is more convincing when one enemy has a complete vocal set than when a project collects impressive, unrelated screams. Players notice when the same file loops, when an attack has no voice, or when a death cry belongs to a different creature than the idle breath they heard in the corridor.

This guide is for game developers working in Unity, Unreal Engine or Godot, and for anyone building audio for a horror game. It focuses on one enemy: which vocal actions to cover, how variations stop repetition, and how to connect those sounds to gameplay. It is not a survey of alien libraries, and it does not assume you need a particular species. The working example is a generic cellar stalker — a single presence the player can learn to recognize.

What does a complete horror enemy vocal set include?

Start with the actions your enemy actually performs, then record or select vocals that communicate those actions. A complete set is a vocabulary, not a folder of loud highlights.

Use the following roles as a practical baseline. Remove anything your encounter does not need, and add a role only if the player must understand that state by ear.

RoleWhat the player should understandWhat to listen for
Idle or breathThe enemy is present, waiting or watchingLow, sustainable material that can sit under tension without becoming a loop you immediately recognize
LocomotionThe enemy is moving, climbing or closing inEffort, weight and pacing — not necessarily footsteps
AttackA committed strike is starting or landingA wind-up, a lunge or a short bark that fits the animation
Hurt or hitThe player’s action landedAn interrupted, involuntary reaction that can fire more than once
DeathThe encounter has endedA distinct final performance that should not be mistaken for another hit

Two optional roles are often useful in horror and easy to overuse: an alert or detection call when the enemy notices the player, and a searching or frustrated sound when it loses them. Add those only if the game has those states. A decorative roar that does not map to an event is usually less valuable than a clearer hurt or death sound.

Keep vocals separate from Foley. Footsteps, cloth, body impacts, debris and door movement may belong in their own layers. A locomotion vocal is the creature’s effort, not a substitute for a footstep library.

How should you start with one enemy and one encounter?

Write a short behavioral brief before you record, design or buy anything. You do not need a full fictional biology — only a few rules the voice must obey so idle, attack and death still sound like the same being.

For a working example, imagine a stalker that lives in a cellar. It breathes through a damaged throat. When idle, that breath is wet and uneven, with long gaps. When it climbs a stair or drags itself forward, the same throat produces strained, rhythmic effort. The attack collapses that effort into a short, committed burst. A hit interrupts the burst. Death empties it — longer, less controlled, and clearly final.

That brief gives you tests you can apply to every file:

  1. If you hear only the idle breath, can you still imagine the attack?
  2. If you hear only the death, does it belong to the same throat as the breath?
  3. If two hurt sounds play in a row, do they feel like repeated injury or like a copied file?

Design the set around one representative encounter: the enemy waits, moves closer, attacks, takes damage and dies. If that sequence works with the lights down and the music lowered, you have a usable core. Additional enemies can reuse the method; they should not reuse the same identity unless you intend them to sound related.

Why do variations matter more than one perfect scream?

A single excellent attack sound becomes a problem as soon as the player hears it twice in a row. Horror depends on uncertainty. Exact repetition tells the ear that the threat is a sample, not a presence.

Variations are alternative performances of the same role, not random extra textures. A useful hurt variation still has to sound like a hit reaction from the same creature. If the alternative changes the size, age or species of the voice, it is a different asset, not a variation.

How many variations you need depends on how often the event can fire. Idle material that plays in long gaps can survive with fewer alternatives than a hit reaction in a struggle. There is no universal count that suits every project. A practical test is to play the encounter twice and notice whether any file announces itself immediately. If it does, that role needs another take, a longer pool, or a rule that prevents the last file from playing again.

Also decide what happens when events overlap. Should a new attack cut off the previous vocal, layer on top of it, or wait? Hurt sounds are frequent candidates for overlap problems. A short, clipped reaction is often easier to repeat than a long moan that stacks into a chord.

How do you keep the voice sounding like one creature?

Consistency comes from shared constraints, not from processing every file identically. The cellar stalker might keep a wet throat, a narrow midrange and an uneven pulse across every role, while still changing intensity, duration and articulation.

Three checks help before you call the identity stable:

  1. Compare roles at a similar listening level. An attack that is simply louder than the idle breath may sound like a different character until you match perceived loudness.
  2. Listen in order. Play idle, locomotion, attack, hurt and death as a sequence. Gaps in identity usually appear between roles, not inside a single impressive file.
  3. Test the busiest moment. Trigger movement, a hit and an attack close together. If the voice falls apart, the problem is often conflicting tails, not a missing scream.

If you are choosing a ready-made library rather than recording one, judge it the same way: can this one product cover the encounter, with enough alternatives for the repeated actions? Coverage and variation matter more than whether the loudest preview is memorable.

Listen to complete creature vocal sets

Some libraries are already organized as full action vocabularies rather than isolated highlights. The following demo reels are examples of complete creature sets — idle through death, with enough material to hear how a voice changes across actions. They are references for structure, not a requirement to put an alien, a monster or a zombie in your game.

Alien demo reel

Monster demo reel

Zombie demo reel

These previews include a light musical watermark. The WAV files you buy are clean.

If you are comparing packs, listen for whether each action is present and whether repeated actions have alternatives. A short game-jam checklist can still help when time is limited: warning, attack, hurt and death will carry a prototype farther than a single roar.

How do you hook the set to gameplay in Unity, Unreal and Godot?

Implementation details differ by engine, but the decisions are the same. Each vocal role needs a trigger, a small pool of files and a rule for overlap. Do the design work before you write the first hook.

A reliable pattern is to fire vocals from animation events rather than from a coarse state name alone. An “attacking” state may last longer than the vocal should. An event on the wind-up, the lunge or the impact lets you place the sound against a visible gesture. In Unity that often means an animation event; in Unreal Engine, an Anim Notify; in Godot, a method call or signal from the AnimationPlayer.

For variations, keep a small array or playlist per role and pick an entry that is not the one you just used. Random pitch or volume, used lightly, can help — but it will not hide a single file that the player has already memorized. Prefer another performance of the same action over heavy processing at runtime.

Write a short implementation sheet for the enemy: event, file or pool, trigger, overlap policy and a note from a playtest. This is especially useful when one person selects sounds and another connects them to animation. The sheet also makes it obvious when a role exists in the folder but has no trigger in the build.

Finally, test inside a representative mix. Horror music, room tone and player footsteps will mask quiet idle material and clash with long death tails. Judge the set in the encounter, not only in a file browser.

What should you check before you call the set finished?

Use this as a review pass, not as a claim that every horror enemy needs every item:

  1. Every action in the encounter has a vocal, or you have deliberately chosen silence for that action.
  2. Repeated actions have at least one alternative, or a rule that avoids immediate repeats.
  3. Idle, attack, hurt and death still sound like the same creature when played in order.
  4. Vocals and Foley are separate enough that you can adjust footsteps or impacts without breaking the voice.
  5. Overlap behavior is defined for attack and hurt.
  6. The packaged build includes the files, and a playtest on your target platform has heard them.
  7. If the sounds come from a third-party library, the license permits your intended use and any required credit is recorded.

Frequently asked questions

These questions usually appear after the roles are chosen and before the set is connected to animation.

Do I need footsteps in a voice set?

Not necessarily. A vocal set covers the creature’s voice and effort. Footsteps, scrapes and clothing movement are often easier to control as separate Foley, especially if the enemy moves across different surfaces.

How many variations does each action need?

Enough that a repeated encounter does not immediately expose the same file. Hurt and locomotion usually reveal repetition first. Add takes where the playtest makes the loop obvious, rather than aiming for a fixed number in advance.

Should an attack vocal line up with the wind-up or the impact?

Use the performance to decide. An effort sound can begin during the wind-up, while a short bark may belong nearer the strike. Test the vocal and any physical impact separately so each supports the action. One synchronization rule is unlikely to suit every animation.

What if I only have time for four cues?

Prioritize the sounds that explain the encounter: a warning or alert, an attack, a hurt reaction and a death. Idle breath and locomotion can wait if the player already understands that the enemy is there. Silence is clearer than a reused attack file playing in the wrong state.

Can one vocal set cover several enemy types?

It can if you intend those enemies to sound related — for example, weaker and stronger versions of the same presence. If the player should recognize different threats, give each threat its own constraints. Sharing a death cry across unrelated enemies usually flattens them.

ScreamBeast

Need creature sounds for your project?

Royalty-free creature sound effects packs, or your own voice turned into a monster in the Voice Studio.

Related articles