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
Just wondering is there a reason that the base SKState class does not descend from scriptable object? I tend to make this change anytime I implement this repo (so that I can serialize and drag and drop states inside unity). Has this ever been considered? I just wanted to bring it up somewhere before sending a pull request for it.
The text was updated successfully, but these errors were encountered:
I personally always prefer to use the highest class up the chain (object in this case). ScriptableObject is a much heavier beast. If you prefer ScriptableObjects it should be as simple as just adding them as a base class just one time when you import StateKit into your project and you're all set.
Just wondering is there a reason that the base SKState class does not descend from scriptable object? I tend to make this change anytime I implement this repo (so that I can serialize and drag and drop states inside unity). Has this ever been considered? I just wanted to bring it up somewhere before sending a pull request for it.
The text was updated successfully, but these errors were encountered: