Fix: Unreal GameplayCue Not Firing on Client

Here is how to fix Unreal GameplayCue not firing on client. You apply a Gameplay Effect that should spawn a fire particle and play a sound via a GameplayCue. It works in single-player PIE. In multiplayer, the server sees the effect but clients see nothing — no particles, no sound, no visual feedback. The Gameplay Effect applies correctly on both sides (damage lands), but the cosmetic cue only fires on the server.

The Symptom

A GameplayCue associated with a Gameplay Effect does not trigger its visual or audio handler on remote clients. The effect applies (gameplay logic works), but the cosmetic layer is silent. In the Gameplay Debugger, the cue tag shows as active on the server but not on the client’s ASC.

What Causes This

Tag not prefixed with GameplayCue. The GameplayCueManager only processes tags that begin with GameplayCue. (e.g., GameplayCue.Fire.Burst). A tag like Effect.Fire.Burst is ignored by the cue system entirely.

Cue handler not in scanned path. The GameplayCueManager scans specific asset directories to discover cue handler Blueprints. If your GC_FireBurst Blueprint is in a plugin folder or a non-default directory, the manager does not find it. No handler means no execution.

Gameplay Effect not replicating. If the GE’s replication policy is set to not replicate, or if Minimal Replication skips it, the client’s ASC never receives the effect — and never fires the cue. The cue fires from the ASC that receives the effect, not from a central dispatcher.

Using Execute vs Add incorrectly. ExecuteGameplayCue fires a one-shot event. AddGameplayCue starts a persistent cue that must be removed. If you call Execute for a looping effect, it fires once and stops. If you call Add for a burst effect, it stays active indefinitely.

Client does not have the handler loaded. In packaged builds, if the cue handler is not referenced by anything in the client’s asset graph, it may be stripped during cooking. The manager cannot find an uncooked asset.

The Fix

Step 1: Use correct tag prefix.

// In your Gameplay Effect Blueprint:
// Display > Gameplay Cues > GameplayCue Tag:
//   GameplayCue.Combat.HitSpark    (correct)
//   Combat.HitSpark                (WRONG - not picked up)

// C++ equivalent when manually executing:
FGameplayTag CueTag = FGameplayTag::RequestGameplayTag(
    FName("GameplayCue.Combat.HitSpark"));

FGameplayCueParameters Params;
Params.Location = HitLocation;
Params.Normal = HitNormal;

AbilitySystemComponent->ExecuteGameplayCue(CueTag, Params);

The tag MUST start with GameplayCue. for the system to route it to cue handlers.

Step 2: Ensure the handler is in a scanned directory. Check DefaultGame.ini:

[/Script/GameplayAbilities.AbilitySystemGlobals]
GameplayCueNotifyPaths="/Game/Effects/GameplayCues"
GameplayCueNotifyPaths="/Game/Blueprints/Cues"

Add paths where your GameplayCueNotify assets live. The manager scans these recursively on startup.

Step 3: Set replication on the Gameplay Effect. In the GE Blueprint, under Replication:

// Gameplay Effect settings:
// Replication > Replicate Gameplay Effect to Owner: true
// Replication > Minimal Replication Tags: ensure cue tag included

// For Minimal Replication mode on the ASC:
// The GE must be marked to replicate for minimal mode
// Set in GE: bReplicateToOwner = true

If your ASC uses Minimal Replication (common for large player counts), effects must explicitly opt into replication. Otherwise the client ASC never receives them and never fires cues.

Step 4: Choose Execute vs Add correctly.

// One-shot (particle burst, sound): use Execute
AbilitySystemComponent->ExecuteGameplayCue(CueTag, Params);

// Persistent (burning aura, shield glow): use Add/Remove
AbilitySystemComponent->AddGameplayCue(CueTag, Params);
// Later:
AbilitySystemComponent->RemoveGameplayCue(CueTag);

Match the cue type to the handler type. GameplayCueNotify_Static handles Execute. GameplayCueNotify_Actor handles Add/Remove with OnActive, WhileActive, and OnRemove events.

Debugging Cue Execution

Use showdebug abilitysystem in the console. It shows active Gameplay Effects and their associated cue tags. If a cue tag appears on server but not client, the replication path is broken. If it appears on client but the visual does not play, the handler is missing or not loaded.

“GameplayCues are cosmetic replication. The GE replicates the gameplay, the cue replicates the feel. Both must reach the client independently.”

Related Issues

For collision channel issues in multiplayer, see Collision Channel Not Blocking. For general replication problems, see Actor Replication Not Working.

GC_ prefix, scanned paths, replicated GE, correct Execute vs Add. Cues fire on all clients.