Remote Procedure Calls
Last updated
Last updated
Remote Procedure Calls, simply referred to as RPCs, are ideal for sharing punctual game events.
The Fusion module has 3 types of RPCs:
All of them work the same as the original Run instructions from Game Creator 2 except that they run through the Fusion network, and the target object requires a NetworkObject.
RpcTarget define on which it is executed.
All: can be sent / is executed by all peers in the session (including the server).
Proxies: can be sent / is executed by a peer who does not have either Input Authority or State Authority over the object.
InputAuthority: can be sent / is executed by the peer with Input Authority over the object.
StateAuthority: can be sent / is executed by the peer with State Authority over the object.
If enabled, the state of the trigger will be cached and sent to newly connected peers.
If you need to remove the cached state of any of the RPCs you can use the appropriate instructio for each type of RPC.
