Full FAQ
The full team document, in 16 sections by module.
1. Overview#
The enemy AI is a rule-based system written entirely in C++, with no Behavior Tree or StateTree assets. The guard (AAIEnemy) perceives and decides, the controller (AAIEnemyController) acts, and the level's enemy subsystem (UAIEnemySubsystem) hands sounds, evidence, lights and witnessed events to every guard.
Sounds, evidence and witnessed events all go to the subsystem first, which hands them to every guard. Sight is the guard checking for itself, every frame.
What parts make up the AI?#
| Part | Class | Lives on | What it does |
|---|---|---|---|
| Guard | AAIEnemy | Parent class of the Guard Blueprint | Sight, hearing, evidence, Awareness and alert state, capture, knockout, death, and all the Blueprint events |
| Behavior controller | AAIEnemyController | Possesses the guard automatically | Patrols, investigates, searches, chases and returns based on the alert state; runs card-forced fights |
| Enemy subsystem | UAIEnemySubsystem | One per level, created automatically | Broadcasts sounds, holds the evidence pool, answers light queries, handles witnesses and Belief, relays Ghost Score events, finds guards by radius |
| Emotion | UEmotionComponent | Built into every guard | Current emotion, the flicker on change, the cooldown after a steal |
| Decision | UEnemyMLDecisionComponent | Built into every guard | Where to go while searching or hunting, by rule or ML |
| Light | UAILightComponent | Lights | Marks areas that can go dark, reports evidence when the light goes out |
| Evidence | UAIEvidenceComponent | Items that can be taken | Reports “item missing” when the item is taken |
| Player noise | UStealthNoiseComponent | Player | Noise from footsteps and actions |
| Stealth package | UStealthMovePackage | Player (optional) | Crouch and sprint, kill, steal emotion, invisibility and test keys |
| Score | UGhostScoreComponent | Player (optional) | Turns the guards' events into points |
| Machine learning | The EnemyML classes | Training maps | Training arena, bot player and statistics |
Where are the code and assets?#
- All C++ lives in Source/ProjectKangaroo/. File names are the class names without the prefix, such as AIEnemy.h and AILightComponent.h; the AI Evidence component is in AIEvidence.h.
- Guard Blueprint: /Game/Benjamin-AI/Enemy/Guard.
- Test level: /Game/Benjamin-AI/LV/LV_AITest, see section 14.
- Invisibility material: /Game/Benjamin-AI/Materials/M_StealthInvisible.
What happens each frame?#
- The guard's Tick checks whether it can see the player, updates Awareness and the alert state, checks for a capture, and scans for evidence every 0.25 seconds.
- The controller's Tick picks a behavior for the alert state, issues path requests and turns the guard toward what it should look at.
- Sounds and witnessed events are events, not Tick work. Whoever makes one calls the subsystem, which hands it to every guard right away.
Which numbers does this doc use?#
All numbers are the C++ defaults. The Guard Blueprint or a placed instance may override them, so trust the Details panel. The guard's settings are grouped under AI categories there, such as AI | Perception and AI | Behavior.
2. Getting started: putting a guard in a level#
Drag the Guard Blueprint into a level and make sure there is a navmesh under it, and it stands guard on its own; give it a few patrol points and it patrols. Everything else is automatic.
What is the minimum setup?#
- Drag /Game/Benjamin-AI/Enemy/Guard (or any Blueprint based on AAIEnemy) into the level. The controller possesses it automatically, so there is no need to set AI Controller Class.
- A NavMeshBoundsVolume must cover the area the guard moves in, and the navmesh must be built (press P in the viewport to see the green area). Without a navmesh the guard won't move, and a red MoveTo failed diagnostic appears in the top-left of the screen.
- The level needs a player. By default the guard watches player 0's pawn.
How do I make a guard patrol?#
Place a few actors as patrol points (Target Points work well), then set these under the guard's Details → AI → Behavior:
- Patrol Points: add the points in order.
- Loop Patrol: on goes back to the first point after the last one; off walks the same path back.
- Patrol Wait Time: seconds to wait at each point, default 2.
- Patrol Speed: patrol speed, default 200 cm/s.
What if there are no patrol points?#
With Random Patrol Radius at 0 (the default), the guard stands guard at its spawn point, facing its spawn direction. Above 0, it wanders to random points within that radius of its spawn point.
Where is the guard's post?#
Wherever it stood, and whichever way it faced, when the controller possessed it. After an investigation or a chase, a guard with patrol points walks to the nearest one and carries on patrolling; a guard without them returns to its post.
Do guards spawned at runtime work?#
Yes. The guard's Auto Possess AI is Placed In World Or Spawned, so spawned guards are possessed too.
Can I pause a guard?#
Yes. Turn on Behavior Paused on the controller and the guard stands still, with no patrol and no chase, which is handy for cutscenes. Perception keeps running, so Awareness can still rise. In Blueprint, get the controller with Get AI Controller → Cast To AIEnemyController.
Where are the settings?#
Categories in the guard's Details panel:
- AI | Perception: sight, Awareness, alert sharing, capture range.
- AI | Perception | Light: how light changes sight.
- AI | Perception | Reactions: how the guard reacts to noise, evidence and warnings.
- AI | Behavior: patrol, speeds, turning, confirm time.
- AI | Emotion, Knockout, Fight Anim, Death: emotion, knockout, fight animations, death.
- AI | Debug: debug drawing.
Search radius, arrival radius and similar settings are on the controller, see section 8.
3. Sight#
A guard sees the player only when three things are true at once: the player is within range, inside the horizontal cone, and nothing blocks the line between them. The default range is 1500 cm with a 45° half-angle, a 90° wedge in front; light changes both values, see section 7.
How exactly is it checked?#
- Distance: the straight-line distance from the guard's eyes (capsule center plus Base Eye Height) to the player's capsule center is within range.
- Angle: horizontal only. The horizontal angle between the guard's forward direction and the player is within the half-angle. A player directly above or below counts as inside.
- Occlusion: a Visibility-channel trace runs from the eyes to the player's center. It only counts as seen if the trace hits the player, or something attached to the player.
Settings#
| Setting | Default | What it does |
|---|---|---|
| Sight Range | 1500 cm | Range when both the guard and the target are lit |
| Sight Angle | 45° | Half-angle of the cone; the full opening is twice this |
| Turn Rate | 360°/s | How fast the guard turns; the cone turns with the body |
| Target Override | Empty | When set, the guard watches this pawn instead of player 0 |
Why does the player get seen behind a low wall?#
Occlusion checks one line only: eyes to the player's capsule center. If low cover doesn't block that line, it doesn't count. Crouching makes the capsule shorter and its center lower, so low cover blocks it more easily.
What blocks sight?#
Any collision set to Block on the Visibility channel, such as walls, pillars and crates. For things guards should see through, like glass, fences or grass, set their Visibility response to Ignore.
Does the cone follow the head or the body?#
The whole actor. A moving guard faces where it walks; a stopped guard faces its focus point (the spot it's investigating, the player, its post direction) and turns there smoothly at Turn Rate. Head animation doesn't affect the check.
Who is the guard watching?#
Player 0's pawn by default; Get Perception Target tells you. When Target Override is set, it watches that pawn instead, which is how the ML arena points guards at its bot. A guard watches one target at a time.
How do I make the player completely undetectable?#
Add the tag InvisibleToAI to the player actor. An actor with this tag:
- can't be seen, and any noise it makes is ignored;
- can't be captured;
- has no witnesses for what it does, such as stealing emotions or killing. A body it leaves behind is still evidence.
Add or remove the tag any way you like, for example by editing the actor's Tags in an ability. The Blueprint node Is Actor Invisible To AI checks it.
What happens once the guard sees the player?#
- It records the player's position every frame (Last Known Player Location), and Awareness starts rising, see section 4.
- On Player Spotted fires on the frame the player becomes visible; On Player Lost fires when the player is lost.
- Seen Time counts continuous sight, which is used for “confirm before chasing”.
What does the cone from Draw Debug show?#
The range and half-angle being used right now to check the player, with light at both the guard and the player already applied. Red means the guard sees the player, yellow means Suspicious, green means anything else. An Alerted guard that has lost sight of the player is also green. The cone is drawn in 3D, but the check only uses the horizontal angle.
4. Awareness and alert states#
A guard's state comes from one Awareness value between 0 and 1: at 0.3 it becomes Suspicious and goes to check, at 1 it becomes Alerted and goes for the player. Awareness rises by 1.0 per second while the player is visible, so by default 0.3 seconds of continuous sight makes a guard suspicious and 1 second alerts it.
Settings#
| Setting | Default | What it does |
|---|---|---|
| Awareness Gain Rate | 1.0 /s | How much Awareness rises per second while the player is visible |
| Awareness Decay Rate | 0.5 /s | How much it falls per second when nothing is perceived |
| Suspicion Threshold | 0.3 | Suspicious at or above this |
| Alert Threshold | 1.0 | Alerted at or above this |
| Alert Duration | 5 s | After going Alerted, how long it holds with nothing perceived before falling |
| Suspicion Duration | 8 s | After a noise, evidence or a warning makes it Suspicious, how long it holds before falling |
| Chase Delay | 1 s | How long an Alerted guard must keep the player in sight before it chases |
What do the three states mean?#
- Unaware: normal patrol or standing guard.
- Suspicious: something is off. The guard goes to check the suspicious spot and searches nearby.
- Alerted: it knows someone is there. It chases if it can see the player, and hunts at the last known position if it can't.
The state comes only from Awareness, and it falls back one step at a time: Alerted → Suspicious → Unaware. On Alert State Changed(Old, New) fires on every change.
Does one glimpse alert the guard?#
No. By default it takes about 0.3 seconds of continuous sight to become suspicious and 1 second to be alerted. Once sight breaks, Awareness falls by 0.5 per second. Raise Awareness Gain Rate for sharper guards.
Why are noises and evidence only Suspicious?#
They are indirect clues, and the default reaction to them is Suspicious: Awareness rises to at least 0.3 and holds for Suspicion Duration (8 seconds), so the guard has time to walk over. Every new clue restarts the 8 seconds. An Alerted guard is never pulled back to Suspicious.
You can change the reactions to Alerted under AI | Perception | Reactions: Noise Reaction, Evidence Reaction and Shared Alert Reaction.
How long does an Alerted guard take to calm down?#
After the last thing it perceived, it holds Alerted for 5 seconds. Then Awareness falls by 0.5 per second and drops below 0.3 about 1.4 seconds later, back to Unaware. If some suspicion hold time is still left, it stays Suspicious until that runs out.
If the guard is still searching when it reaches Unaware, it finishes the search first (see section 8) and then goes back to its post.
What is the confirm time (Chase Delay) for?#
Alerted only means the guard is sure someone is there. Before chasing, it stops and watches the player for Chase Delay (1 second) of continuous sight; this behavior is called Spotting. Losing sight resets the timer, and 0 means chase on sight.
Continuous sight (Seen Time) starts counting the moment the guard sees the player, whatever its state. So a guard that watches from zero all the way to Alerted usually already has enough and chases straight away. A guard that was alerted some other way first, such as a witnessed event or a noise, visibly stops to stare when it then sees the player.
How do Blueprints change Awareness?#
- Add Awareness / Set Awareness: add to it or set it directly; the state updates at once.
- React To Stimulus(Suspicious / Alerted): raise it by the indirect-clue rules; Suspicious includes the 8-second hold.
- Set Known Player Location: tell the guard where the player is without changing Awareness.
- Reset Perception: clear all memory and return to Unaware, handy for a new round.
How do I read the bar over a guard's head?#
With Draw Awareness Bar (or Draw Debug) on, the guard shows:
- Thick bar: Awareness. Green, yellow and red for the three states; the two white ticks are 0.3 and 1.0.
- Thin orange bar: confirm progress after seeing the player (Seen Time / Chase Delay); red when full.
- Thin white bar: how much longer a knocked-out guard stays down.
- Thin cyan bar: how much pacify time is left after an emotion was stolen.
5. Hearing and noise#
Hearing has one rule: a guard hears a sound when it is within the sound's radius of the source, with no line of sight needed. The default reaction is Suspicious, and the guard walks over to check where the sound came from, which is the source, not where the player is now.
Where do sounds come from?#
Sounds never happen on their own; something has to report them to the subsystem:
- The player: use the Stealth Noise component. The formal project's player Blueprint, BP_ThirdPersonCharacter, already has one. It never makes noise by itself: the player Blueprint calls Make Walk Noise, Make Sprint Noise, Make Crouch Noise, Make Movement Noise(state) or Make Noise(radius, tag) at the right moments.
- Anything else (doors, a thrown bottle, an alarm): Get AIEnemySubsystem → Report Sound At(location, radius, instigator, tag, wall attenuation), or Report Sound with a sound struct.
- To find out who heard it: Report Sound With Feedback returns the guards that heard it; the Stealth Noise nodes return how many did.
How loud is the player by default?#
| Action | Node | Radius |
|---|---|---|
| Walking | Make Walk Noise | 500 cm |
| Sprinting | Make Sprint Noise | 1400 cm |
| Crouching | Make Crouch Noise | 0 (silent) |
| Anything else | Make Noise | Set in the call |
Change these on the Stealth Noise component. While the player has the InvisibleToAI tag, none of the nodes make noise.
Do walls block sound?#
That depends on wall attenuation. A trace runs from the source toward each guard, and for every wall it passes, the remaining distance is multiplied by (1 − attenuation). Characters don't count as walls.
- 0: goes through walls completely. Report Sound At defaults to 0.
- 0.5: each wall halves what is left. Stealth Noise's Noise Wall Attenuation defaults to 0.5.
- 1: a single wall blocks it completely.
What does a guard do when it hears something?#
- Remembers where the sound came from (Last Heard Sound Location).
- Reacts with Noise Reaction: Suspicious by default, raised to 0.3 and held for 8 seconds. It can be set to Alerted instead.
- Fires On Sound Heard.
- The controller walks to the source and searches nearby once there.
Pacified, knocked-out and dead guards hear nothing.
Footsteps are reported every frame. Is that a problem?#
Not for scoring: each guard reports Noise Heard once per alert cycle, and again only after it is back to Unaware. But every sound it hears updates the source position and restarts the 8-second suspicion hold, so constant noise keeps a guard investigating.
How do I hook up footsteps?#
Two common ways: call Make Movement Noise from a footstep Anim Notify, or decide by speed in Tick. The editor function Wire Stealth Noise Footsteps (category Project Kangaroo | Editor Tools) wires the Tick version into a character Blueprint for you. While moving on the ground, it makes crouch noise when crouched, sprint noise above 450 horizontal speed, and walk noise otherwise.
How do I see a sound's reach?#
Turn on Draw Debug on the Stealth Noise component. Each noise draws an expanding ring where it was made, at most as big as its real reach after wall attenuation, and every guard that heard it gets a line to the player. Walking is orange, sprinting red, crouching a small green ring.
6. Evidence, witnesses, Belief and alert sharing#
Evidence is a clue that makes a guard suspicious and come to check, such as a missing item, a body or a light that went out, and it never affects Belief. Witnessing means a guard saw the player do something wrong: witnesses go straight to Alerted, warn nearby guards, and add to Belief based on how many saw it.
What kinds of evidence are there?#
| Type | Reported by | Meaning |
|---|---|---|
| Item Missing | The AI Evidence component on an item, automatically when the item is destroyed | Something is gone |
| Body | A guard, automatically when it dies | A body, permanent |
| Light Off | The AI Light component, automatically when the light goes out | A light went out, see section 7 |
| Custom | Your Blueprint | Any custom clue |
To report evidence from Blueprint: Get AIEnemySubsystem → Report Evidence At(type, location, lifetime, source object), which returns an Id. Report Evidence takes the full struct for finer settings, and Remove Evidence(Id) withdraws it. A lifetime of 0 means permanent.
When does a guard notice evidence?#
Every guard checks the evidence pool every 0.25 seconds (Evidence Scan Interval). It needs both:
- The evidence is within its Notice Radius (default 1200 cm).
- If the evidence requires line of sight (the default), its location is inside the guard's cone and not blocked. A trace that hits the evidence object itself counts as seen. Evidence in the dark is likewise only seen up close.
Evidence with an Auto Notice Radius is noticed without looking by guards closer than that; light evidence works this way. Each guard notices a piece of evidence only once, but different guards notice it separately.
How do I make guards notice a missing item?#
Add an AI Evidence component to the item actor and keep Report When Owner Destroyed on. When the item is destroyed, for example taken by the player, an Item Missing is reported where it was.
You can also call Report Change, Report Change At or Report Change Of Type yourself, and Retract Last Change when the item is put back.
What does a guard do when it finds evidence?#
It remembers the location and type, fires On Evidence Found, then reacts with Evidence Reaction. That is Suspicious by default, so it goes to check. Evidence never adds to Belief.
What are witnessable events?#
Three for now:
- Emotion Stolen: reported automatically by the guard's Steal Emotion.
- NPC Killed: reported automatically by the guard's Report Killed.
- Restricted Area Sighting: seen somewhere the player shouldn't be. How restricted areas are defined isn't decided yet, so Blueprints report it.
Report one from Blueprint with Get AIEnemySubsystem → Report Witnessable Event At(type, location, instigator, victim). The returned record lists the witnesses and how much Belief was added.
Who counts as a witness?#
At the moment of the report, every guard that is alive, conscious and not pacified checks whether it can see the event location. It uses the same cone, trace and light rules as for seeing the player, and those that can see it are witnesses. The victim never counts, and an instigator with the InvisibleToAI tag has no witnesses at all.
What do witnesses do?#
They take the instigator's position as the player's position, jump straight to Alerted, warn nearby guards (alert sharing, below) and fire On Event Witnessed.
How is Belief calculated?#
It is added only when someone witnessed the event; no witnesses, nothing added. The amount is the base value × (1 + (witnesses − 1) × 0.5), and the total is capped at 1.
| Event | Base | 2 witnesses | 3 witnesses |
|---|---|---|---|
| Emotion Stolen | 0.2 | 0.3 | 0.4 |
| NPC Killed | 0.5 | 0.75 | 1.0 |
| Restricted Area Sighting | 0.1 | 0.15 | 0.2 |
Belief doesn't change guard behavior by itself; it is there for other systems to read. Read and write it with Get Belief, Set Belief and Add Belief, listen with On Belief Changed and On Event Witnessed, and get every record with Get Witness Records. The base values and the factor live on the subsystem and can be changed from Blueprint at runtime.
How does alert sharing work?#
When a guard calls Share Alert, it sends the newest clue location it knows to every guard within Alert Share Radius (default 2000 cm).
- When it happens automatically: only on witnessed events for now. A guard that goes Alerted by seeing the player doesn't warn anyone on its own; call Share Alert from On Alert State Changed if you want that.
- Guards that receive it remember the location, react with Shared Alert Reaction (Suspicious by default, so they go and check) and fire On Alert Received.
- The guard that sends it fires On Alert Shared(number notified) and reports an Alarm Raised Ghost Score event.
- Set Alert Share Radius to 0 to never warn others.
7. Lights and darkness#
A spot is dark when an AI Light covers it and every AI Light covering it is off. Guards see only a short, narrow way into the dark, while a guard standing in the dark sees lit targets farther and wider; when a light goes out, nearby guards also come to check.
How does light change sight?#
| Guard | Target | Range | Half-angle | Setting (range / angle multiplier) |
|---|---|---|---|---|
| Lit | Lit | 1500 cm | 45° | Sight Range / Sight Angle |
| Lit | Dark | 225 cm | 18° | Light To Dark Sight (0.15 / 0.4) |
| Dark | Lit | 1950 cm | 67.5° | Dark To Light Sight (1.3 / 1.5) |
| Dark | Dark | 300 cm | 22.5° | Both Dark Sight (0.2 / 0.5) |
The multipliers are under the guard's AI → Perception → Light: Range Scale multiplies the range, Angle Scale the half-angle. The same rules apply to seeing evidence and witnessed events. To get the sight toward a spot right now, call the guard's Get Effective Sight(target location).
How do I add AI Light to an existing level?#
- Lamps based on BP_LightParent (recommended): open Content/Blueprints/Lights/BP_LightParent → Components → Add → AI Light, then compile and save. Every instance and child class in every level gets it. It is a shared asset, so check it out in P4 first and let its author know.
- Lights placed directly in the level: select the light actor → Details → + Add → AI Light. Lights that switch at runtime should be Movable or Stationary.
- Areas that start dark: place a light with Visible unchecked and add an AI Light to it. Or add an AI Light to an empty actor, untick Start On, and set Radius to the size of the area.
Guards need no setup.
How do I turn a light off so guards notice?#
Every 0.1 seconds the AI Light checks the light components on its actor; the light counts as on while any of them is visible with intensity above 0.
- Detected: Set Visibility(false) or Set Intensity(0) on the light component, or the AI Light's own Turn Off, Toggle or Set Light On.
- Not detected: dimming without reaching 0, Set Actor Hidden In Game, turning the light color black, or destroying the light actor. A destroyed light counts as no light at all, so its area becomes lit.
- Turn it back on the same way you turned it off. If Turn Off switches it off (it changes Visible) and Set Intensity switches it back on, the light stays dark.
- The formal project's snuff ability, GA_Snuff, uses Set Intensity; make sure it sets 0.
How big is the dark area?#
- A sphere around the light with radius Radius. A Radius of 0 uses the light's Attenuation Radius.
- It is checked at a character's capsule center, about 90 cm above the floor. The higher a light hangs, the smaller its circle on the floor; once its height minus 90 cm exceeds Radius, it covers no floor at all.
- The sphere goes through walls, so a light with a large attenuation radius leaks darkness into the next room.
- Spots that no AI Light covers are always lit. Where lights overlap, one lit light keeps the spot lit.
- Turn on Draw Debug on the AI Light to see its circle on the floor in PIE: yellow when on, dark blue when off. Radius can be set per instance in the level.
What happens when a light goes out?#
A Light Off piece of evidence appears at the light. It expires after 15 seconds by default (Evidence Lifetime), and turning the light back on removes it at once:
- Guards within Radius of the light notice right away, without looking.
- Guards within 2 × Radius (or Notice Range) that can see the light notice it too.
They react with Evidence Reaction, Suspicious by default, so they come to check. To keep guards away, untick Investigate When Turned Off on the AI Light.
Which Blueprint nodes are there?#
- AI Light component: Turn On, Turn Off, Toggle, Set Light On, Is Light On, Get Light Radius, and the On Light Changed event.
- Subsystem: Set Lights In Radius (switches an area and returns how many changed), Is Location Dark, Get Light Level At, Has Any Light Off, Get All Lights.
- Guard: Get Effective Sight, Get Sight For Light.
8. Behaviors: patrol, investigate, search, chase#
The controller picks every behavior from the alert state. Unaware patrols or stands guard; Suspicious goes to the suspicious spot and searches around it; Alerted chases after confirming when it can see the player, or hunts at the last known position when it can't. Each change fires the guard's On Behavior Changed(Old, New), handy for switching animations or expressions.
Green, yellow and red match the three alert states, the same colors as the awareness bar over a guard's head. Search happens in both Suspicious and Alerted.
Which behaviors are there?#
| Behavior | When | What it does | Speed (cm/s) |
|---|---|---|---|
| Patrol | Unaware, with patrol points or a random patrol radius | Walks the patrol points in order, waiting Patrol Wait Time at each | Patrol Speed 200 |
| Stand Guard | Unaware, no patrol points | Goes back to its post and faces its spawn direction | Patrol Speed 200 |
| Investigate | Suspicious | Walks to the newest suspicious spot, looking at it | Investigate Speed 320 |
| Search | After reaching the suspicious spot or the hunt target | Picks nearby points, walks over and pauses to look at each | Search Speed 200 |
| Spotting | Alerted and can see the player, Chase Delay not reached yet | Stops and stares at the player | Stands still |
| Chase | Alerted, can see the player, confirmed | Runs at the player | Chase Speed 520 |
| Hunt | Alerted but can't see the player | Goes to the newest clue, then searches | Chase Speed 520 |
| Return | Back to Unaware | Forgets every clue and returns to the nearest patrol point or its post | Patrol Speed 200 |
| Fight Allies | Card-forced state | Attacks the nearest guard, see section 9 | Chase Speed 520 |
| Unconscious | Knocked out | Lies still | Stands still |
| Idle | Just possessed, dead or paused | Does nothing | Stands still |
How is the “suspicious spot” chosen?#
A guard remembers three kinds of clue: the last known player position (including warnings and witnessed events), the last evidence it found, and the last sound it heard. It goes to whichever is newest; Get Point Of Interest and Get Point Of Interest Source tell you which.
If a new clue appears more than Retarget Distance (150 cm) from the current target during an investigation, the guard changes course at once. During a search, a new clue farther than the search radius plus 150 cm from the search center makes it drop the search and go there.
How long does a search last?#
- While Suspicious or Alerted: it keeps searching, with no time limit.
- On dropping back to Unaware: a search lasts at least Search Duration (8 seconds) in total, so if that isn't up yet, it finishes before returning.
At each point it pauses for Search Look Time (1.5 seconds) before moving on. The decision component picks the next point; the rule version picks a random reachable point within Search Radius (400 cm) of the search center. With no navmesh nearby, the guard looks around where it is and tries again a little later.
How does a guard turn?#
While moving it faces where it walks. Below 20 cm/s it faces its focus point instead: the investigate spot, the player, the search point or its post direction. Either way it turns smoothly at Turn Rate (360°/s), and while fighting it always faces its opponent.
Where do I change arrival radius, search radius and so on?#
On the controller. The controller is created at runtime, so to change its defaults, make a Blueprint based on AIEnemyController and set the guard's AI Controller Class to it.
| Setting | Default | What it does |
|---|---|---|
| Patrol Acceptance Radius | 80 cm | Arrival radius for patrol and return |
| Investigate Acceptance Radius | 100 cm | Arrival radius for investigate and search |
| Retarget Distance | 150 cm | How far a new clue must be from the current target to change course |
| Nav Projection Extent | 250, 250, 300 cm | Search box for snapping target points onto the navmesh |
| Search Radius | 400 cm | Radius for picking random search points |
| Search Duration | 8 s | Minimum search time |
| Search Look Time | 1.5 s | Pause at each search point |
| Chase Acceptance Scale | 0.5 | Chase arrival radius is Capture Range times this |
Can Blueprints direct a guard?#
Yes. Get the controller with Get AI Controller → Cast To AIEnemyController, then:
- Request Investigate(location): send the guard to look at a spot. It raises Awareness to Suspicious with the 8-second hold, and is ignored while Alerted.
- Return To Patrol: drop whatever it is doing and go back to its post.
- Reset Behavior: stop everything and treat the current location as the new post. Use it after teleporting a guard.
- Behavior Paused: pause behavior, see section 2.
The guard itself also has Set Move Speed for a temporary speed change, but the next behavior change sets the speed for that behavior again.
9. Capture, knockout, fights and death#
Guards only capture while Alerted: within Capture Range (150 cm) of the player a capture event fires, and what happens next is up to Blueprint. Guards can also be knocked out (10 punches by default), forced by a card to fight each other, or killed, leaving a body behind.
When does a capture happen?#
When all of these are true at once:
- The guard is Alerted.
- The straight-line distance to the player is within Capture Range.
- The guard isn't dead, knocked out, or in a card-forced state.
- The player doesn't have the InvisibleToAI tag.
Capture doesn't check line of sight, so a guard can capture through a thin wall.
What happens on a capture?#
C++ only fires events; it doesn't end the game. While the conditions hold, two things fire every frame: the On Player Captured event in the guard Blueprint, and the bindable On Captured Player delegate (guard, player). Whatever listens should guard against handling it twice, for example with a “caught” flag.
How do I kill a guard?#
Call the guard's Report Killed(killer); the formal project's tutorial flow FAB_KillGuard does exactly this. Then, in order:
- Perception turns off, movement stops, and the capsule stops blocking.
- The death presentation plays: Death Anim if set, then it freezes on the last frame or switches to ragdoll. With no animation, it goes ragdoll straight away.
- On Died fires and a Guard Dead Ghost Score event is reported.
- A permanent Body piece of evidence is left where it fell.
- An NPC Killed witnessable event is reported, and guards who see it go Alerted.
The death settings are in the AI → Death category:
| Setting | Default | What it does |
|---|---|---|
| Death Anim | Empty | Death animation (sequence or montage); empty means ragdoll right away |
| Ragdoll After Death Anim | Off | Switch to ragdoll after the animation; off freezes on the last frame |
| Ragdoll Impulse | 300 | A push along the killer-to-guard direction when the ragdoll starts |
| Destroy After Death | 0 | Seconds before the body is destroyed; 0 keeps it forever |
How do I knock a guard out?#
Each Take Punch(attacker) counts one punch. Hits To Knock Out (10) knocks the guard out, and the count resets if no punch lands for Hit Reset Time (10 seconds). Knock Out knocks it out at once.
While out, it doesn't perceive or move, and its Awareness and memory are frozen. It wakes on its own after Recover Time (8 seconds) and carries on where it left off; Wake Up wakes it early. With a Knock Out Anim it plays that and holds the last frame; without one it goes ragdoll and later stands up where the body lies.
Events: On Hit Received(attacker, total punches), On Knocked Out, On Woke Up.
How do guard fights work?#
This is the Fight Allies card-forced state; section 11 covers how to trigger it.
- The guard looks for the nearest other guard within Fight Search Radius (3000 cm) that is alive and conscious, checking again every 0.5 seconds.
- It walks over and stops at Fight Stand Off Distance (150 cm). Closer than 120 cm, it steps back while still facing its opponent.
- Within Fight Attack Range (190 cm) it throws a punch every Fight Attack Interval (1 second, never shorter than the punch animation). The punch lands after Attack Hit Delay (0.35 seconds), and the opponent takes a punch.
- The guard that is hit plays a hit reaction, and 10 punches knock it out. With no opponent nearby, a guard stands still until the forced state ends.
On Attack(opponent) fires on each punch. Fighting guards don't capture the player, but they keep perceiving.
How do I change the attack and hit animations?#
Under AI | Fight Anim. Attack Anims default to the template's MM_Attack_01 to 03 and Hit React Anims to its light hit reactions; one is picked at random each time. Ignore Fight Root Motion is on by default so a punch doesn't push the guard into its opponent. Blueprints can also call Play Attack Anim and Play Hit React Anim directly.
10. Emotion, stealing emotions and pacify#
Every guard carries an emotion component and has exactly one emotion at a time, Calm by default. The player can steal a guard's current emotion as a card; the robbed guard returns to Calm, goes back to its patrol and ignores everything for a while, which is called pacify.
Which emotions are there, and where do they come from?#
Four for now: Calm, Angry, Fear and Joy. The rule table (Rules) decides which applies, and by default it has only two rules:
- Threat present (Alerted, or seeing the player) → Angry.
- Found an ally's body → Angry, held until it is stolen.
Fear and Joy have no default rules. Add rules to the table, use switch nodes such as Turn On Fear and Turn On Joy, or use Set Custom Flag with a Custom Flag condition. To write your own logic entirely, override Evaluate Desired Emotion in Blueprint.
Which conditions can rules use?#
Threat Present, No Threat, Allies Nearby (a living ally within Ally Radius, 1500 cm), No Allies Nearby, Evidence Found (it remembers any evidence), Body Found (the remembered evidence is an ally's body), Suspicious and Custom Flag. Every condition in a rule must hold, and when several rules hold, the highest Priority wins.
How does an emotion change?#
- When a new emotion's conditions are met, the color flickers between old and new for Emotion Change Time (1 second), then switches instantly.
- If the conditions stop holding during the flicker, it is cancelled and the old emotion stays.
- When no conditions hold at all, the guard returns to Calm after Emotion Reset Time (3 seconds).
- Dead guards have no emotion.
To show the color, have the Blueprint read Get Display Color every frame and set it on the material; the flicker is already worked out. Each emotion's color is set in Emotion Colors.
Can a guard start the level angry?#
Yes. Set Initial Emotion and Initial Intensity. With Lock Initial Emotion on, it keeps that emotion regardless of the rules until the player steals it.
How do I steal an emotion?#
Call the guard's Steal Emotion(thief), which returns the emotion and its card weight (the emotion's intensity). Nothing in the formal project calls it yet, so the stealing ability still needs to be hooked up. After a steal:
- The guard returns to Calm and can't produce the stolen emotion for Emotion Suppress Time (10 seconds).
- An Emotion Stolen witnessable event is reported: other guards who see it go Alerted, and Belief rises. The robbed guard itself is not a witness.
- If the stolen emotion isn't Calm, the guard is pacified.
Stolen mid-flicker, the thief gets the old emotion by default; turn on Take Pending During Flicker to get the new one instead.
What is pacify?#
A pacified guard forgets everything: Awareness drops to 0, its memory clears, it returns to Unaware, any card-forced state ends, and it heads straight back to its patrol route. While pacified it doesn't see or hear, isn't a witness and ignores warnings; evidence it sees during this time is ignored for good.
| Setting (AI → Emotion → Pacify) | Default | What it does |
|---|---|---|
| Pacify On Emotion Stolen | On | Whether a stolen emotion pacifies the guard |
| Pacify When Calm Stolen | Off | Whether stealing Calm pacifies too. Off, so that stealing Calm isn't a free “stop chasing me” |
| Pacify Duration | 0 | How long it lasts; 0 uses the emotion component's Emotion Suppress Time (10 seconds) |
Blueprints can also call Pacify(duration) and End Pacify. Events: On Pacified and On Pacify Ended. The thin cyan bar over the guard's head shows the time left.
Do cards or knockouts change emotions?#
No. During a card-forced state or a knockout the emotion is frozen: it neither changes nor returns to Calm, although it can still be stolen.
How do I see a guard's current emotion?#
Turn on Draw Debug on the emotion component to draw a ring in the emotion's color at the guard's feet; it flickers during a change. Events: On Emotion Changed, On Flicker Started, On Flicker Cancelled and On Emotion Taken.
11. Hooks for cards and abilities#
Cards affect guards in two ways: forced states (only Fight Allies for now, which makes guards fight each other) and area effects such as switching lights, making noise or pacifying. A forced state changes behavior only, never the emotion.
How do I make a group of guards fight?#
Get AIEnemySubsystem → Force State In Radius(center, radius, Fight Allies, duration). Every living, conscious guard in the radius starts fighting, and it returns how many were affected.
- For one guard only, use Force State(state, duration) on the guard.
- A duration of 0 or less lasts until Clear Forced State is called.
- Forced guards don't capture the player; afterwards they carry on from their current alert state.
- Event: On Forced State Changed(Old, New). The guard's State Forced tells you whether a forced state is active.
Which node should each effect use?#
| Effect | Node | On |
|---|---|---|
| A group of guards fights | Force State In Radius | Subsystem |
| A blackout, an area goes dark | Set Lights In Radius | Subsystem |
| A noise to lure guards away | Report Sound At | Subsystem |
| Send one guard to look somewhere | Request Investigate | Controller |
| Calm a guard so it ignores the player | Pacify | Guard |
| Knock out directly | Knock Out | Guard |
| Invisibility | Add the InvisibleToAI tag | Player actor |
| Do something else to guards in range | Get Enemies In Radius / Get All Enemies | Subsystem |
Any Blueprint can get the subsystem with Get AIEnemySubsystem, with no reference needed.
Are there ready-made test keys?#
The Stealth Move Package component has a set of test keys: T makes nearby guards fight (press again to clear), L toggles the nearest AI Light, V turns invisible, E kills and F steals an emotion. Ctrl crouches, Shift sprints and the mouse wheel zooms.
The formal project's player Blueprint doesn't have this component, so these keys don't exist there. For testing, add it to a test character for a while; it creates its own input at runtime, so no extra assets are needed.
12. Ghost Score events#
Guards report five “the player was exposed” events to the subsystem, so a scoring system only has to listen there to hear every guard. The bundled Ghost Score component is a ready-made scoring example, and its point values are still placeholders.
Which events are there, and when are they reported?#
| Event | Reported when | Repeats? | Ghost Score default |
|---|---|---|---|
| Spotted Player | A guard goes from not seeing the player to seeing them | Once per guard per alert cycle; again only after it is back to Unaware | −10 |
| Detected Player | Alerted and watched for Chase Delay, so the chase starts | Once per time it goes Alerted | −50 |
| Noise Heard | A guard hears a sound | Once per guard per alert cycle | −5 |
| Alarm Raised | A guard warned the others (Share Alert) | Every warning | −25 |
| Guard Dead | A guard is killed | Once per guard | −100 |
An alert cycle runs from the moment a guard gets suspicious until it is back to Unaware. So a player slipping in and out of a guard's view doesn't keep losing points.
How do I connect my own scoring system?#
Get the subsystem with Get AIEnemySubsystem and bind:
- On Ghost Score Event: fires for every type.
- Or the per-type On Spotted Player, On Detected Player, On Noise Heard, On Alarm Raised and On Guard Dead.
The event data holds the type, which guard, where it happened, the instigator (the player, the noise maker or the killer, possibly empty) and the game time. Blueprints can also send one by hand with Report Ghost Score Event, for example from a test button.
How do I use the bundled Ghost Score component?#
Put it on the player, or on any actor in the level. It listens to the subsystem by itself, applies the points under Points, and prints every change on screen and in the log.
- Starting score: Starting Score, default 1000.
- Custom points: Add Score(delta, reason), for example for an objective.
- Reset: Reset Score.
- UI: bind On Score Changed(new total, delta, reason).
- Quieter screen: turn off Print Score Changes.
Nothing in the formal project uses this component yet.
13. Decision component and machine learning#
Where a guard goes when it can't see the player, meaning the next search point and the hunt target, is up to the decision component. The rule version is what runs today. The ML hooks are in place but no trained policy is connected yet, so choosing ML falls back to the rules automatically.
How does the rule version pick points?#
- Search: a random reachable point within Search Radius of the search center.
- Hunt: straight to the newest clue.
Sight, Awareness, capture and chasing a visible player never go through the decision component; they are always rule-based.
How do I switch between rules and ML?#
The guard's Decision component → Decision Mode: Rule or ML. When ML isn't available, Get Active Mode returns Rule and the fallback is counted in ML Fallback Count.
- On Decision Made(request type, point, from ML) fires on every decision.
- Draw Debug draws the latest decision point: blue for ML, gray for rule.
What is the training arena?#
A toolkit for training and evaluating ML; its design doc is at Content/EnemyMachineLearning/Docs/Design.md. Normal levels don't need any of it.
| Class | What it does |
|---|---|
| Enemy ML Arena | One area, 1 guard and 1 bot player. Each episode places both at random out of each other's sight and gives the guard an initial clue; a catch is Captured, running out of time is Timeout |
| Enemy ML Player Bot | A bot player that hides, relocates and flees, with three difficulty stages: stays put, relocates, flees |
| Enemy ML Evaluator | Collects episode results, writes a CSV to Saved/EnemyML/, and prints the capture rate and mean capture time |
| Enemy ML Training Game Mode | The game mode for training maps |
When tiling several arenas, keep their centers farther apart than Alert Share Radius plus the sprint noise radius, or neighbors will interfere with each other.
Can I use ML now?#
Not yet. The policy network isn't connected, so Is ML Available always returns false. Setting Decision Mode to ML is harmless: it logs one warning and then follows the rules.
14. Debug tools and the test level#
The most useful tool is the guard's Draw Debug: it draws the current cone, the clue points in memory, the status text and the awareness bar. Together with Draw Debug on AI Light and Stealth Noise, it shows most of what the AI is thinking.
What does each debug switch draw?#
| Switch | Where | What it draws |
|---|---|---|
| Draw Debug | Guard, AI → Debug | The cone; clue points (red ball for the player position, purple for evidence, cyan for sound); the orange alert-sharing circle while Alerted; the status text and awareness bar. It also turns on the controller's debug |
| Draw Awareness Bar | Guard, AI → Debug | Only the awareness bar, see section 4 |
| Controller debug | On automatically with the guard's Draw Debug | A magenta line to the current target point, the yellow search circle while searching, the behavior name and move status; a copy is printed in the top-left |
| Draw Debug | AI Light component | The light/dark circle on the floor, yellow when on, dark blue when off |
| Draw Debug | Stealth Noise component | Noise rings, and lines to the player from guards that heard them |
| Draw Debug | Emotion component | A ring in the emotion's color at the feet, flickering during a change |
| Draw Debug | Decision component | The latest decision point |
| Draw Debug | Stealth Move Package | Kill range in white and steal range in cyan |
How do I read the text over a guard?#
- The guard's line: its state and Awareness, for example Suspicious Awareness: 0.45 Hold 6.2s, where Hold is the suspicion hold time left. While any light in the level is off, it also shows [Guard Lit/Dark, Player Lit/Dark].
- The magenta line above it: the controller's behavior, how long it has lasted, and the move status (moving, done, failed/idle).
Text over the head needs a HUD, so it doesn't show in Simulate; use the copy in the top-left instead.
What's in the LV_AITest test level?#
/Game/Benjamin-AI/LV/LV_AITest is a level built for testing the AI. Every guard and light has debug drawing on, and the floor is colored by zone.
| Zone | Tests | Layout |
|---|---|---|
| A Sight and cover | Cone and occlusion | An outdoor lane with low cover (crouch behind it) and pillars, one patrolling guard |
| C Hearing | Noise and walls | A booth with a guard facing away from the walkway; try walking, sprinting and crouching past |
| B Lights | Switching lights | A room lit by three AI Lights, one patrolling guard |
| E Dark hall | Sight in the dark | Two AI Lights that start off, one patrolling guard |
| D Witness, body, alarm | Witnesses and alert sharing | Two guards facing each other, one patrolling guard, and one behind a wall that only an alarm can reach |
What should I watch for when opening LV_AITest in the formal project?#
- First change World Settings → GameMode Override to /Game/Blueprints/Player/BP_ThirdPersonGameMode; the template game mode it points to doesn't exist in the formal project.
- The key hints painted on the floor are for the Stealth Move Package, and the formal project's player doesn't have those keys.
- To switch a light in PIE, press F8 to leave the character, select the light's PointLight component and untick Visible.
How do I find out why a guard stopped moving?#
Look at the red “[guard name] MoveTo failed …” text in the top-left. It lists every step of the failed path request: whether the navigation system exists, whether the target projects onto the navmesh, the pathfinding result, the movement mode and more. The usual causes are a missing navmesh, or a target too far from it.
15. Troubleshooting#
Most problems are easiest to start on with the guard's Draw Debug: the text over its head shows its state, behavior and move status. Below are the usual causes, by symptom.
The guard doesn't move at all#
- There is no navmesh, or the target is too far from it. Check the red MoveTo failed text in the top-left.
- Behavior Paused is on in the controller.
- The guard is knocked out or dead, or it's in a fight with no opponent nearby.
- The guard's AI Controller Class was changed to something that isn't AIEnemyController.
The guard can't see the player#
- The player has the InvisibleToAI tag.
- Target Override points at another pawn, or the player isn't player 0.
- Something in between blocks the Visibility channel, including invisible trigger boxes.
- The player is in the dark and the guard is lit, so the range is only 225 cm. Check the [Guard …, Player …] text.
- The guard is pacified, or Perception Enabled was turned off.
The guard sees or catches the player through a wall#
- That wall isn't set to Block on the Visibility channel.
- Capture doesn't check line of sight: an Alerted guard within 150 cm captures, thin wall or not.
The guard doesn't hear anything#
- Nothing calls Make … Noise or Report Sound. Stealth Noise never makes noise on its own.
- The player is crouching, and the crouch radius defaults to 0.
- A wall in between cut the radius down through wall attenuation.
- The player is invisible, or the guard is pacified.
The guard keeps investigating and never goes back#
Usually it's constant noise: every sound it hears restarts the 8-second suspicion hold. Check whether something makes noise every frame.
Turning off a light does nothing#
- The light has no AI Light component.
- The light was only dimmed, so its intensity isn't 0, or it was hidden or destroyed instead.
- Another AI Light that is still on covers that spot.
- The light hangs too high or Radius is too small, so it covers no floor. Turn on the AI Light's Draw Debug to see its circle.
Sometimes the guard chases on sight, sometimes it stands still first#
That's the confirm time working as intended. A guard that watched from zero all the way to Alerted already has enough continuous sight and chases at once. One that was alerted first by a witnessed event or a noise stares for 1 second when it then sees the player. See section 4.
A capture does nothing, or fires many times#
C++ doesn't end the game; a Blueprint has to handle On Player Captured or bind On Captured Player. It fires every frame while the player is in range, so the listener has to ignore repeats.
Fewer points are lost than expected#
Spotted Player and Noise Heard are reported once per guard per alert cycle, and again only after the guard is back to Unaware. That is on purpose.
A changed setting doesn't take effect#
- The placed instance may override the Blueprint default; overridden settings show a yellow reset arrow in Details.
- Controller settings can't be changed in the level; make a controller Blueprint, see section 8.
- After changing a C++ header, close the editor and rebuild. Live Coding can't handle new properties.
The cone is green but the guard is clearly after the player#
An Alerted guard that has lost sight of the player draws a green cone too; it only turns red while the guard sees the player. Trust the state in the text over its head.
A knocked-out guard wakes up somewhere else#
Without a Knock Out Anim the guard goes ragdoll, and the body may roll. It stands up where the body actually lies, which is expected. Set a fall animation if you don't want that.
16. Blueprint API quick reference#
The nodes you can use in Blueprint, grouped by the object they live on. Any Blueprint gets the subsystem with Get AIEnemySubsystem; get the controller with Get AI Controller → Cast To AIEnemyController.
Guard (AIEnemy) functions#
| Node | Use |
|---|---|
| Get Perception Target | The target it is watching |
| Can See Actor, Can See Location | Whether it can see an actor or a spot right now |
| Get Effective Sight, Get Sight For Light | Range and half-angle with light applied |
| Add Awareness, Set Awareness, React To Stimulus | Change Awareness |
| Set Known Player Location | Tell it where the player is without changing Awareness |
| Reset Perception | Clear its memory and return to Unaware |
| Is Chase Confirmed | Whether it has confirmed and may chase |
| Hear Sound | Make this guard hear a sound directly |
| Share Alert, Receive Shared Alert | Send or receive an alert |
| Notify Evidence Found, Witness Event | Make it find evidence or witness an event by hand |
| Get Point Of Interest, Get Point Of Interest Source | The spot most worth checking, and where that clue came from |
| Forget Player, Forget Evidence, Forget Sound | Forget one kind of clue |
| Report Killed, Start Ragdoll | Kill it, switch to ragdoll |
| Take Punch, Knock Out, Wake Up | Take a punch, knock out, wake up |
| Play Attack Anim, Play Hit React Anim | Play fight animations |
| Steal Emotion | Steal its emotion |
| Pacify, End Pacify, Is Pacified | Pacify |
| Force State, Clear Forced State | Forced state |
| Set Move Speed | Change the move speed for now |
| Can Perceive Events | Whether it can perceive: alive, conscious, not pacified |
| Is Actor Invisible To AI | Whether an actor has the InvisibleToAI tag |
Guard (AIEnemy) events#
| Event | Fires when |
|---|---|
| On Alert State Changed | The alert state changes |
| On Player Spotted, On Player Lost | The player becomes visible, or is lost |
| On Player Captured, On Captured Player | The player is captured, every frame while in range; the second is a bindable delegate |
| On Sound Heard | It hears a sound |
| On Alert Received, On Alert Shared | It receives a warning, or sends one |
| On Evidence Found, On Event Witnessed | It finds evidence, or witnesses an event |
| On Behavior Changed | The controller switches behavior |
| On Died | It dies |
| On Pacified, On Pacify Ended | Pacify starts or ends |
| On Forced State Changed | A forced state starts or ends |
| On Attack, On Hit Received | It throws a punch, or is hit, in a fight |
| On Knocked Out, On Woke Up | It is knocked out, or wakes up |
Controller (AIEnemyController)#
| Node | Use |
|---|---|
| Request Investigate | Send the guard to look at a spot |
| Return To Patrol | Go back to its post now |
| Reset Behavior | Stop everything and treat the current location as the new post |
| Force State, Clear Forced State, Is State Forced | Forced state |
| Behavior, Current Target, Behavior Paused | Current behavior, current target point, pause switch |
Enemy subsystem (AIEnemySubsystem)#
| Node | Use |
|---|---|
| Report Sound, Report Sound At, Report Sound With Feedback | Make a sound |
| Compute Sound Reach, Compute Sound Shape | How far a sound travels in a direction, for drawing its shape |
| Get Enemies In Radius, Get All Enemies | Find guards |
| Force State In Radius | Force a state on guards in an area |
| Get Light Level At, Is Location Dark, Has Any Light Off | Light queries |
| Set Lights In Radius, Get All Lights | Switch the lights in an area, get every AI Light |
| Report Evidence, Report Evidence At, Remove Evidence, Get Active Evidence | Evidence |
| Report Witnessable Event, Report Witnessable Event At, Get Witness Records | Witnessed events |
| Get Belief, Set Belief, Add Belief | Belief |
| Report Ghost Score Event | Send a scoring event by hand |
| On Belief Changed, On Event Witnessed | Delegates: Belief changed, an event was witnessed |
| On Ghost Score Event and the five per-type delegates | Scoring events, see section 12 |
Other components#
| Component | Common nodes |
|---|---|
| AI Light | Turn On, Turn Off, Toggle, Set Light On, Is Light On, Get Light Radius, On Light Changed |
| AI Evidence | Report Change, Report Change At, Report Change Of Type, Retract Last Change |
| Emotion | Take Emotion, Force Emotion, Turn On / Off Emotion and the Angry, Fear, Joy and Calm shortcuts, Set Custom Flag, Get Display Color, Evaluate Desired Emotion (can be overridden) |
| Stealth Noise | Make Walk Noise, Make Sprint Noise, Make Crouch Noise, Make Movement Noise, Make Noise, Get Noise Radius |
| Ghost Score | Add Score, Reset Score, Get Score, Get Points For Event, On Score Changed |
| Decision | Choose Search Point, Choose Hunt Point, Is ML Available, Get Active Mode, On Decision Made |