You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 10, 2021. It is now read-only.
Copy file name to clipboardExpand all lines: Documentation/README.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
## Game Events
4
4
<palign="center">
5
-
<imgwidth="100%"src="events.png"alt="Diagram showing how data is shared using events."/>
5
+
<imgwidth="75%"src="events.png"alt="Diagram showing how data is shared using events."/>
6
6
</p>
7
7
8
8
Game events allow to decouple prefabs from direct dependencies such as scene or nested prefab game objects. The biggest benefit of events is that they can be referenced in isolated prefabs, this allows to later avoid having to set them up in the scene.
@@ -90,7 +90,7 @@ Import the `GameEvents` sample which shows how to use game events in various sit
90
90
91
91
## Mutable Objects
92
92
<palign="center">
93
-
<imgwidth="100%"src="mutable-objects.png"alt="Diagram showing how data is shared when using mutable objects."/>
93
+
<imgwidth="75%"src="mutable-objects.png"alt="Diagram showing how data is shared when using mutable objects."/>
94
94
</p>
95
95
96
96
Mutable objects allow using `ScriptableObject` assets to store and share data. They are handy when a lot of behaviours need access to specific data. In such cases, mutable objects can be injected in dependant behaviours instead of forming hard dependencies between them or using singletons.
0 commit comments