unity-scripting-advanced

Define an abstract State class with Enter, Update, and Exit methods, then a StateMachine MonoBehaviour that calls ChangeState to transition between states. Concrete states like IdleState check conditions such as PlayerInRange and trigger transitions to ChaseState.

Create a ScriptableObject class with CreateAssetMenu to define data assets like WeaponData containing damage, fire rate, and prefab references. Controllers then reference these assets, keeping data decoupled from scene objects and editable in the Inspector.

Use a generic ObjectPool<T> class that pre-instantiates a queue of inactive objects, dequeues them on Get(), and re-enqueues on Return(). Enable allowGrowth to expand the pool at runtime and log pool stats to monitor active versus pooled counts.

The patterns work in any Unity project, but AI-assisted code generation features require unity-mcp connected to the Unity Editor plus Visual Studio or Rider. Without unity-mcp, you can still apply the C# architecture patterns manually.

GameEvent listeners must register in OnEnable and unregister in OnDisable, and the ScriptableObject event asset must be assigned in the Inspector. Check that Raise() is actually invoked and add debug logs to confirm listener registration counts.

Memory leaks occur when active objects are destroyed instead of returned to the pool. Always call Return() to deactivate and re-enqueue objects, and use the LogPoolStats context menu to verify active and pooled counts stay balanced.