Quick answer: Make sure you override GetLifetimeReplicatedProps and call DOREPLIFETIME_CONDITION for the right property. Verify the actor has an owning PlayerController for COND_OwnerOnly to work.

You added a private inventory array to a player’s pawn and used DOREPLIFETIME_CONDITION(AMyPawn, Inventory, COND_OwnerOnly) to keep it from leaking to opponents. Open a 4-player session, log Inventory contents from each client — every client sees every player’s inventory. The condition is being ignored.

How Replication Conditions Work

Each replicated property has a per-frame check the engine performs against every connection. COND_OwnerOnly resolves “owner” via AActor::GetNetOwner, which walks up the owner chain to a APlayerController. If the actor has no owning PlayerController, “owner” is the server (or null), so the engine sends the property to nobody — or to everyone, depending on the condition.

Common ways to break this:

Step 1: Correct Replication Registration

// MyPawn.h
UCLASS()
class AMyPawn : public APawn
{
    GENERATED_BODY()
public:
    AMyPawn() { bReplicates = true; }
    virtual void GetLifetimeReplicatedProps(TArray<FLifetimeProperty>& Out) const override;

protected:
    UPROPERTY(Replicated)
    TArray<FName> Inventory;
};

// MyPawn.cpp
void AMyPawn::GetLifetimeReplicatedProps(TArray<FLifetimeProperty>& Out) const
{
    Super::GetLifetimeReplicatedProps(Out);
    DOREPLIFETIME_CONDITION(AMyPawn, Inventory, COND_OwnerOnly);
}

The const override on the function signature must match exactly — if it’s missing override and the parent signature changes, your method silently stops being called.

Step 2: Ensure Server Owner Is Assigned

When the player spawns, the server assigns the pawn to the PlayerController via possession. Verify with a log:

// On the server, after spawn
APawn* P = ...;
P->SetOwner(PlayerController);
UE_LOG(LogTemp, Log, TEXT("Pawn owner: %s"),
       P->GetOwner() ? *P->GetOwner()->GetName() : TEXT("none"));

If the log says “none”, the PlayerController didn’t take ownership. Without ownership, COND_OwnerOnly excludes the property from every client — including the one you intended to send it to. In practice this often means the inventory looks empty on all clients, which is the inverse of the original bug.

Step 3: Confirm the Condition Macro

Common confusion table:

Step 4: Use Network Profiler

From the console on the server:

NetProfile start
// play for 30s
NetProfile stop

Open the saved profile in Tools → Profiling → Network Profiler. You’ll see per-property bandwidth and per-connection deltas. If Inventory shows up under more clients than expected, the condition isn’t being honored.

Verifying

Add a log to OnRep_Inventory and run 4 clients. Only the owning client should log inventory contents. Other clients should never call OnRep. If they do, double-check ownership and condition setup.

Understanding the issue

Replication systems make the same data visible on multiple machines. The hard part is that these machines have different clocks, different network conditions, and different load. A replication bug usually means one of these realities was ignored.

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

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

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

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

Diagnostic approach

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

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

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

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.

“Replication conditions need three correct things: registration, ownership, and the right macro. One missing piece = condition ignored.”

For player-private data, COND_OwnerOnly + SetOwner is the safe combination. Verify owner is set before any replication starts.