Merge pull request #7 from spatialos/release-1.0.1-rc-01

Release 1.0.1-rc-01

Author: oblm

Assets/Plugins/Improbable/Sdk/Dll/Improbable.WorkerSdkCsharp.Framework.dll

@@ -149,8 +149,8 @@ private IEnumerator Connect()
             var connect = WorkerConnection.ConnectAsync(parameters, Deployment, AttachConnection);
             yield return connect;
 
-            SpatialOS.ConnectionWasSuccesful = Connection.IsConnected;
-            if (SpatialOS.ConnectionWasSuccesful)
+            SpatialOS.ConnectionWasSuccessful = Connection.IsConnected;
+            if (SpatialOS.ConnectionWasSuccessful)
             {
                 logger = new LogSender(() => SpatialOS.IsConnected, Connection.SendLogMessage, SpatialOS.Configuration, SpatialOS.LogFilter);
                 SetupComponents();
@@ -200,6 +200,7 @@ private void Update()
         // before calling the first OnDestroy).
         private void OnApplicationQuit()
         {
+            SpatialOS.SignalApplicationQuit();
             Dispose();
         }
 

Assets/Plugins/Improbable/Sdk/Dll/Improbable.WorkerSdkCsharp.Framework.dll.meta

@@ -50,7 +50,7 @@ static SpatialOS()
             };
         }
 
-        internal static bool ConnectionWasSuccesful { get; set; }
+        internal static bool ConnectionWasSuccessful { get; set; }
 
         /// <summary>
         ///     A callback that will be invoked when the deployment list has been retrieved from the Locator.
@@ -691,10 +691,21 @@ internal static void Disconnected(DisconnectOp disconnectOp)
             receivedDisconnectOp = disconnectOp;
             Disconnecting = true;
         }
