unity-patterns

Use ScriptableObjects for shared configuration data that remains static during runtime, while plain C# classes are better for managing mutable runtime state. This separation prevents architectural anti-patterns by keeping data persistence and gameplay logic distinct.

Object pooling is the best way to manage high-frequency spawning in Unity. It pre-instantiates reusable objects, avoiding the performance overhead of transient instantiation and reducing garbage collection spikes during active gameplay.

Choose C# events for simple, localized notifications within a single system, and an observer hub for broader, decoupled communication across multiple systems. The observer pattern prevents tight coupling when many unrelated scripts need to listen to global state changes.

Yes, you can use a state machine for player ability systems to enforce deterministic state transitions. It structures complex ability logic into discrete states, preventing invalid transitions and making the modular configuration of abilities much easier to maintain.

You need a service layer to decouple systems with clear interfaces, whereas singletons often create hidden global dependencies. Choosing a service layer over singletons during refactor decisions reduces unnecessary complexity and prevents architectural anti-patterns.