unity-patterns

Use ScriptableObject in Unity when multiple systems need read access to static configuration values, but avoid it for per-run mutable state because changes persist across editor sessions and create hidden coupling between gameplay systems.

Event channels in Unity provide typed, asset-referenced communication that reduces hidden coupling, whereas a global event bus offers broader accessibility but risks spaghetti dependencies. Event channels are recommended when you need explicit routing without singleton overhead.

Object pooling is the best way to manage frequent VFX and enemy spawns in Unity because it pre-instantiates objects and reuses them, eliminating the performance overhead of runtime instantiation and garbage collection spikes during active gameplay.

You need a service layer or interfaces instead of singletons for Unity cross-scene systems when you want testable, decoupled architecture. Singletons create rigid global dependencies, whereas service layers define clear boundaries and improve maintainability.

Over-architecting with state machines in Unity causes maintenance issues when applied to simple logic flows, adding unnecessary abstraction layers. Simpler alternatives like boolean flags or switch statements often suffice for minimal scope before state machines are justified.