In this lesson, you will learn how to architect a modular inventory system by decoupling item definitions from their physical representation in the game world.
The Problem with Monolithic Items
In early development, we often store item data directly inside MonoBehaviour scripts attached to game objects. This creates a tight coupling: if you want to change an item’s damage or sprite, you have to find that specific object in a scene. By shifting to ScriptableObject assets, we turn items into "data templates" that exist outside of the scene hierarchy.
Defining the Item Blueprint
We start by creating a base ItemDefinition class. Because this is a ScriptableObject, every unique item (like a Health Potion or Iron Sword) becomes its own file in your Project folder. This allows designers to create new items without writing a single line of code.
[CreateAssetMenu(menuName = "Inventory/Item")]
public class ItemDefinition : ScriptableObject
{
public string itemName;
public Sprite icon;
public int maxStackSize;
// Common properties shared by all items
}
Decoupling Logic from Data
Once we have our definitions, we build an Inventory class—not as a MonoBehaviour tied to a specific player, but as a data container. We use the ScriptableObject Runtime Set pattern (which we covered in previous lessons) to keep track of these items.
By separating the ItemDefinition (the "what") from an InventorySlot (the "where"), your UI can simply subscribe to an event channel. When the player picks up an item, they aren't interacting with a specific GameObject instance; they are simply adding a reference to a ScriptableObject asset into a list. Your UI then refreshes by polling this list, creating a completely decoupled flow where the logic doesn't care if the item is displayed in a backpack, a hotbar, or a shop window.
This architecture ensures that changing an item’s stats updates every system referencing that asset simultaneously, preventing the "duplicate data" bugs common in monolithic systems.
Key Takeaway: By using ScriptableObjects as modular definitions, you decouple your item data from scene-specific logic, allowing your UI and gameplay systems to interact with item assets as interchangeable, project-wide references.