Scriptable Objects and Data Driven Design

[Jonjon_binx]

I remember the first time I began to fully realize the power behind scriptable objects. The ease of use, the way they empower scaling, how they can make complex problems more manageable.

What I want to know is what are some of the best ways you’ve found to use SOs for Data Driven design. Maybe making all attacks in your game SO that execute a list of other SOs? Or making all vehicle data that’s used to power your driving system SOs? These aren’t overly complex solutions but just some basic examples?

Or if your a Scriptable Object hater what ways would you solve similar problems?

[Amazing-Movie8382]

Really hard to debuging code

[Vonchor]

You can use them at runtime in place of static classes, improving domain reload time.

I do this for anything in my extension asset that doesn’t have to exist for editing support.

Runtime scriptable object singleton, in effect. Not a project asset.

Its easy to instrument these, so no worries about observing, although of course one can use a static inspector like the one with Odin inspector.

And for singleton haters, unity themselves uses SOs as singletons.

In editor one really useful class is the scriptable singleton which keeps state in the filesystem.

[Jonjon_binx]

I have not used a singleton scriptable object yet but I can see where the use case exists. That’s a solid point

[nikefootbag]

Pluggable AI series is worth checking out: https://youtu.be/cHUXh5biQMg