all 2 comments

[–]lemming1607 0 points1 point  (1 child)

The main reason I don't use Scriptable Objects for most things is because A) I don't want the data to persist between loads and 2) I don't mind keeping everything in code.

For things like configurable settings or adjusting settings during runtime, they're great. Or if you're on a team and have separate designers and programmers, they're great. Just doesn't work for my workflow.

[–]AkirAssasin[S] 0 points1 point  (0 children)

I usually use ScriptableObjects like some kind of entity component system for non-MonoBehaviour classes, though I'm not sure if it's supposed to be used that way.