Modding guide

Sounds and effects

10 min readASA DevKit as of November 2026 (UE 5.8.1); ASE where noted

Your own sounds and particle effects go into ARK and play for the right players on a server. Importing is quick. The hard part is where a sound or effect plays. A dedicated server has no speakers and no screen, so nobody hears what it plays.

  • You'll make: a sound cue with sensible range, and sounds and effects that play for nearby players on a server
  • Time: under an hour for a sound; longer for an effect you build yourself
  • Level: intermediate (you've made an item or structure, and met replication)
  • You'll need: a mod set up, WAV files, and Works in PIE, not on a server close by

The process

  1. Import your sound as a WAV. Drag a 16-bit WAV into your mod folder. The kit makes a sound wave asset from it.

    Show me how
    • Vanilla creature sounds are 44,100 Hz WAVs. The Rex's roars are stereo.
    • Mono positions most predictably in the world. Stereo suits music and interface sounds.
    • Trim the silence at the start, or it plays late.
    • The wave and its cue must live in your mod folder. Modders found a cue reused from DLC content stays silent until it's copied into the mod folder.
  2. Wrap it in a sound cue. A sound cue is a small graph that plays waves with randomness, volume and range. Most ARK fields want a cue, and some take nothing else.

    Show me how

    Right-click the wave → Create Cue. Copy what the vanilla Rex roar cue does:

    Rex roar cue Setting
    three waves into a Random node, then a Modulator variety in which take and pitch
    Attenuation Settings: MediumHigh how far it carries
    Sound Class: Creatures which volume slider controls it
    Concurrency: Prevent New stops one creature stacking roars

    Sound cue or MetaSound? The 5.x kit has MetaSounds, Unreal's newer programmable sounds. Vanilla uses them rarely: 45 MetaSound sources against about 9,000 sound cues in the official content. Some ARK fields are typed as cues only, so a MetaSound won't go in: the weapon's Fire Sound, Equip Sound, Out Of Ammo Sound and Fire Projectile Sound, and the item's Use Item Sound. Fields typed as any sound, like Equip Sound on an item or the buff's sounds, take either. Cues are the safe choice: they fit every field.

  3. Give it an attenuation preset. Attenuation is how a sound fades with distance. Without it, the whole map hears it.

    Show me how

    ARK's presets are in /Game/PrimalEarth/Sound/Attenuation/, from Smallest to Highest. Distances are in centimeters; 100 is one meter.

    Preset Full volume within Fades out over Use for
    Small 1,000 3,400 small props, item use
    Medium 2,000 6,600 structures, most creature sounds
    High 3,000 17,000 big creatures, explosions
    Highest 7,000 28,000 boss roars, alarms

    All of them fade logarithmically and turn on occlusion, so walls muffle the sound. Pick the preset on the cue's Attenuation Settings, or on the component that plays it with Override Attenuation. Modders report the editor sometimes ignores attenuation, while the cooked game respects it. Test range in a cooked build.

  4. Play it where the players are. A sound plays only on the machine that plays it. Play it on each client, never only on the server.

    Show me how
    Where your logic runs How to make everyone nearby hear it
    an animation that plays on every client a Play Sound notify in the animation (step 5)
    the server (a hit, a timer, a use) a Multicast custom event, called by the server, with the sound as an input; or NetPlaySoundOnCharacter on a character
    an actor that replicates, like a buff its Begin Play runs on every client it reaches, so play it there
    one player's interface Play Sound 2D in the widget; it's local by nature
    • Random sounds: let the server pick, then pass the chosen sound in the multicast. If each client picks, each hears a different one.
    • Only for the owner: play it on the owning client. InventoryViewersPlayLocalSound plays to whoever has an inventory open.
    • Looping sounds: add an Audio component with Auto Activate off. Activate and deactivate it from a replicated variable with RepNotify, so players who arrive later hear it too.
    • Filter cosmetic work with Can Run Cosmetic Events (true where there's a screen) and Is Running on Server.
  5. For animations, use notifies. A notify fires at a frame of an animation, on every machine that plays it. ARK's creatures sound this way.

    Show me how
    • The Rex's bite animation has a Play Sound notify with its attack cue. Since the bite plays on every client, every client hears it, from the right place.
    • Add one in the animation editor: right-click a notify track → Add Notify → Play Sound, then set the cue.
    • Put the notify in the animation sequence or the montage the creature or player actually plays.
    • Modders recently reported cues on montage notifies and on consumables that played in the editor and single player, but not on a dedicated server. They moved the sound into a buff. I haven't reproduced it on 5.8.1.
  6. Pick Niagara for new effects. Niagara is Unreal's current particle system. Cascade, the old one, still works but has cook problems. Many ARK fields come in pairs, one for each.

    Show me how
    • The official content holds about 1,000 Niagara systems and 3,200 Cascade ones. The new content leans Niagara: the ASA folder has 108 Niagara systems to 19 Cascade, and Lost Colony 135 to 16.
    • Paired fields: the weapon's Muzzle FX and Niagara Muzzle FX, the instant weapon's Trail FX and Trail FX Niagara, a character's Hurt FX and Hurt FX Niagara. Fill the Niagara one.
    • Some fields take either kind (a container's Default Particle Template); a few older ones take Cascade only.
    • Effects that spawn and destroy themselves, such as a structure's Spawn Emitter and Destruction Emitter and an item's Use Particle Effect, point at a PrimalEmitterSpawnable actor. Make a child of a vanilla one and swap in your effect.
    • Cascade systems ported from ASE can fail the cook (Legacy particles). Modders were told they can keep a Cascade effect that works; rebuild it in Niagara when it breaks.
  7. Spawn effects on the clients. Effects follow the same rule as sounds. The server draws nothing.

    Show me how
    • Attached to something: add a Niagara component to the actor, Auto Activate off, and activate it from a RepNotify or a multicast. Or call Spawn System Attached on each client.
    • At a point, once: Spawn System at Location inside a multicast called by the server.
    • On a buff: modders report a buff handles the first particle component it finds, as it did with Cascade, so a Niagara component on the buff shows and dies with it. Others add their own activate and deactivate logic in a shared parent buff.
    • Owner-only buffs never reach other players, so neither does their effect (buff page).
    • GPU emitters need Fixed Bounds. The engine can't measure GPU particles, so without bounds the effect pops out of view at the wrong moments. Set them on the system.
    • Effect Types (a Niagara asset you assign to the system) set distance culling and how many copies may play. Give effects that run on many creatures or structures one, so far-away copies stop.
    • Keep sprites few and small. Each see-through sprite redraws the pixels behind it, so stacked sprites cost the most. Where a hard edge is fine, a masked material skips that cost.
  8. Test on a local dedicated server with a second client. PIE plays sounds where a server wouldn't (Testing your mod).

Find out why a sound doesn't play

Unreal 5.8 includes Audio Insights, a set of audio debugging windows. The kit has it built and switched on. I haven't run it in the kit yet.

  1. Open it during PIE. Look for Audio Insights in the editor's Tools menu. If it stays empty, check the Trace status-bar menu: Audio Insights needs the Unreal Trace Server, which the kit doesn't ship. It may only work on a PC that also has an Unreal install from the Epic launcher.
  2. Find your sound in the Sounds dashboard. It lists every sound playing, with its volume, distance and actor, and how much distance and occlusion turn it down. Solo by Text plays only matching sounds.
  3. Not there? Check Virtual Loops. A loop that's too far away, over its concurrency limit or low priority keeps running silently there.
  4. Read the Event Log. It records each play and stop with its asset and actor. "Play Failed: Concurrency" means your cue's concurrency rule blocked it.
  5. Check the right machine. In multiplayer PIE, the World Filter picks which client's sounds you see.
  6. Mark your own moments. The Log Audio Insights Event node adds a named line to the Event Log. Remove it before you publish.

Quick checks without it: stat audio, or au.Debug.SoundCues 1 and au.3dVisualize.Enabled 1 in the PIE console. They show playing cues and draw where sounds are. They're editor-only and reset when PIE stops.

The settings that matter

Setting Where
Attenuation Settings sound cue
Sound Class, Concurrency sound cue
Fire Sound, Equip Sound weapon actor
Use Item Sound, Equip Sound item
Niagara Muzzle FX weapon actor
Spawn Emitter, Destruction Emitter structure
Harvest Destruction Sound harvesting component

Common mistakes

No sound on a server

The sound plays on the server, which has no audio. Play it from a multicast, a replicated actor's Begin Play, or an animation notify (step 4). Silent everywhere live? Check the cue and its waves are in your mod folder.

The sound plays for everyone on the map

It has no attenuation, or a huge one. Set a preset on the cue (step 3). Full volume wherever you stand means a 2D sound. Play it at a location or on a component instead.

Every player hears a different random sound

Each client picked its own. Pick on the server and pass the sound in the multicast (step 4).

The effect is invisible in the cooked game

The system or its material sits outside your mod folder, or the cook dropped a Cascade system. Search the cook log for its name (When a cook or upload fails). Missing only for other players? It was spawned on the server or on one client (step 7).

It plays twice for the player who did it

The owner played it locally, then the multicast played it again. Drop one of the two for the owner.

I can't find which vanilla sound plays

Run stat audio in the console during PIE to see what's playing, or open Audio Insights: its Sounds dashboard lists every sound playing, with its asset and actor (above). Then right-click the asset → Reference Viewer.

Check it worked

  1. PIE, a listen server and a client: both hear and see it, once each.
  2. Walk away: it fades out at the range you expect.
  3. A local dedicated server with a separate client: it still plays. A late joiner hears loops and sees lasting effects.
  4. The client log after a cooked test has no "failed to load" line naming it (Reading ARK's logs).

Watch

No video in my library covers ASA sounds or Niagara effects yet. General Unreal talks cover Niagara performance: fixed bounds (Epic) and effect types and culling. Works in PIE, not on a server has the videos on replication, which is the hard part.

Go deeper

Sources

  • General Unreal videos (not ARK-specific, not checked in the kit): Ben Cloward on sprite overdraw (2025, auto captions).
  • Unreal Fest 2026 talks (UE 5.8, the kit's version; auto captions): the Sounds dashboard, distance and occlusion, Virtual Loops, the Event Log and Log Audio Insights Event (Audio Insights, 2026-07-20). The kit's own files confirm the plugin is built and on; the au. commands are in its editor build.
  • DevKit files, read offline on 2026-11-06 (UE 5.8.1): Rex_Roar_Cue and its waves (nodes, attenuation, sound class, concurrency, sample rate, channels); the attenuation presets in /Game/PrimalEarth/Sound/Attenuation/ (radii, falloff, occlusion); Rex-Bite2 (its Play Sound notify); a count across the 210,014 packages in the official content folders (36,158 sound waves, 9,005 sound cues, 45 MetaSound sources, 37 attenuation assets, 1,039 Niagara systems, 3,223 Cascade particle systems); the class data for ShooterWeapon, ShooterWeapon_Instant, ShooterWeapon_Projectile, PrimalItem, PrimalCharacter, PrimalStructure, PrimalStructureItemContainer, PrimalInventoryComponent and PrimalBuff (which sound and effect fields exist, and their types; NetPlaySoundOnCharacter and InventoryViewersPlayLocalSound).
  • My other pages: Works in PIE, not on a server (multicasts and late joiners), When a cook or upload fails (Cascade), How to make a buff (owner-only buffs).
  • What modders report, from the ARK Modding Community Discord: server-spawned sounds and buffs as the way to reach every client (September 2024); a server-picked random sound passed in a multicast (October 2025); attenuation that seemed ignored in the kit and worked in the cooked game (March 2024); always using the cue rather than the wave (April 2024); cues on montages and consumables silent on servers, moved into buffs (February and April 2026); occlusion settings on attenuation (June 2025); a Genesis cue left out of a mod folder (December 2025); Niagara on buffs (November 2023); keeping Cascade effects (March 2025); stat audio and looping seat sounds.
  • Community knowledge from the ARK Modding Community Discord (discussions from November 2023 to April 2026, mainly #asa-fx-and-media, #asa-general, #asa-animation and #asa-blueprints), found with Overseer. Threads that helped (they open for server members): who hears a sound (September 2024), a server-picked random sound (October 2025), attenuation in the kit (March 2024), montage sounds on a server (February 2026), consumable sounds on a server (April 2026), Niagara on buffs (November 2023), keeping Cascade effects (March 2025), stat audio (November 2024), a cue outside the mod folder (December 2025).
Where this page's information comes from

Applies to: ASA DevKit as of November 2026 (UE 5.8.1); ASE where noted

the DevKit's own sounds, attenuation presets, animations and class data, the community Discord (see Sources)

Esc

↑ ↓ move↵ openCtrl ↵ new tab