To play a stagger animation only on heavy hits, compare the event damage with the threshold in an Action Condition. Add more conditions to the same group when the action also depends on target state. Test both a passing and a failing case in Play Mode.
A damage event can drive UI, audio, and effects through separate callbacks. Open Game Event Behavior to configure its action list, condition, and schedule. A Receiver Inspector can use its own Action Condition in GES 2.3.0 when that receiver needs a separate rule.
Create a parameterless event for a simple scene response, then use the same asset for the raiser and the callback. Trigger the raiser in Play Mode and check that the callback runs once.
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.
Profile a frequently raised event with its real listeners attached. Measure typed dispatch, condition evaluation, and the callbacks separately so you can identify where the frame time or allocations come from. For an AOT build, use baked evaluators for serialized conditions.
Choose the event signature based on the data a listener needs. Game Event Creator uses the signature to generate concrete Unity types for the event and its Inspector binding. Once Unity compiles them, assign the new event asset to the sender and receiver.
When a player-death event drives both UI and audio, both systems can listen to the same event asset. The asset reference lets you find the senders and listeners before a refactor. Check the serialized callback separately when renaming its method.