Skip to content

Commit 8109f24

Browse files
authored
docs: Fixed a simple typo (#336)
activley -> actively
1 parent fff06dd commit 8109f24

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/_docs/the-basics/object-behaviour-relation.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ The MLAPI's high level components (The RPC system and the Object Spawning System
99
For an object to be replicated across the network it needs to have a NetworkedObject component. It also has to be registered as a NetworkedPrefab. When a NetworkedObject is considered "Spawned", it's replicated across the network so that everyone has their own version of the object. Each NetworkedObject gets assigned a NetworkId at runtime which is used to associate two NetworkedObjects across the network. Ex: One peer can say, Send this RPC to the object with the NetworkId 103 and everyone knows what object that is.
1010

1111
### NetworkedBehaviour
12-
NetworkedBehaviour is an abstract class that inherits MonoBehaviour and adds additional functionality. Each NetworkedBehaviour is owned by a NetworkedObject. NetworkedBehaviours can contain RPC methods and NetworkedVars. When you call InvokeRPC, a message is sent containing your parameters, the networkId of the NetworkedObject that owns the NetworkedBehaviour that the Invoke was called on, and the "index" of the NetworkedBehaviour on the NetworkedObject. This means that if you run multiple projects, it's important that the order and amount of NetworkedBehaviours on each NetworkedObject is the same. It also means that NetworkedBehaviour's can only exist as a child or on the same object as a NetworkedObject that is activley Spawned.
12+
NetworkedBehaviour is an abstract class that inherits MonoBehaviour and adds additional functionality. Each NetworkedBehaviour is owned by a NetworkedObject. NetworkedBehaviours can contain RPC methods and NetworkedVars. When you call InvokeRPC, a message is sent containing your parameters, the networkId of the NetworkedObject that owns the NetworkedBehaviour that the Invoke was called on, and the "index" of the NetworkedBehaviour on the NetworkedObject. This means that if you run multiple projects, it's important that the order and amount of NetworkedBehaviours on each NetworkedObject is the same. It also means that NetworkedBehaviour's can only exist as a child or on the same object as a NetworkedObject that is actively Spawned.
1313

1414

1515
#### RPC Flow
@@ -30,4 +30,4 @@ Receive:
3030
- Reads RPC Method Name Hash
3131
- Finds The Method With The Hash Provided
3232
- Invokes It's Delegate With Parameters Or Body
33-
```
33+
```

0 commit comments

Comments
 (0)