Added example component with write-access to example entity

Workers will not check any entities out unless they have write-access to at least one component on an entity, which is handled by the Name component added as an example

Author: samc-improbable

schema/improbable/player/name.schema

@@ -1 +1,8 @@
-package improbable.player;
+package improbable.player;
+
+component Name {
+    // Schema file ID, unique within the project
+    id = 1001;
+
+    string entity_name = 1;
+}

snapshots/initial_world.snapshot

@@ -1,6 +1,7 @@
 using Improbable.General;
 using Improbable.Worker;
 using Improbable.Math;
+using Improbable.Player;
 using Improbable.Unity.Core.Acls;
 using UnityEngine;
 
@@ -16,9 +17,16 @@ public static SnapshotEntity GenerateExampleSnapshotEntityTemplate()
 
             // Define components attached to snapshot entity
             exampleEntity.Add(new WorldTransform.Data(new WorldTransformData(new Coordinates(-5, 10, 0))));
+            exampleEntity.Add(new Name.Data(new NameData("your_example_entity")));
+
+            var acl = Acl.Build()
+                // Both FSim (server) workers and client workers granted read access over all states
+                .SetReadAccess(CommonPredicates.PhysicsOrVisual)
+                // Only FSim workers granted write access over WorldTransform component
+                .SetWriteAccess<WorldTransform>(CommonPredicates.PhysicsOnly)
+                // Only client workers granted write access over Name component
+                .SetWriteAccess<Name>(CommonPredicates.VisualOnly);
 
-            // Grant FSim (server-side) workers write-access over all of this entity's components, read-access for visual (e.g. client) workers
-            var acl = Acl.GenerateServerAuthoritativeAcl(exampleEntity);
             exampleEntity.SetAcl(acl);
 
             return exampleEntity;