#Unity networkview rpc vs rpc android
#Unity networkview rpc vs rpc software

#Unity networkview rpc vs rpc android

It then calls an RPC when clicking on the area to affect.Unity 3.3 Android Changes from Pre-Release Version

We would not care about the area of effect ability's VFX, which works great with a transient RPC.ĪoeActionInput.cs Shows the input being updated client side and not waiting for the server. If a new player connects, they will see the damaged imps. The imp's health ( NetworkVariables) is updated. The area of effect action ( AoeAction) triggers an RPC when the action is activated (showing a VFX around the affected area). They do care about the current health of the players around that explosion though.Īctions in Boss Room are a great example for this. A newly connected player doesn't care about an explosion that happened 5 seconds ago. You would have an 'unexploded' state that would need to be synced everytime a new player connected? From a design perspective, you might not want to represent these events as state.Īn explosion could use an RPC for the event, but the effect of the explosion should be using NetworkVariables ( for example player's knockback and health decrease). If you have a temporary event like an explosion, you do not need a replicated state for this. Why not use NetworkVariables for everything? # If I open the door and a player connects after this, the host will replicate all the world's information to that new player, including the door's state. It uses a BoolNetworkVariable to represent the 'IsOpen' state. In that case, it is preferable to use NetworkVariables like shown here. If we sent an RPC to all clients, then all players connecting mid game after that RPC are sent will miss that information and have the wrong visual on their clients. A player's client needs to receive the information that the door is open to play the right animations. Using the Boss Room's door as an example.

Use NetworkVariables for persistent states, for information that will be around more than a moment.Ī quick way to choose which to use is to ask yourself: 'Should a player joining mid-game get that information?'.

Use RPCs for transient events, information only useful for a moment when it's received.

If you change your variable's value on your side, others will see the latest value on their side.įor more information on NetworkVariables see NetworkVariable Choosing between NetworkVariables or RPCs # NetworkVariable can be referenced as 'state' or as 'Netvars' or as replicated vars. Your state gets updated at regular intervals. When a client connects initially to a host, all relevant NetworkVariable latest values 'state' will be replicated to that new client. Its values are replicated to other nodes in your network regularly. If you call an RPC method on your side, it will execute on a different machine.įor more information on RPC's see Messaging System and RPCs NetworkVariables #Īt a high level, a NetworkVariable is a variable with its value tracked by the SDK. They are 'events' you can trigger when needed. When calling an RPC, you call a method remotely on an object that could be anywhere in the world.

The server will receive that information, find the specified object, find the specified method and call it on the specified object with the received parameters. They are ways to call methods on objects that are not in the same executable.Īt a high level, when calling an RPC client side, the SDK will take a note of the object, component, method and any parameters for that RPC and send that information over the network.

#Unity networkview rpc vs rpc software

The concept of an RPC is common not only in video games but in the software industry in general. The logic and your design considerations around how they send messages is what will make you choose one over the other. They both send messages over the network. RPC (Remote Procedure Call) and replicated state ( NetworkVariable). MLAPI has two main methods of syncing information between players.