5 posts tagged with "Scripting API"

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.

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.

A generated room can connect its pressure plate to a trap only after the layout is known. Register the connection after creating the room, store the returned handle on the room owner, and remove the connection when that room is discarded.

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.

Give a bomb a fuse by scheduling its explosion with RaiseDelayed. Keep the returned ScheduleHandle so defusing can cancel that exact request. The same handle pattern also works for repeated effects such as poison ticks.