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.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unreal Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

The triage path for this kind of bug is long. The symptom appears in gameplay, but the cause is in a different system. The reporter describes the gameplay effect; the engineer has to translate that into a hypothesis about the underlying cause. Misdirection is common.

At the engine level, the behavior comes from a deliberate design decision in Unreal. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

Live games surface this bug class at scale. What's a rare edge case in development becomes a daily occurrence once you have a few thousand concurrent players. The class isn't 'this player has a unique setup'; it's 'one in N thousand sessions will trigger this exact combination'.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

For Unreal-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

Within Unreal, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“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.