Merge pull request #190 from simon-winter/patch-1

docs(object-spawning): added more Info about .Spawn() method

Author: TwoTenPvP

docs/_docs/the-basics/object-spawning.md

@@ -12,6 +12,14 @@ GameObject go = Instantiate(myPrefab, Vector3.zero, Quaternion.identity);
 go.GetComponent<NetworkedObject>().Spawn();
 ```
 
+The .Spawn() method takes 2 parameters, both with default values, so they are optional.
+```csharp
+public void Spawn(Stream spawnPayload = null, bool destroyWithScene = false);
+```
+The first parameter is a System.IO.Stream and can be retrieved in the NetworkStart() to sync values once when spawning this object. Note however, that the payload data is only avalible for people that get the spawn call straight away. People that join later on won't get the payload data.
+
+The second parameter speaks for itself. If set to true, the object will be destroyed on scene switching. This can only be set inside the spawn call.
+
 ## Scene Objects
 Any objects already on the server with NetworkedObject components (static scene objects) will get automatically replicated. 
 
@@ -21,4 +29,4 @@ There are **two** modes that define how scene objects are spawned. The first mod
 If PrefabSync is disabled, the MLAPI will use SoftSync. This allows scene objects to be non prefabs and they will not be replaced, thus keeping their serialized data. **This mode is recommended for single project setups**. This is the default since MLAPI 6.
 
 #### PrefabSync
-If it's enabled, every scene object has to be a prefab and scene objects are recreated on the client side. This means that serialized data gets lost on the clients. It's thus recommended to place serialized data in NetworkedVars. **This mode is ONLY recommended for Multi project setups**. This was the default before MLAPI 6.
+If it's enabled, every scene object has to be a prefab and scene objects are recreated on the client side. This means that serialized data gets lost on the clients. It's thus recommended to place serialized data in NetworkedVars. **This mode is ONLY recommended for Multi project setups**. This was the default before MLAPI 6.