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
Is your feature request related to a problem? Please describe.
It would be a useful feature to implement and then combine with orders. Rather than having events called by name and implementing them in code, we could allow designers to create events using scriptable objects (similar to SOAP). We could then allow these objects to be used in orders via property fields which could then be triggered for specific game features.
This is similar to just calling another node from one node but would make it more flexible and robust.
Additional context
Checkout how SOAP looks and implements such objects.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
It would be a useful feature to implement and then combine with orders. Rather than having events called by name and implementing them in code, we could allow designers to create events using scriptable objects (similar to SOAP). We could then allow these objects to be used in orders via property fields which could then be triggered for specific game features.
This is similar to just calling another node from one node but would make it more flexible and robust.
Additional context
Checkout how SOAP looks and implements such objects.
The text was updated successfully, but these errors were encountered: