Decoupling Data from Logic with ScriptableObjects

In this lesson, you will learn how to extract static game data from your MonoBehaviour scripts into ScriptableObject assets to create a cleaner, data-driven architecture.

The Problem with Hard-Coded Data

Up until now, you likely stored your game configuration (like movement speeds, health values, or item stats) directly inside your MonoBehaviour classes using serialized fields. While simple, this creates a tight coupling between your logic and your data. If you want to change a value, you have to find the specific GameObject in your scene, modify the inspector, and re-save the scene. Furthermore, if multiple objects share the same data, you end up with redundant values that are difficult to keep synchronized.

Decoupling with ScriptableObjects

By moving this data into a ScriptableObject, you create an independent "data container" that lives as an asset in your project folder. Your MonoBehaviour then simply holds a reference to that asset.

Consider an EnemyData container:

[CreateAssetMenu(fileName = "NewEnemyData", menuName = "Game/Enemy Data")]
public class EnemyData : ScriptableObject
{
    public float movementSpeed;
    public int maxHealth;
    public float attackCooldown;
}

Now, instead of declaring three separate floats and ints in your EnemyController, you do this:

public class EnemyController : MonoBehaviour
{
    public EnemyData stats; // Reference to the asset

    private void Start() 
    {
        float currentSpeed = stats.movementSpeed;
        // Logic remains clean; the data is managed externally
    }
}

Why This Matters

This shift offers three major benefits:

1. Memory Efficiency: All enemies share the same instance of the EnemyData asset in memory rather than each having their own copies.
2. Designer Friendly: You can create multiple variants of an enemy (e.g., "FastEnemyData", "TankEnemyData") by simply creating new assets in the Project window, without ever touching the logic code or needing to create Prefab variants for every single stat tweak.
3. Runtime Flexibility: Because these are assets, you can swap the reference in your EnemyController at runtime, allowing you to change an enemy's behavior profile instantly.

Key Takeaway: By migrating static variables to ScriptableObjects, you transform your logic classes into generic processors that operate on external data assets, making your architecture significantly more modular and easier to balance.