Changing a Scriptable Object's Variables without effecting other instances.

[Kurt-Dekker]

You can use ScriptableObject.CreateInstance<>(); to create an instance to use.

It’s not optimal however, as you are conflating the idea of ScriptableObjects (authored when making the game) with runtime data.

I actually just wrote a big post about it here:

ScriptableObjects for an RPG with multiple units in your team

The most important concept about ScriptableObjects (SOs) is that they are custom-shaped blobs of data that you can edit inside the Unity inspector. The serialized values inside a SO map directly to that created asset on disk, the instance of the SO. When your game runs, it needs some data. One way to get that data is to hard-code it in the code. That is bad because when you change it, you need to change code. That’s why we have things like a SO to configure existing unchanging shipped code. W…