scriptable-objects

ScriptableObject event channels enable decoupled communication between publishers and subscribers in Unity, replacing singletons with serialized asset references that maintain clean separation between gameplay systems without fragile scene-bound dependencies.

Use ScriptableObject data containers to create reusable asset-based configurations for weapons, abilities, and enemies, allowing designers to tune gameplay definitions directly in the Inspector while maintaining a scalable data-driven architecture.

Use ScriptableObject runtime sets to track active enemies dynamically. This pattern avoids circular-reference anti-patterns by maintaining a shared serialized list that gameplay systems can query without tightly coupled component dependencies.

Yes, ScriptableObject runtime state requires lifecycle-safe event subscriptions and explicit state reset handling. Because serialized assets retain values between play sessions, you must manage runtime resets carefully to avoid stale data carrying over.

Use ScriptableObject factory configurations when you need scalable, designer-friendly object spawning workflows. This approach separates spawning logic from data definitions, supporting data-driven architecture for enemies, weapons, and abilities without overextended logic anti-patterns.