Fix: Unreal GameplayTagContainer Not Replicating

You set a tag on the server. The client doesn’t see the change. The actor replicates other properties fine. GameplayTagContainer is a USTRUCT and follows normal replication rules — but it’s easy to skip a step.

The Symptom

Server-set GameplayTags don’t appear on clients. RPC calls work; other replicated properties update. Only the tag container is silent.

The Required Pattern

// Header
UCLASS()
class AMyActor : public AActor
{
    GENERATED_BODY()
public:
    AMyActor();

    UPROPERTY(ReplicatedUsing=OnRep_Tags, BlueprintReadOnly)
    FGameplayTagContainer Tags;

    UFUNCTION()
    void OnRep_Tags();

    virtual void GetLifetimeReplicatedProps(TArray<FLifetimeProperty>& Out) const override;
};

// Cpp
AMyActor::AMyActor()
{
    bReplicates = true;             // MUST
    SetReplicateMovement(true);       // optional, for transform
}

void AMyActor::GetLifetimeReplicatedProps(TArray<FLifetimeProperty>& Out) const
{
    Super::GetLifetimeReplicatedProps(Out);
    DOREPLIFETIME(AMyActor, Tags);
}

void AMyActor::OnRep_Tags()
{
    UE_LOG(LogTemp, Log, TEXT("Client saw tags update: %s"), *Tags.ToString());
}

Three things must all be true:

1. Actor bReplicates = true.
2. Property tagged Replicated or ReplicatedUsing.
3. Registered in GetLifetimeReplicatedProps.

Mutating from the Server

The container only replicates when modified on the server (HasAuthority). Client-side AddTag/RemoveTag never propagates — the change exists only locally and is overwritten on the next server replication.

void AMyActor::ServerAddTag(const FGameplayTag& Tag)
{
    if (!HasAuthority()) return;
    Tags.AddTag(Tag);
    OnRep_Tags();   // also fire locally on the server
}

Conditional Replication

To replicate to only some clients (owner, relevant), use COND parameters in DOREPLIFETIME:

DOREPLIFETIME_CONDITION(AMyActor, Tags, COND_OwnerOnly);

Verifying

Network Profiler (Window → Developer Tools → Network Profiler) records replicated properties per actor. Trigger a tag change on the server; the property should appear in the next replication batch with a non-zero size.

Or simply Print on the client’s OnRep_Tags. Should fire on every server-side change.

Understanding the issue

AI bugs are emergent. The code is correct in isolation; the behavior emerges from interaction with other systems. Reproducing means controlling the interaction; fixing means deciding which interaction was wrong.

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

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

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

For shipping games, the safest verification is a staged rollout. Apply the fix to 1% of players for 24 hours; watch the affected metric; expand if green. Skipping the staged rollout means the verification is the entire player base, which is too high a stakes for most fixes.

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

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

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

Platform-specific edge cases are worth enumerating explicitly. iOS handles backgrounding differently than Android; Windows handles focus changes differently than macOS. A fix that works on the development platform may not work on every target. Test on each shipping platform deliberately.

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.

“bReplicates. Replicated. DOREPLIFETIME. OnRep for client reactions. Tags arrive.”

Related Issues

For multiplayer spawn replication, see spawner replication. For input modifier stuck, see input modifier.

Three switches. Tags propagate.