5 posts tagged with "Best Practices"

Bind a scene HUD in the Inspector and let spawned enemies register their own callbacks when enabled. Both can reference the same typed event asset. Give each listener an owner so it is clear who configures it and when it is removed.

A persistent audio service needs to hear the level-start event after each scene change. Keep the service GameObject alive, give each level the same event asset, and register the service as a persistent listener. Remove its callback when the service shuts down.

Check the lifetime of every listener and scheduled action attached to an event. Scene objects should remove their own callbacks when disabled, and callbacks that can raise another event should account for paths that lead back to the source.

If a damage event changes health and refreshes the HUD, register both listeners in the same priority tier and give the data update higher priority. Use the listener execution stages to check the order when the event mixes Inspector actions with C# callbacks.

Put related events such as combat hits and defeats in one database, then use categories to split it into smaller groups. The database gives the team a shared place to find the assets and inspect their Behavior before editing a scene.