Hi Alex,
Thanks for the prompt response. Using LogNetTraffic allowed me to see what is causing the issue here and it’s our blueprint calling a reliable multicast RPC which is causing the not relevent actor to be created on the client. Changing this RPC to unreliable does not help. If I remove all calls to this RPC, the actor no longer spawns as expected.
Is there something that I’m missing to prevent RPCs from being sent? I would assume that these follow the same rules as the rest of the node?