ClientRPC one Client?

I can't see how to do this? Especially on reconnection in a game, I'd like to send a clientRPC to just one person. Is this possible?

Thanks,

 

Hello,

I would call the Rpc call on the NetworkBehaviour instantiated for this person (which would exist on every client of the game), then check the property isLocalPlayer to execute the code only on that person.

I don't know if this the optimal solution but I think this would work.

 

But the problem I have is where there's a single instance of an object that's shared between the three of them. So for example a GameManager. I want to basically sync a client's version of the GameManager with the server's and the use of SyncLists/SyncVars isn't really enough or would be very difficult to work with. So what I'd like to send is an array of int[] in an rpc call where my clients then make a list of current players based on that array of player numbers. I don't need to send this to preexisitng clients as they've already set themselves up.

 

You can use NetworkServer.Send, which sends to a single, specific client.

ClientRpc to single client would be great though

 

I would also consider network bandwith consumption. I think an RPC is always being send to all clients. If only one client uses it's data, however, the data send to the other clients is not needed so a significant part of the consumed network traffic is just going to waste. This waste likely scales with the amount of players and the actual data you send. Anyway, a reconnection seems to be something that does not happen too frequently, so a little waste/redundancy might be acceptable in this case. In terms of raw efficiency, I guess sending messages would be a better solution though.

 

Yeah I have seen NetworkServer.Send but as far as I'm aware you have to set up specific message types which feels rather overkill for a one shot message.

 

Agreed. I'm interested in any alternative solutions, since this seems like a problem lots of people have been running into (RPC to a specific client).

 

Wouldn't you just use Unity's TargetRpcAttribute?

 

I'm going to venture a guess they weren't using TargetRpc because it was added in Unity 5.4, which was released in mid 2016, but this necro thread is from the prior year.