Child actor component never replicated

[anonymous_user_c018ee23]

@NisshokuZK;243274

I’ve been working on a project where we use SetIsReplicated to dynamically spawn replicated components and add them to a replicated actor. So to clear your doubts about whether its possible to replicate a child actor component, it certainly is. Child components that are known pre-begin play should be easier to replicate than dynamically spawned components.

One thing I may have misunderstood from your first post. Is your child component an actor (inheriting from AActor) or a component (inheriting from UActorComponent, USceneComponent…)?

Also, you mention that the child components are added in blueprint. Where is that, in the construction script or at begin play? Note that in both cases it would count as dynamic spawning. Both server and client execute the construction script and BeginPlay event. If we are dynamically spawning then you have to (1) set the actor class and component class to replicate and (2) make sure the actual spawning/attaching only happens on the server.

Thanks for answering.

The child actor is an actor, not a component. So It is an actor connected to the parent actor via the child actor component.

Here is how the system is setup:

1. in C++ code I define a parent actor class and a child actor class (bReplicates = true on both of them).
2. I create a blueprint that derives from the parent actor C++ class.
3. I create a blueprint that derives from the child actor C++ class.
4. I add a child actor component to the parent blueprint (in the components tab, not dynamically at begin play, but as part of the blueprint itself) and link both actors there.
5. In the PostInitializeComponents of the parent C++ class I get the child actor component and call SetIsReplicated(true) on it (if HasAuthority)
6. I add the blueprint to the scene (no dynamic spawning)

Somehow on the client, the parent is always a replica (has no authority) while the child always has authority.