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
Signal mechanic is something really flexible to use now, and i would like to make it more flexible by introducing "Value signal"
It is the same Signal mechanic but it triggers only to certain value that is set in it
For example:
""""""Signal value""""""
mana true/false
cooldown true/false
target receiver true/false
signal value (here you can set an value name or a value itself)
"""""""""""""""""""""""""""""""
""""""Signal value emit""""""
mana true/false
count as cast true/false
signal value (here you can set an value name or a value itself)
self handling true/false
arguments...
"""""""""""""""""""""""""""""""
So in the "signal value" section you set a value directly or a value name key, this way you can create signals that dynamicaly can change and react to certain values that are set any time
For example you can have one signal emit with a value name key, that value changes by some actions, and you have many signal receivers each with different value, for example "signal 1000". "signal 1001" and so on, so one of them triggers depends on what value was set by the time the signal was emit. And if you set an value name key, you can change it on the go with other value mechanics, to make signal receivers flexible
The text was updated successfully, but these errors were encountered:
Signal mechanic is something really flexible to use now, and i would like to make it more flexible by introducing "Value signal"
It is the same Signal mechanic but it triggers only to certain value that is set in it
For example:
""""""Signal value""""""
mana true/false
cooldown true/false
target receiver true/false
signal value (here you can set an value name or a value itself)
"""""""""""""""""""""""""""""""
""""""Signal value emit""""""
mana true/false
count as cast true/false
signal value (here you can set an value name or a value itself)
self handling true/false
arguments...
"""""""""""""""""""""""""""""""
So in the "signal value" section you set a value directly or a value name key, this way you can create signals that dynamicaly can change and react to certain values that are set any time
For example you can have one signal emit with a value name key, that value changes by some actions, and you have many signal receivers each with different value, for example "signal 1000". "signal 1001" and so on, so one of them triggers depends on what value was set by the time the signal was emit. And if you set an value name key, you can change it on the go with other value mechanics, to make signal receivers flexible
The text was updated successfully, but these errors were encountered: