Skip to content
This repository was archived by the owner on Aug 10, 2021. It is now read-only.

Commit dbd86d1

Browse files
authored
Update README.md
1 parent 3772ad3 commit dbd86d1

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Documentation/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
## Game Events
44
<p align="center">
5-
<img width="100%" src="events.png" alt="Diagram showing how data is shared using events."/>
5+
<img width="75%" src="events.png" alt="Diagram showing how data is shared using events."/>
66
</p>
77

88
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
9090

9191
## Mutable Objects
9292
<p align="center">
93-
<img width="100%" src="mutable-objects.png" alt="Diagram showing how data is shared when using mutable objects."/>
93+
<img width="75%" src="mutable-objects.png" alt="Diagram showing how data is shared when using mutable objects."/>
9494
</p>
9595

9696
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

Comments
 (0)