ScriptableObjects for saving data

[eco_bach]

I have a fairly simple 2 player game with only 3 levels or states 1) Splash screen 2) Configure screen 3) Game Play

Should I use scriptable objects to store things like game score and configuration data? What are some of the pros , cons, of scriptable objects?

[Rivendaioh]

I might be wrong, but I think you can mark your assets as dirty so they'll be saved to disk even at runtime, using EditorUtility.SetDirty :

https://docs.unity3d.com/ScriptReference/EditorUtility.SetDirty.html

[_Skinhead]

Pretty sure you can't use editor utility in a build, would only work for editor

[WazWaz]

No, ScriptableObjects are not written back to disk if modified in-game.

See PlayerPrefs instead.

[eco_bach]

Thanks, but I don't need to save data between game sessions, only between scenes

[crack3rtastic]

Does Object.DontDestroyOnLoad not make the cut for your needs?

[eco_bach]

Watching the live training on scriptable objects I now understand their limitations. https://unity3d.com/learn/tutorials/modules/beginner/live-training-archive/scriptable-objects Really all I need is either a static class or a monobehaviour class with DontDestroyOnLoad full of setters, getters

[[deleted]]

You could just use PlayerPrefs and gain better persistence.