Help scriptable objects

[paoran983]

I am pretty new to Unity and I am trying to create an object that can hold multiple abilities, which are made using scriptable objects. I want to be able to upgrade these objects and have them gain more abilities. As well as being able to pick up and transfer the item between inventories, which I have set up using scriptable objects, while still keeping the abilities gained from previous upgrades. Should I use scriptable objects to make this object? Or is there a better way of doing this? I’m open to any suggestions

[Kurt-Dekker]

ScriptableObject usage in RPGs:

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…

Creating lookup tables that can be assigned in the inspector.

This looks like a job tailor made for ScriptableObjects! ScriptableObjects are basically structured blobs of predefined data to help you create content for your game. For instance if I had a ScriptableObject called Weapon, it might have these properties: name detailed name description damage toughness weight what it looks like in the inventory what model it uses in game what animations the player uses to swing it I would create many of these Weapons, each one a file on disk (also called an…

[spiney199]

There was some discussion on this here: Best practices for managing large amounts of ScriptableObject data?

If you intend for your abilities to be mutable, then they would be better as plain C# objects, with scriptable objects as factories for said abilities. A container for said abilities/upgrades could also be a plain C# object, which should make saving the current state of abilities to disk easier then. Then that container object can just be used in a monobehaviour.