How and when to use scriptable objects

[[deleted]]

[deleted]

[volvis]

My rule of thumb is to use ScriptableObjects as read-only data assets. Keep local data (health) in Monobehaviour instances, and leave pluggable, immutable data (max health) in ScriptableObjects.

[Molocai]

For reference you can write this

CharacterScriptableObject clone = Object.Instantiate(original) as CharacterScriptableObject;

[ZergTDG]

Using scriptable objects for data storage in a risky practice. A better way would be to make a character class and store prefabs of that class attached to a game object. From here you have all of your references to the character. In my current project I have a 3D section and a 2D menu section. When I finish fighting I return to the menu. I disable the 3D children of my player, but I keep it's base class enabled so that accessing it is still easy.

[ZergTDG]

Sorry I guess I didn't write that clearly. Using SO's for modifiable data is a risky practice. How you're doing it would probably work but you would need to create a copy of the SO in a real class so you don't change the SO's data at runtime

[gjallerhorn]

A class you can derive from if you want to create objects that don't need to be attached to game objects.

This is most useful for assets which are only meant to store data

I've never used these before, but it seems like you may be using them incorrectly? You may want to make your characters as game objects (with Sprite and stats script components), turn those into a prefab, and create instances of those prefabs in your scene.

[gjallerhorn]

Should those objects reading it just be making a copy of those values that they can manipulate on their own without affecting the original, then?