+        
+        internal static void SignalApplicationQuit()
+        {
+            if (!ConnectionWasSuccessful)
+            {
+                receivedDisconnectOp = new DisconnectOp
+                {
+                    Reason = "An application quit signal was received."
+                };
+            }
+        }
 
         internal static void SignalDisconnection()
         {
-            if (!ConnectionWasSuccesful)
+            if (!ConnectionWasSuccessful)
             {
                 OnConnectionFailedInternal();
                 OnConnectionFailedWithReasonInternal();

Assets/Plugins/Improbable/Sdk/Dll/Improbable.WorkerSdkCsharp.Framework.xml

@@ -217,8 +217,8 @@ The menu `Improbable -> Prefabs -> Export All EntityPrefabs` runs the entity exp
 
 This method puts files into the `<project root>/build/assembly/` directory; when you run `spatial cloud upload`, the
 contents of this directory are uploaded so they can be used by a
-[cloud deployment (SpatialOS documentation)](https://docs.improbable.io/reference/12.2/shared/glossary#cloud-deployment). For more information
-on deploying, see [Deploying to the cloud (SpatialOS documentation)](https://docs.improbable.io/reference/12.2/shared/deploy/deploy-cloud).
+[cloud deployment (SpatialOS documentation)](https://docs.improbable.io/reference/13.0/shared/glossary#cloud-deployment). For more information
+on deploying, see [Deploying to the cloud (SpatialOS documentation)](https://docs.improbable.io/reference/13.0/shared/deploy/deploy-cloud).
 
 ### Customizing the exporting of prefabs
 
@@ -277,7 +277,7 @@ If you use the `Local` asset database, workers will load asset bundles from a di
 on disk. Assets are bundled into the worker executable, which means workers don't need to download prefab information
 at entity spawn time.
 
-Set this in the [launch section of the worker configuration file (SpatialOS documentation)](https://docs.improbable.io/reference/12.2/shared/worker-configuration/launch-configuration)
+Set this in the [launch section of the worker configuration file (SpatialOS documentation)](https://docs.improbable.io/reference/13.0/shared/worker-configuration/launch-configuration)
 (eg `spatialos.UnityClient.worker.json`) in the `arguments` section, for example:
 
 ```
@@ -298,7 +298,7 @@ However, it might take longer to load initially, depending on internet speed, an
 This is the default asset database, but we recommend switching to the local asset database.
 
 To explicitly use the streaming asset database, set this in the
-[launch section of the worker configuration file (SpatialOS documentation)](https://docs.improbable.io/reference/12.2/shared/worker-configuration/launch-configuration)
+[launch section of the worker configuration file (SpatialOS documentation)](https://docs.improbable.io/reference/13.0/shared/worker-configuration/launch-configuration)
 (eg `spatialos.UnityClient.worker.json`) in the `arguments` section, for example:
 
 ```

Assets/Plugins/Improbable/Sdk/Dll/Improbable.WorkerSdkCsharp.Framework.xml.meta

@@ -3,12 +3,12 @@ is experimental.
 
 # Entity pipeline
 
-The **entity pipeline** is the logic which a [worker (SpatialOS documentation)](https://docs.improbable.io/reference/12.2/shared/glossary#worker) uses to create and
+The **entity pipeline** is the logic which a [worker (SpatialOS documentation)](https://docs.improbable.io/reference/13.0/shared/glossary#worker) uses to create and
 manage their representations of entities.
 
-A SpatialOS [deployment (SpatialOS documentation)](https://docs.improbable.io/reference/12.2/shared/glossary#deploying) communicates with connected workers to instruct them
+A SpatialOS [deployment (SpatialOS documentation)](https://docs.improbable.io/reference/13.0/shared/glossary#deploying) communicates with connected workers to instruct them
 when an entity needs to be added/removed from the worker's view. For example, when an entity moves into or out of a
-worker's [checkout area (SpatialOS documentation)](https://docs.improbable.io/reference/12.2/shared/glossary#checking-out). The entity pipeline handles:
+worker's [checkout area (SpatialOS documentation)](https://docs.improbable.io/reference/13.0/shared/glossary#checking-out). The entity pipeline handles:
 
 * choosing how to represent an entity locally - in Unity, we use a prefab to represent an entity
 * dealing with changes in an entity's components (one being added or removed) and changes in the properties of those
@@ -104,7 +104,7 @@ entity spawning to the next frame if necessary.
     > Make sure that those two components are attached to every entity (see
     [Creating an entity](../interact-with-world/create-delete-entities.md#create-an-entity)
     for more details) and that your
-    [bridge configuration (SpatialOS documentation)](https://docs.improbable.io/reference/12.2/shared/worker-configuration/bridge-config#component-delivery) adds these
+    [bridge configuration (SpatialOS documentation)](https://docs.improbable.io/reference/13.0/shared/worker-configuration/bridge-config#component-delivery) adds these
     components to your worker.
 
     > If you can't include the components, consider replacing this block with a modified version of

Assets/Plugins/Improbable/Sdk/Dll/Improbable.WorkerSdkCsharp.dll.meta

@@ -1,7 +1,7 @@
 # Logging
 
 Unity SDK will send messages logged via Unity's `Debug.Log` family of functions to SpatialOS. You can view these logs
-in your cloud deployment's web interface. See the documentation for [cloud deployments (SpatialOS documentation)](https://docs.improbable.io/reference/12.2/shared/operate/logs#cloud-deployments)
+in your cloud deployment's web interface. See the documentation for [cloud deployments (SpatialOS documentation)](https://docs.improbable.io/reference/13.0/shared/operate/logs#cloud-deployments)
 for more information.
 
 ## Global log levels

Assets/Plugins/Improbable/Sdk/Dll/Improbable.WorkerSdkCsharp.xml.meta

@@ -29,10 +29,10 @@ This system does have a few downsides:
 
 To set up Unity to use the new build system:
 
-1. In the `spatialos.*.worker.json` files for both the UnityClient and UnityWorker, change the value of [`tasks_filename` (SpatialOS documentation)](https://docs.improbable.io/reference/12.2/shared/worker-configuration/worker-build#using-custom-build-scripts):
+1. In the `spatialos.*.worker.json` files for both the UnityClient and UnityWorker, change the value of [`tasks_filename` (SpatialOS documentation)](https://docs.improbable.io/reference/13.0/shared/worker-configuration/worker-build#using-custom-build-scripts):
   * For `spatialos.UnityClient.worker.json`, change `spatialos.unity.client.build.json` to `Improbable/build_script/spatialos.unity.client.build.experimental.json`
   * For `spatialos.UnityWorker.worker.json`, change `spatialos.unity.worker.build.experimental.json` to `Improbable/build_script/spatialos.unity.worker.build.experimental.json`
-1. In the root folder of your project, run [`spatial codegen` (SpatialOS documentation)](https://docs.improbable.io/reference/12.2/shared/spatial-cli/spatial-worker-codegen#spatial-worker-codegen).
+1. In the root folder of your project, run [`spatial codegen` (SpatialOS documentation)](https://docs.improbable.io/reference/13.0/shared/spatial-cli/spatial-worker-codegen#spatial-worker-codegen).
 1. Open your project in Unity.
 1. Open the UnityClient scene, and select the "Bootstrap" or "GameEntry" `GameObject` in the hierarchy.
 1. Remove the `DefaultTemplateProvider` component if it is there, then add the `BasicTemplateProvider` component.
@@ -49,15 +49,15 @@ There are two ways to build your workers:
   * The console will print a log after the build has completed.
 
 * From a command prompt in your project folder
-  * With Unity closed, run [`spatial worker build --target=local` (SpatialOS documentation)](https://docs.improbable.io/reference/12.2/shared/spatial-cli/spatial-worker-build#spatial-worker-build)
+  * With Unity closed, run [`spatial worker build --target=local` (SpatialOS documentation)](https://docs.improbable.io/reference/13.0/shared/spatial-cli/spatial-worker-build#spatial-worker-build)
 
 ## Configuring your build
 
 You can use the build configuration asset created in [Getting started](#getting-started) to configure how the workers should be built.
 
 ### Local and cloud environment
 
-Use the local and cloud environments to have different build settings for [local (SpatialOS documentation)](https://docs.improbable.io/reference/12.2/shared/glossary#local-deployment) and [cloud (SpatialOS documentation)](https://docs.improbable.io/reference/12.2/shared/glossary#cloud-deployment) deployments. Both environments will produce the same results if they have the same settings, with the exception of the compression on the final zip file: to save build time, the local environment will not enable compression.
+Use the local and cloud environments to have different build settings for [local (SpatialOS documentation)](https://docs.improbable.io/reference/13.0/shared/glossary#local-deployment) and [cloud (SpatialOS documentation)](https://docs.improbable.io/reference/13.0/shared/glossary#cloud-deployment) deployments. Both environments will produce the same results if they have the same settings, with the exception of the compression on the final zip file: to save build time, the local environment will not enable compression.
 
 > 'local' and 'cloud' environments were previously called 'development' and 'deployment'.
 
@@ -142,4 +142,4 @@ You can revert to the old system using the following steps:
 1. Delete the build configuration asset that was created in step 7 of [Getting Started](#getting-started).
 1. Revert the changes to the UnityClient and UnityWorker scenes.
 1. Revert the changes to the `spatialos.*.worker.json` files.
-1. Run [`spatial codegen` (SpatialOS documentation)](https://docs.improbable.io/reference/12.2/shared/spatial-cli/spatial-worker-codegen#spatial-worker-codegen) in your project's root folder.
+1. Run [`spatial codegen` (SpatialOS documentation)](https://docs.improbable.io/reference/13.0/shared/spatial-cli/spatial-worker-codegen#spatial-worker-codegen) in your project's root folder.

Assets/Plugins/Improbable/Sdk/Src/Unity/Core/ConnectionLifecycle.cs

@@ -54,7 +54,7 @@ the secret key.
 
 ### Pass a command-line argument
 
-The command-line arguments used to launch each worker are defined in the [worker launch configuration files (SpatialOS documentation)](https://docs.improbable.io/reference/12.2/shared/worker-configuration/launch-configuration#worker-launch-configuration). To add a command line argument:
+The command-line arguments used to launch each worker are defined in the [worker launch configuration files (SpatialOS documentation)](https://docs.improbable.io/reference/13.0/shared/worker-configuration/launch-configuration#worker-launch-configuration). To add a command line argument:
 
 0. Open `workers/unity/spatialos.UnityWorker.worker.json`. The command-line arguments for 
     each target are defined in the arguments object.

Assets/Plugins/Improbable/Sdk/Src/Unity/Core/SpatialOS.cs

@@ -110,7 +110,7 @@ At this stage, you can start a game client from Steam. However, the current impl
 
 * UnityClients can only be started from Steam and nowhere else.
 * UnityWorkers won't connect.
-* The [Launcher (SpatialOS documentation)](https://docs.improbable.io/reference/12.2/shared/glossary#launcher) will no longer work.
+* The [Launcher (SpatialOS documentation)](https://docs.improbable.io/reference/13.0/shared/glossary#launcher) will no longer work.
 
 To fix these problems, you can wrap the Steam logic in a check for a command-line argument: `steamClient`.
 This argument will be present when you launch a client from Steam. But it won't be there when you launch a client
@@ -158,8 +158,8 @@ To do this:
     * Executable: Your client executable, for example `UnityClient@Windows.exe` or `UnityClient@Mac.app`.
     * Arguments: `+appName <your SpatialOS project name> +assetDatabaseStrategy Streaming +steamClient true`
         * `+appName` needs to be set to your
-        [SpatialOS project name (SpatialOS documentation)](https://docs.improbable.io/reference/12.2/shared/glossary#project-name), as specified in
-        your [`spatialos.json` (SpatialOS documentation)](https://docs.improbable.io/reference/12.2/shared/reference/file-formats/spatialos-json).
+        [SpatialOS project name (SpatialOS documentation)](https://docs.improbable.io/reference/13.0/shared/glossary#project-name), as specified in
+        your [`spatialos.json` (SpatialOS documentation)](https://docs.improbable.io/reference/13.0/shared/reference/file-formats/spatialos-json).
         * `+assetDatabaseStrategy Streaming` specifies that entity prefabs loaded as part of your project assemblies
         will be downloaded to the game client at runtime.
         * `+steamClient true` means that clients launched from Steam will use Steam authentication, using the
@@ -181,7 +181,7 @@ To do this for all the deployments in your project:
 
 Alternatively, you can:
 
-* Add the tag when [launching a cloud deployment (SpatialOS documentation)](https://docs.improbable.io/reference/12.2/shared/deploy/deploy-cloud) (replacing `steam_deployment` with your own string):
+* Add the tag when [launching a cloud deployment (SpatialOS documentation)](https://docs.improbable.io/reference/13.0/shared/deploy/deploy-cloud) (replacing `steam_deployment` with your own string):
 
     ```
     spatial cloud launch [...] --tags=steam_deployment