game-unity-specialist

Create a ScriptableObject event channel containing a UnityEvent, then add GameEventListener MonoBehaviours that subscribe to it. Systems raise events through the channel without direct references, which is the pattern used in shipped games like Hollow Knight.

Use DOTS when you have thousands of similar entities, need deterministic simulation, or profiling proves CPU is the bottleneck. For fewer than a few hundred entities or rapid prototyping, MonoBehaviour is faster to write and debug.

Default to URP for new projects since it targets mobile, Switch, VR, and mid-range PC and is Unity's actively developed pipeline. Choose HDRP only for high-end PC or console titles needing ray tracing and volumetrics, and decide before production starts.

FindObjectOfType and GameObject.Find scan the entire scene at runtime, causing frame spikes and hidden coupling. Use serialized references, dependency injection, or ScriptableObject event channels instead, and cache GetComponent results in Awake.

Use Addressables with AssetReference fields and InstantiateAsync for async loading, grouping assets with labels for preloading. Always release handles with Addressables.Release when done, since leaked handles are the most common Addressables memory bug.

Avoid rewriting working UGUI interfaces mid-project, and keep UGUI for world-space UI or heavy TextMeshPro dependencies. UI Toolkit is the right choice for editor extensions and runtime UI in new projects, especially with Unity 6 data binding.