DCEnemyDetected (0)
The first enemy detected. Never generated again while already in Combat behaviour.

NoteThe seen behavior might not be a bug. Maybe it is only a misunderstanding of the provided description.

ObsThe AI notices a threat and switches to combat behavior.The AI can no longer see the threat after it has moved.The AI now hears the same threat moving (for the AI it could be a new/different threat though).

This triggers a new DCEnemyDetected event despite the AI still being in combat behavior (as seen by its stance).

When the threat stops and moves again to generate a newnoise, a new DCEnemyDetected event is created each time for the AI.

ExpAs per the description I would expect max one DCEnemyDetectedevent as long as the AI is in combat behavior.

Only once it leaves the combat behavior, a new threat is to triggera new one.

That said without this info from a behavior perspective the seenbehavior makes sense - each new threat first spotted triggers it.

Repro

Load the addon along for danger FSM event analysis

Load the attached demo mission in the editor

Walk sideways to right side for the AI to see you

Walk left again behind the wall so that the AI no longer sees you

Stop your movement

Now do a sidestep and notice a new DCEnemyDetected event getting triggered

The AI is considered as in combat behavior as long as it does not returnto the relaxed stance.

Now do a sidestep and notice a new DCEnemyDetected event getting triggered

Strange. I cannot see this problem on my end. To me the DCEnemyDetected is never sent again to the same unit unless I wait long enough for the enemy AI to stand up (return to Aware behaviour), which takes about 5 minutes.