They are not stored in the scene, but in the assets folder (like models, textures, script files etc).

Hey guys, I'm getting errors in my build when I try to use my scriptable objects.

But honestly SO can do everything (almost) monobehaviours can so.. or rather, they can store methods, variables, and data.

No need to attach scriptable objects to the game objects. Creating a scriptable object To create a scriptable object, we start with creating a C# script that derives from ScriptableObject class instead of the MonoBehavious class. They are special assets which is meant to store data. I use Scriptable Objects a lot, but only use them to store dynamic data when I know the number of instances before, e.g. Get this panel and finalize the object after selecting the script for it. Scriptable Objects are amazing data containers. Stay organized by creating a folder under your Scripts folder called Scriptable Objects, and then another folder inside of the Scriptable Objects folder called Sword Data. When each of the enemies in the scene has unique properties, then moving those properties to scriptable objects is unlikely to have any benefit. I noticed that GUISkin is a scriptable object, so I thought maybe I could use ScriptableObject to create assets that exist in the project view, of which the properties can changed there and taht can then be dragged on the relevant properties in scripts that use … Scriptable Objects. Scriptable objects make the game more dynamic with much ease. technically you could make a game with scriptable objects only and one monobehavior script (or few) that will read and write data from/to there. The real power comes from manipulating data in the editor outside of Play Mode, and for that we need to add the CreateAssetMenu … An Asset may come from a file created outside of Unity, such as a 3D model, an audio file or an image. Scriptable objects are containers of variables mostly. Say for example you have a weapon, you can use a Scriptable object to keep the stats of each weapon. So if you want to re-use the tool to perform some action in the editor at a later date (after you have closed and reopened Unity), you have to re-configure the tool. A other use is to keep data for instanced enemies to share. Scriptable objects are the data containers which allows you to store the large amount of independent shared data. Im already using ScriptableObject for item database its great for that. Scriptable objects are data containers, but at the same time allow to plug/connect assets and data. They don't need to be attached to a GameObject in a scene. It's free to sign up and bid on jobs. With the use of scriptable objects, one can save a lot of different presets for gameObject(s) that too in very little space. With scriptable objects, this can be done very easily by just replacing the existing scriptable object with a new one. Inside the newly created Sword Data folder, create your first Sword Data asset. They can be saved as assets in our project. Scriptable objects are useful when you have certain tuples of data which you want to be able to maintain separately and assign to many different objects.