caleb-brown/unity-atoms
1
0
Fork 0
mirror of https://github.com/unity-atoms/unity-atoms.git synced 2025-01-22 08:08:51 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

[doc] Added informations to "Changed with history" documentation

Browse Source 
I couldn't find a part in the documentation that indicated which was which in "Changed with history" callbacks FloatPair.
This commit is contained in:
Pordrack 2024-05-25 14:37:24 +02:00
parent 2e11570e74
commit 97ba3f8b33
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/tutorials/events.md
View File

@ -10,7 +10,7 @@ sidebar_label: Events
Events are things that happens in our game that other scripts or entities could listen and subscribe to. Events are (like Variables) also Scriptable Objects that live outside of a specific scene. In Unity Atoms Events can be of different types and thereby pass along data to listeners. Variables do by default have the possibility to raise two specific Events:
- `Changed` — raised every time a Variable’s value is changed. The Event contains the new value.
- `Changed With History` — also raised every time a Variable’s value is changed. However, this Event contains both the new and the old value.
- `Changed With History` — also raised every time a Variable’s value is changed. However, this Event contains both the new and the old value. The callbacks to this event receive a FloatPair object, with Item1 being the new value and Item2 the old value.
This makes it easier to make our game more data driven than just using Variables. Lets take a look at how that looks in our last example. We can [create](./creating-atoms.md) a new `IntEvent` and called `HealthChangedEvent`. Drop it on our `IntVariable` for the player’s health like this: